Dreadknux

Many thanks @Matt!

"But when will then be now?" "SOON."

Yeah, I just don't like the blur at all and want it removed entirely. 🙂 That's why I decided not to post a bug topic, technically this is about a design choice. 😄

I've been a bit pre-occupied with work lately to stay on top of Beta updates (sorry), but just caught up and installed B4 and noticed a change in how the text-against-image areas on Wallpaper widgets have been handled... I can't say I'm a fan. ^ It doesn't look very nice really. Look at all that fog around the text, smudging the background image up to the halfway point. Is there a chance we can switch this back to the way it was (or maybe revert this with custom CSS somehow)? I much preferred how it was handled before... now it just kind of looks like someone's opened a tub of vaseline over my screen, my eyes are going blinking crazy just looking at it 🙃

Yeah, that's a nice solution for people who want to save specific statuses, but that's not gonna work for me, lol. Trying to archive 13+ years worth of status updates one by one will take me an ice age. 🙂 Hopefully the solution Matt proposed could be looked into as I can definitely work with something like that.

I downloaded and installed the security update 4.7.19 to my live instance, and have been hit with this error at the very start of the upgrade process: I cannot proceed, refreshing does nothing, and I cannot roll back the option to initiate the upgrade to "unlock" my community - as a result my website is now stuck on the 'upgrading' notice page and I cannot resolve this. This is urgent as I need the site to be live today; can someone please assist?

This is a welcome upgrade to the moderation features of the suite, thank you for the hard work on this. I especially like the Approve/Reject system, as we often get reports from users who are simply reporting something they disagree with/are mad about which doesn't actually break any community rules, so we can formalise this in our workflow now by rejecting the complaint.

Hi Ehren, the issue is happening on the homepage of my test instance (you should have access to this via the DM I sent you recently about the other issue). This is still occurring in BETA 3. If it helps, I have captured a recording of this issue occurring in real time, swapping between a signed-in instance and a mobile-view private browser instance. There is also a random issue I've found where the floating dialog box to insert an existing image appears out of bounds of the browser window (you can see this happen in the video below at 0:40)... leftwrap-issue.mp4

Hi Ehren, the issue is happening on the homepage of my test instance (you should have access to this via the DM I sent you recently about the other issue). This is still occurring in BETA 3. If it helps, I have captured a recording of this issue occurring in real time, swapping between a signed-in instance and a mobile-view private browser instance. There is also a random issue I've found where the floating dialog box to insert an existing image appears out of bounds of the browser window (you can see this happen in the video below at 0:40)... leftwrap-issue.mp4

That's great, thanks @Ehren!

That could work, yeah! I was thinking, personally, that each status update would be its own topic in a specific forum (rather than a single topic for all of one user's statuses) and every status update comment would translate to a (quoted) reply within that topic. But I'm happy for a solution like you suggested as well, it might actually be cleaner that way! Let me know if something like either of the above is possible at all on the Invision side. Thanks @Matt! 😀

That's fair enough. I'll leave it here for consideration then, thanks Marc. I realised that I was slightly incorrect in my last post; this only seems to be an issue when using folders; I can have pages with the same filename in different folders without issue, I just have to make sure the folders are named individually. So: /pages/special/v1/games-v1/gamepage1(.html) /pages/special/v2/games-v2/gamepage1(.html) /pages/special/v3/games-v3/gamepage1(.html) /pages/special/v4/games-v4/gamepage1(.html) Still not super-ideal, but I think I can work with this for the time being. Thanks for the feedback.

Hi guys (Sorry for cross-posting, I didn't realise that the old topic I asked about this was in the now-closed Alpha Club) As we're in Beta phase, I wanted to raise this topic again and see if there has been any more thought given to this? It'd be great to keep an archive of status updates somehow instead of simply disappearing them; if there's no plans then I'll need to look into a third party solution, so it'd be good to know the first-party plans so I can arrange things on my side accordingly. Thanks!

Sorry for being annoying, but I wanted to raise this particular topic again as it'd be great to get some clarity on how this works from IPS' side. At present, my workaround plan is to do the following: /pages/special/v1/games-v1/gamepage1-v1 /pages/special/v2/games-v2/gamepage1-v2 /pages/special/v3/games-v3/gamepage1-v3 /pages/special/v4/games-v4/gamepage1-v4 etc etc. As you can see, it's not exactly elegant in terms of FURL, is unwieldy for admins to name like this, and from an end-user POV it's pretty redundant (they will ask, "why does "games" and "gamepage1" require the "-vX" suffix at the end of it all the time?"). I should be able to organise as follows: /pages/special/v1/games/gamepage1 /pages/special/v2/games/gamepage1 /pages/special/v3/games/gamepage1 /pages/special/v4/games/gamepage1

I believe this is fixed in the next Beta.