Rami Obeidat

Hi,

Just a quick update 😊

YOOAdmin 1.5.8 has now been released and includes fixes and improvements based on several of the points discussed throughout this topic.

The update includes improvements to the setup wizard branding flow, compatibility improvements for third-party admin toolbar actions, RTL enhancements, user management fixes, security hardening improvements, and various reliability improvements across the workspace.

We also spent additional time improving compatibility with Desktop Mode while testing both plugins together, including dark mode integration and visual consistency improvements to provide a smoother experience when both plugins are active.

If you are currently using YOOAdmin, we recommend updating to version 1.5.8 to benefit from the latest fixes and improvements.

Thank you again for all the testing, screenshots, suggestions, and detailed feedback. Several improvements in 1.5.8 were influenced by reports and observations shared here.

We genuinely appreciate the time and effort you invested in helping improve YOOAdmin, and we’re very grateful for your support and the 5-star review 🙌

Thank you!

Hi,

Thank you again for the detailed feedback and for testing YOOAdmin 1.5.7 deeply with different plugins and workflows. We really appreciate the time you spent reporting everything clearly.

1. Regarding the logo and favicon during the setup wizard:

We tested this again and it appears to be working correctly, including in your own video demonstration. This may have been related to caching or a temporary save issue during setup. However, we will still review the setup flow again and improve reliability further in the upcoming 1.5.8 update to avoid inconsistent behavior.

2. About the menu/actions compatibility with third-party plugins:

Thank you for the detailed explanation and screenshots. You are correct that some plugin-added menu items and actions still require additional compatibility improvements. We already started working on a broader compatibility layer for custom admin toolbar/dropdown actions and we plan to improve this further in version 1.5.8.

3. Thank you also for the suggestions regarding:

• hiding the “Connect Account” button,
• dashboard redirect visibility,
• and additional interface visibility controls.

Advanced branding and white label customization are currently part of the licensed version, mainly to help support ongoing development, maintenance, compatibility improvements, and long-term support for YOOAdmin.

Our goal is still to keep the free version very complete and fully usable for normal users, while more advanced agency/client customization options remain part of the licensed experience.

More details about the available plans:
https://www.yooadmin.io/pricing/

And thank you again for the positive feedback about 1.5.7 , we are really glad you liked the improvements 🙂

• This reply was modified 2 days, 18 hours ago by Rami Obeidat.

Thanks again for the detailed feedback and testing 🙌

The Code Snippets dark mode compatibility issues you reported have now been improved in YOOAdmin 1.5.7, including better support for code editor selection visibility, toggle states, token fields, and classic plugin admin pages inside adaptive dark mode.

We also made several broader improvements to the adaptive dark mode engine across classic WordPress admin screens and third-party plugins.

Since the remaining feedback is now being discussed in your newer thread, I’m marking this topic as resolved so we can continue tracking future improvements there more cleanly.

Thanks again for all the thoughtful reports and suggestions ✨

Thanks for the report and the detailed explanation.

We were able to reproduce the issue and have already fixed it. The problem was related to compatibility between the WordPress Customizer and certain theme/admin styles (including Hestia), which affected dark mode rendering and caused slower loading behavior inside customize.php.

We have also released the new YOOAdmin 1.5.6 update which includes this fix.

Thank you again for reporting it 🙌

Just a quick update

Version 1.5.5 is being released today and includes the first version of a new dark mode compatibility engine we recently built for YOOAdmin.

The system is designed to automatically detect and adapt many interface colors across WordPress admin areas and third-party plugins to create a much more consistent dark mode experience overall.

In our current testing, it already improves compatibility across a very large number of plugins and covers most common interface scenarios automatically. We are still actively improving and expanding it further, and it will continue receiving updates and refinements in the coming days and future releases.

Your feedback and detailed testing genuinely had a big impact on this development direction because maintaining a good experience for users like you who rely heavily on dark mode is very important to us.

We would be very happy to hear your thoughts once you test the new update 🙂

Thank you so much again for the detailed video and testing
The video was genuinely very helpful for us and contained many valuable observations and improvement ideas. We will absolutely do our best to improve and resolve as many of these issues as possible in upcoming updates.

We also noticed that some features may have been missed during testing, which is completely understandable since YOOAdmin now includes many workspace customization options.

For example, inside Workspace Edit Mode you can fully customize the workspace layout, move plugins between sections using drag and drop, move cards between sections, and even hide the right widget area entirely. These features are explained during the interactive onboarding tour shown after installation, but it is possible the welcome popup and tour were skipped during setup

Regarding the default WordPress dashboard widgets, we currently do not fully support the original WordPress widgets because many of them visually conflict with the Studio Hub workspace design and dark mode system. Instead, we created a developer-friendly system and documentation that allows plugin developers to integrate properly with YOOAdmin using custom sections and Edit Mode compatibility.

About the tooltip/banner behavior at the top of the page, the current design is intentional because we want users to be able to quickly access the related settings page and optionally convert these admin banners into notifications instead of showing them directly in the workspace. However, we completely agree that the close icon should also properly support dark mode and we will improve this.

Regarding the original WordPress homepage/dashboard, there is also an option inside YOOAdmin settings that allows users to open the default WordPress dashboard instead of the YOOAdmin workspace homepage when clicking Home.

And finally, regarding global dark mode support, we are honestly very happy to receive feedback like yours. Studio Hub and the new dark mode system were introduced recently in version 1.5 and are still actively evolving. Feedback like this is extremely valuable during development and genuinely helps us improve compatibility and overall user experience across WordPress admin areas.

There were also many other important points mentioned in your video that we noted internally and will continue improving over time.

Thank you again for all the effort and time you spent testing YOOAdmin and sharing such detailed feedback with us

Thank you for clarifying

Yes, we understand exactly what you mean now. We actually already improved this experience inside the YOOAdmin Plugin Manager in the Extended version, which is currently completely free.

For the ww.wp.xz.cn repository version, we try to stay closer to the default WordPress experience and avoid replacing some core plugin management interfaces too aggressively in order to remain compatible with ww.wp.xz.cn guidelines and expectations.

That said, we are still actively improving the original WordPress plugin details popup, dark mode coverage, and overall compatibility across the default admin experience as much as possible. Several improvements related to this are already being worked on for upcoming updates.

Thank you again for reporting this and helping us improve the experience