Hello @skytthe,
Thank you for sharing the detailed information.
In this update, the “Both Backend and Frontend” CSS location was corrected. Previously, an internal value typo meant CSS snippets configured for this location were effectively loaded only on the frontend. With the current code, snippets using run_at = everywhere are now also loaded in /wp-admin/.
This could explain styling changes on Posts, Pages, Media, and other admin screens, particularly if an active CSS snippet contains broad selectors such as body, .wrap, table, .media, ul, or .button.
Could you please check:
- Go to FluentSnippets > Styles.
- Review active CSS snippets configured for Both Backend and Frontend.
- If the CSS is only intended for the frontend, change it to Frontend.
- If admin styling is intentional, consider scoping the CSS to the specific admin screen/component instead of using broad selectors.
- Clear any page cache, object cache, and OPcache after making the change.
If the issue persists, please share the CSS snippet you are currently using along with a screenshot showing the affected admin area. This will help us investigate the issue further.
Please let me know the update.
Best regards!
Ruman Ahmed.
Thanks, your explanation and solution was spot on.
I had a snippet to be anywhere, and changed it to frontend. After that was everything OK.
Thanks for the support, and your wonderful plugin 🙂