Hello,
I am not sure why you have to change the way you implement some of those things in v5 but, now, with the new dashboard, we can’t dismiss Non MainWP changes, just see then and select but no action possible and if you click see all, you see all the changes that you don’t want to see! Can we have the dismiss button back please?
Also, for hardening, so many false alert now! Also, no more options to run the hardening on all sites…
Evolution is good but when you change everything on V5 from V4, we had to adapt, and now, you are changing everything again from dashboard that we have to rebuild to function removal… Not cool!
We have more than 200 websites and no time to test the beta but those changes were madness for an agency. I saw some other people mad and I understand why.
So please bring back what we were used to to facilate our workflow.
Thanks,
Fred
PS: Editing… forgot to mention the weird load of the dashboard with everything got squished and then expand and sometime, lost the layout! Very annoying too.
The team believed that the button should be removed since most of the Hardening fixes must be performed manually.
Please feel free to make a suggestion about re-introducing this on our feedback site. That way, others can vote for it, letting us know which features our users want the most. https://voice.mainwp.com
@bojan - what about the dismiss of all non MainWP changes? Gone too as you think it needs to be done manually one by one? We got 15 of them daily with more than 230 websites so do we have to remove this function too as it is useless now?
It also still takes much more space than in 5.3. Then it fitted in a 1/3 column, but I have to scroll now.
And the text that shows the status has very few contrast in dark mode:
I’ll check with @bogdan to confirm whether this layout change was intentional or if adjustments are planned.
As for the transition from 5.3 to 5.4, most elements can still be customized to your preference using the Custom Dashboard Extension.
Regarding the dark theme, Bogdan is also working on a full revamp in the coming weeks, and I’ve noted to reach out for your feedback before it’s released.
That’s a good thing in case you don’t like the default, but inthis case the default is not working correctly for all users, so in that case it’s better to improve the default instead of patching it with customizations.
In 5.3 some good improvements were done, that are gone again now. One of them was the space it was taking by replacing text with icons. The info was concatenated to save space. With the current table layout and text instead of icons we need a much wider widget to show the same data. So I’d really like to know why this path was chosen.
As I mentioned, I’ll check with @bogdan on the design decisions, and he’s already working on an update in the next few weeks. If this turns out to be a bug or an issue on our end, we’ll address it in a separate update.
If it’s an intentional design change, I’d recommend sharing your thoughts on voice.mainWP.com so we can gauge if other users feel the same way.
Okay thanks but also, it brings back old non MainWP changes, we have 242 of them that were dismissed… Not going to do it manually so I will wait for the update. Any chance to bring back the “fix all security issues”? It was helpful. Maybe do a survey next time you are removing functionalities? I know you can’t do it for one person but, for big users like ourself, when you hundreds of websites to manage, little details like this make a huge difference.
In that time I’ve seen two rounds of changes where people have been upset about changes on dashboard layout not to mention consistently finding functionality removed after updates.
Consistent UI/UX leads to efficiency and safety. If changes happen:
people have to relearn their work flow and this adds stress in lives that are already often overloaded with IT noise and change
This can destroy security. If you are relying on alerts and they have been removed, then you can miss important info.
Imho - altering peoples layout and altering the UI is a sign of a bad dev process. It is an example of IT development driving clients, not serving clients. Seeing two major changes in 6 months is a warning sign to me the products maturity is in doubt.
It is the type of issue that makes me more likely to migrate to another product where there is less noise and I can concentrate on the job, not waste time managing my tools and relarning a work flow. I want to do my job, not have to soend time re- configuring toolsets
This morning i woke up to 43 emails. Mostly from MainWp, plugins not updated, updates to items, version updates, latest blog posts etc etc. This type of noise is possibly needed to monitor sites. But adding UI changes etc. adds stress to a day where i havent even started work and have 43 trashed emails - non of it actionable. Again IT is full of noise. Adding less noise is ideal.
I am not trying to be critical here - just a hopefully useful reflection.
I really appreciate you sharing your thoughts on the recent UI changes. I know how frustrating it can be when an update disrupts your workflow, that’s definitely not what we want.
You’re correct that consistency is key and when things move around unexpectedly, it takes extra time to adjust, and we get that.
While some changes were design updates, others were necessary technical improvements as we migrated from Gridster.js to Gridstack.js to use a modern and supported framework that increases the dashboards mobile-friendliness and allows it be more responsive. Even so, we understand the impact these changes have on your daily use.
If there are specific tweaks or features you’d like to see, I’d love for you to add them to voice.mainwp.com. That’s where our team keeps track of user suggestions.
We’ll be more mindful of how and when we roll out UI updates in the future. Thanks again for taking the time to share your feedback!
Thank you for sharing! I am so happy to have started this thread and see that I am not the only one unhappy with the changes.
Don’t get me wrong, I am happy to see evolution but we already had a big change from v4 to v5 and all of sudden, everything we started to be used is removed again. I understand that you need to change the framework, but at least keep the same functionalities… Now we have to upvote for something removed, makes no sense to me. Anyway, we don’t have much control over that, just hope that we will see both functionalities back soon or are we the only ones using it?
Fred
That’s exactly why we introduced the Voice system earlier this year, in order to give all MainWP users a clear way to share feedback.
With our growing community, Voice helps us see which features matter most across different workflows and use cases. This allows us to make more informed decisions about what to prioritize.
Again, I understand the frustration when things change. Framework updates sometimes require adjustments, and while not everything can stay the same, we always aim to balance improvements with user needs.
If there’s something specific you’d like to see return, adding it to voice.mainwp.com ensures it’s on the team’s radar.
