Aldro

When you say user preferences --> We only allow that view from an admin standpoint, desperately hope that is still the case. Basically we want our users to login and view the forums as it currently is without being forced to a new layout. Thanks for answering mate.

Ugh... What about our themes and the classic design of forums that we still have to this day? There's no way this will be removed, right? => All the recent videos/images of V5 look so different that I don't know for sure... Please can someone confirm they're not gonna force a changed layout?

Can someone confirm or deny if posting with HTML is gone or not?

How about letting us stay on V4 indefinitely? Otherwise this just reads as a ticking bomb for many of us as we eventually won't have a choice but to upgrade. We understand the reasons but the frustration comes from a lack of choice being offered to us, you're essentially cutting off a part of what is important to us. Now we have to find ways to pick up the pieces and god knows what else goes missing in a future V6, it is very disheartening and concerning to be frank. Can anyone please confirm if postingdirectly with HTML in posts is also being removed? That was a highly used feature by myself, sigh...

Absolutely right there with you.

Thanks, thank god for that. My current concern is about the plugins we will lose that no longer hav developers around. Do you know if there's a way for us to manually turn those into applications??

Exactly, many people have multiple emails and it's already such a hassle tracking the email - password combination across all of your accounts on the net. Username has simplicity going for it and if you were trying to get access, you would get blocked within 5 failed attempts anyway (atleast on our forums). Forcing an email just doesn't make any sense in our situation, it's a gaming forum and so let your clients make the choice!

The username vulnerability is limited to logging into an account on our forums. Why can't we make that call ourselves? Force email on AdminCP sure but why demand it of the users when we don't want it? As long as accessible alternatives exist for PHP and Tagging, that is OK. But Status Updates was universally loved among our users. Holdover or not, please consider not removing features that already exist and are accesible to members, in the future. I just realized Plugins won't work either. Is there any way for us to convert them to applications? Many of our plugins have no developer around. Are we to just accept losing all of that? What are our options?

EDIT: Posted this in wrong section, please remove. Status updates have been removed in v5. Signing in with a Display Name has been removed in v5, email addresses must be used instead. Open tagging has been replaced with a new system in v5. Pages: You are using custom PHP blocks. These will no longer function in v5. Why on earth are we losing features that we have had access to up until this point? I understand iterating on features but the complete removal of Status updates, Display Name login and PHP blocks is a baffling decision. Please reconsider and let us keep the product that we have been paying for, or at the very least make the patch an optional one. We are people with a hobby and not developers, losing functionality or finding additional ways of making things work due to patches like this is a nightmare scenario. All we ask is to maintain a semblance of backwards compatibility, as paying customers -- is such a thing really too much to ask for?

Ah bummer, then it still won't work for us. Our idea was to have 1 secondary group called "Songs enabled" that we can then assign to those who we want to allow to upload a song. If that is not possible: Can you somehow fix the error below or send me the previous older version so I can somehow downgrade to it? I have even disabled the secondary group setting yet everyones profile still looks like this:

It doesn't seem to be working. Perhaps because our members have multiple groups and some are set to disabled whereas some are set to enabled? Members are seeing the following in their profile page: And the support tool logs this as an error: It still only works when primary group is set to enabled currently.

Thank you!!

Any updates on allowing secondary groups to use this feature? 🙏

No worries at all, thank you so much! ❤️

Don't mean to stress you (take your time!) but is there any updates regarding this? 😄