Matt

Yes, there is something funky going on with the js language file. I'll have a look shortly.

Please hold. Upload this to your root directory (where init.php is) and run through your browser. lang.php

Is this a self hosted installation?

Woohooo!

It's something we can being, yeah. Obviously we want 5.0.0 out asap but we will do a massive feedback round and look at ideas like this. I've never noticed because I have an Apple mouse and the swipe gesture works but I accept your point.

Send me PM with an admin log in and FTP and I can take a look. I'll remove the info once done.

We did change some of the language strings, but the upgrade step should have taken care of that for you. I know it sounds like a silly question, but did you run the upgrader?

Beta 2 was released today, and I've just provided a new update on progress:

Invision Community 5.0.0 has reached a huge milestone; we're now in open beta testing. After numerous alpha releases, we're ready to move forward with the last stage of development and testing. The beta stage is primarily just fixing bugs and tweaking existing features and we're confident that the beta testing stage will run smoothly as its already stable and being used on a handful of production sites by brave souls who have upgraded immediately. Of course, we'd not recommend being so cavalier, especially if you are not very technical and do not have the time or patience to wait for fixes and risk broken functionality between beta releases! The good news is that you can use Invision Community 5 beta on a test installation, so you can set it up, and learn its new UI and feature set before planning your upgrade. The beta is available for both Invision Community Cloud customers, and Invision Community Classic customers. Invision Community Classic (Self Hosting) If you have an older license type (Invision Community Suite) and want to test Invision Community 5, then you are welcome to switch to the new v5 license in the client area. The renewal structure has changed, and all this is explained before you switch. If you have the classic license, you will then see the Invision Community 5 Beta download in your client area. Invision Community Cloud Our Cloud customers can request a time-limited v5 demo. Instructions on how to do this are in the Invision Community 5 Beta Testing Club. We're thrilled to move closer to a final release a year after Ehren revealed the "fresh new vision" for Invision Community 5. We'd love for you to join us in the Beta Testing Club and let us know what you think of Invision Community 5.

Any edits to /static/ files will be overwritten. I'll probably have to look on your install and server to see what's going on.

It is fixed. There was one branch for all v4 fixes that had been merged in.

Changed Long ID to 5000028

Self hosted will need to do the manual upload this time. I think the self hosted download zip from cloud is broken in this release.

Patch incoming for this.

Please post bugs in the bug tracker, thanks!

Did I make squad a thing?

Just do the manual action for now. I'll test the self-hosting upgrade system for beta 3.

Interestingly enough, if you have a mouse that supports it, swiping left to right does move the carousel across.

Beta squad! (I'm trying something new, don't judge me) Invision Community 5.0.0 Beta 2 is floating through our cloud deployment system and should be available soon. There's a lot fixed in this version, so thank you for your patience over the past week or so. The full list of fixes is here: https://invisioncommunity.com/release-notes-v5/ Hopefully we didn't add to many new bugs. 🤞

I can't express how much I love seeing these communities, and the mix of sidebar versus top navigation. Keep them coming!

The reason for that is that the colours change subtly for dark and light mode, so adding colours needs to be done thoughtfully or they may not be easy to read. We'll likely add something to enable you to add colours and warn if they are not compatible.

Yeah, it's a bug. Can you post it over in the bugs forum? Just a link back to this is fine.

Right, so our plan was: inform, give people notice, add a deprecation on the username/email log in settings in the ACP and then phase it out in v5. This is the transition process we put into action in the November release (the posts quoted were from September). We kept our word that we were not going to remove it any time soon. Here we are two years later and you're still pointing it out instead of doing something about it. If you want to keep logging in with usernames, then feel free to stick with v4. It'll be supported for a while alongside v5. I'm not really sure what else we can do. I'd suggest that you let people know you're switching to email log ins, so check your email addresses are still valid. Give a date to make the switch so people are aware of the change. Perhaps look through your email provider's bounce list to check on email addresses that regularly bounce and then DM the owner. It's pretty much all part of running a community. We can only do so much.