Jump to content

Hexsplosions

Clients
  • Posts

    2,247
  • Joined

  • Last visited

  • Days Won

    7

Reputation Activity

  1. Like
    Hexsplosions got a reaction from Admonstrator in Suggestion: Allow for a basic editor instead of CKEditor   
    I demand IPS return my preferred editor.

     
  2. Like
    Hexsplosions got a reaction from AndyF in Upgrading to 4.1.6 EROR   
    Thankfully I took backups just before the upgrade, so I can rollback if needed. It's a hassle, but at least I have some security in that sense.
  3. Like
    Hexsplosions reacted to Lindy in Quote removal still no good in 4.1   
    We're aware of the quoting quirks - we're working on them and should have something in coming weeks. 
  4. Like
    Hexsplosions reacted to chilihead in Edit restrictions per app please   
    I saw an update from Matt here on the delete permissions. I'm not clear on what a majorish version is though, assuming it could be in the 4.1 series just not 4.1.6 or .7. Since major would be 4.2.

    When this gets around to being implemented I would like edits to also be considered and follow the same logic, and the edit restriction time in global can take effect unless overridden in app for the content item or comment, thanks.
  5. Like
    Hexsplosions reacted to Matt in Edit restrictions per app please   
    Sometimes we agree with the feedback, but have to schedule it in a future release. Sometimes we might have bigger changes planned which take into account feedback such as this.
    Your points are valid, and noted.
  6. Like
    Hexsplosions got a reaction from chilihead in Edit restrictions per app please   
    Granular permissions for create, edit, and delete, are always going to be better than global ones.
    I've not seen any feedback from Lindy in that other topic yet. I'm waiting with bated breath.
  7. Like
    Hexsplosions got a reaction from opentype in 4.1 - Ability to cache remote images   
    Here's what's come back through the ticket so far:
    A new key needed to be generated before I made the change to HTTPS, it wasn't so there is a gap between the point at which I changed to HTTPS, and enabled the image proxy, and the point at which I was notified of the need to generate a key. Any images posted during this period are now broken with no way to fix them but to trawl through posts and edit them. That's a lot of posts. Images posted before HTTPS and image proxy were in use are still pointing towards insecure connections. I'm therefore getting mixed content warnings on a huge number of topics caused by images in posts and images in signatures. There is no rebuild facility to go back through and correct this. I feel like this defeats the effort of moving to HTTPS and using the image proxy. I want a secure site that does not flood users with mixed content warnings. Images posted after the key has been updated are working perfectly. Unless I'm missing something, there are no clear indications in the ACP that I needed to do anything other than 'flick a switch' to enable the local image proxy. Considering the main use of it would be in making sites over HTTPS remain secure, with the nice green padlock, this feels like a significant oversight. It either needed to be clear in the ACP that a procedure need to be followed, or a rebuild facility needs to be provided. Actually, I'd say a rebuild facility does need to be provided, regardless of what documentation there is.
    I've asked support to get back to me to confirm whether I can do anything in SQL to replace the incorrect keys on those images already posted. Preferably, I'd like the entire post history rebuilding to make all images be served via the proxy, with the correct key. I'd also like this to be something that I, the admin, can trigger.
  8. Like
    Hexsplosions got a reaction from Vesemir in Banned Members... Are They Really Members Just Like Me?   
    I'm not a lawyer, I'm not about to take advice on a forum, nor agree or disagree with you, but simply state that the hassle that was caused by the ban message being in place led my forum to remove the label entirely. It caused a considerable amount of grief and the former member had no intention of letting up.
    I'd come back to my first point though, there really is no need to label a person banned. If members ask, tell them it's none of their business. It's quite simple when moderation decisions are elevated above membership scrutiny.
  9. Like
    Hexsplosions reacted to Adriano Faria in Banned Members... Are They Really Members Just Like Me?   
    https://community.invisionpower.com/files/file/7895-member-restrictions-on-personal-card/
  10. Like
    Hexsplosions got a reaction from Lindy in Banned Members... Are They Really Members Just Like Me?   
    I'm not a lawyer, I'm not about to take advice on a forum, nor agree or disagree with you, but simply state that the hassle that was caused by the ban message being in place led my forum to remove the label entirely. It caused a considerable amount of grief and the former member had no intention of letting up.
    I'd come back to my first point though, there really is no need to label a person banned. If members ask, tell them it's none of their business. It's quite simple when moderation decisions are elevated above membership scrutiny.
  11. Like
    Hexsplosions got a reaction from Lindy in Banned Members... Are They Really Members Just Like Me?   
    I noticed this. It made not one bit of difference to us. The ban means they can't access the site on that account. I don't have a need to broadcast to the world that a particular member is banned. In fact, in the past, this has caused me considerable problems as I was virtually accused of libel! It's better off hidden.
  12. Like
    Hexsplosions got a reaction from kar3n2 in Banned Members... Are They Really Members Just Like Me?   
    I noticed this. It made not one bit of difference to us. The ban means they can't access the site on that account. I don't have a need to broadcast to the world that a particular member is banned. In fact, in the past, this has caused me considerable problems as I was virtually accused of libel! It's better off hidden.
  13. Like
    Hexsplosions got a reaction from chilihead in Banned Members... Are They Really Members Just Like Me?   
    I noticed this. It made not one bit of difference to us. The ban means they can't access the site on that account. I don't have a need to broadcast to the world that a particular member is banned. In fact, in the past, this has caused me considerable problems as I was virtually accused of libel! It's better off hidden.
  14. Like
    Hexsplosions reacted to Morrigan in Signature in "Edit Profile"   
    It would be awesome if the "Signature" was in the "Edit Profile" page as it makes sense to be there. It's a little more of a nuisance to have to go to "Account Settings" to get to it since you can edit your Profile photo straight from the profile page.
    I would not mind if it were in both but I'd prefer that it be at least in the "Edit Profile" button.
  15. Like
    Hexsplosions reacted to BigStamp in 4.1 - Ability to cache remote images   
    I really hope this is something that is corrected, the proxy should work for all attached images no matter when they were posted.
  16. Like
    Hexsplosions got a reaction from sobrenome in 4.1 - Ability to cache remote images   
    So the SQL query was not as a viable solution. I still therefore have two outstanding issues;
    Images posted between the aforementioned dates remain broken Images posted prior to the image proxy being enabled are insecure. The ticket has been closed, with my agreement, as it's something they need to take away and work through.
    I've been told it's a high priority. (So I'm hoping for a 4.1.7/8/9 release.)
  17. Like
    Hexsplosions reacted to Joel R in Please hide spoiler contents in stream   
    I liked this post entirely for the Star Wars reference.  
  18. Like
    Hexsplosions got a reaction from Joel R in Please hide spoiler contents in stream   
    Blimey, that's bad... Seriously, we have STAR WARS around the corner and that spolier tag is about to get some pretty heavy usage! I can already feel the anger, the hatred, flowing through my members. Their journeys to the dark side will be complete, and it'll be all down to this flaw!


  19. Like
    Hexsplosions got a reaction from openfire in Please hide spoiler contents in stream   
    Blimey, that's bad... Seriously, we have STAR WARS around the corner and that spolier tag is about to get some pretty heavy usage! I can already feel the anger, the hatred, flowing through my members. Their journeys to the dark side will be complete, and it'll be all down to this flaw!


  20. Like
    Hexsplosions got a reaction from chilihead in Please hide spoiler contents in stream   
    Blimey, that's bad... Seriously, we have STAR WARS around the corner and that spolier tag is about to get some pretty heavy usage! I can already feel the anger, the hatred, flowing through my members. Their journeys to the dark side will be complete, and it'll be all down to this flaw!


  21. Like
    Hexsplosions got a reaction from MikeW in 4.1 - Ability to cache remote images   
    That's essentially what it does.
    I have found, however, that it doesn't always work or work everywhere it should.
    Signatures and forum descriptions are two places I've seen it fail. I have a bug raised about it.
  22. Like
    Hexsplosions reacted to Charles in No marketplace for you!   
    Really.
    The Marketplace authors have asked us to do it this way. They do not want to support people who may be multiple versions behind. Your argument does not really make sense as the Marketplace author's updates assume you also update the underlying platform. It would do you no good to download a Marketplace update for 4.1.5 if you are running 4.1.0.
    I feel you forget this is how pretty much all software works. If you iOS app, Windows program, OS X app, and so on releases a bug fix update and you have not upgraded iOS itself, Windows itself, or OS X itself then that update will not download for you because it's not going to work for you.
    While I realize you are trying to manufacture a problem, for what it's worth: we used to do it as you suggest. The Marketplace contributors hated it because they ended up wasting time chasing down "bugs" only to find out the issue was the client was multiple versions behind.
  23. Like
    Hexsplosions reacted to chilihead in Excellent Progress on IPS4 Resources Section   
    How to use certain fields like Database Relationship (especially) to their fullest potential. How to create a dynamic field where a user selects a country and the applicable states appear for selection. How to build a jobs database with companies and job seekers. A jobs database would be a popular one to use as an example to show off all the capabilities. Sort by area, profession, salary, date, combination. Expiring job postings. Featured listings. So may variables. Classified ads is another. How to get databases to actually look like websites, a few examples would be nice for different looks. Thanks
  24. Like
    Hexsplosions got a reaction from OctoDev in 4.1 - Ability to cache remote images   
    Here's what's come back through the ticket so far:
    A new key needed to be generated before I made the change to HTTPS, it wasn't so there is a gap between the point at which I changed to HTTPS, and enabled the image proxy, and the point at which I was notified of the need to generate a key. Any images posted during this period are now broken with no way to fix them but to trawl through posts and edit them. That's a lot of posts. Images posted before HTTPS and image proxy were in use are still pointing towards insecure connections. I'm therefore getting mixed content warnings on a huge number of topics caused by images in posts and images in signatures. There is no rebuild facility to go back through and correct this. I feel like this defeats the effort of moving to HTTPS and using the image proxy. I want a secure site that does not flood users with mixed content warnings. Images posted after the key has been updated are working perfectly. Unless I'm missing something, there are no clear indications in the ACP that I needed to do anything other than 'flick a switch' to enable the local image proxy. Considering the main use of it would be in making sites over HTTPS remain secure, with the nice green padlock, this feels like a significant oversight. It either needed to be clear in the ACP that a procedure need to be followed, or a rebuild facility needs to be provided. Actually, I'd say a rebuild facility does need to be provided, regardless of what documentation there is.
    I've asked support to get back to me to confirm whether I can do anything in SQL to replace the incorrect keys on those images already posted. Preferably, I'd like the entire post history rebuilding to make all images be served via the proxy, with the correct key. I'd also like this to be something that I, the admin, can trigger.
  25. Like
    Hexsplosions got a reaction from chilihead in 4.1 - Ability to cache remote images   
    Here's what's come back through the ticket so far:
    A new key needed to be generated before I made the change to HTTPS, it wasn't so there is a gap between the point at which I changed to HTTPS, and enabled the image proxy, and the point at which I was notified of the need to generate a key. Any images posted during this period are now broken with no way to fix them but to trawl through posts and edit them. That's a lot of posts. Images posted before HTTPS and image proxy were in use are still pointing towards insecure connections. I'm therefore getting mixed content warnings on a huge number of topics caused by images in posts and images in signatures. There is no rebuild facility to go back through and correct this. I feel like this defeats the effort of moving to HTTPS and using the image proxy. I want a secure site that does not flood users with mixed content warnings. Images posted after the key has been updated are working perfectly. Unless I'm missing something, there are no clear indications in the ACP that I needed to do anything other than 'flick a switch' to enable the local image proxy. Considering the main use of it would be in making sites over HTTPS remain secure, with the nice green padlock, this feels like a significant oversight. It either needed to be clear in the ACP that a procedure need to be followed, or a rebuild facility needs to be provided. Actually, I'd say a rebuild facility does need to be provided, regardless of what documentation there is.
    I've asked support to get back to me to confirm whether I can do anything in SQL to replace the incorrect keys on those images already posted. Preferably, I'd like the entire post history rebuilding to make all images be served via the proxy, with the correct key. I'd also like this to be something that I, the admin, can trigger.
×
×
  • Create New...