1bmckots

We fixed this manually on our Dev server until you release an update, but here is what broke after updating to WordPress 6.9 so your team can investigate.

After the update, several Happy Addons widgets stopped loading their front-end CSS. Everything still works correctly on our production site (still on WP 6.8) and inside the Elementor editor, but the front-end output is missing key styling.What broke:

1. Advanced Tabs (inside Mega Menu)
   • All tab panels appear at once (stacked vertically).
   • Mobile tab titles show on desktop.
   • The entire tab layout loses its styling.
2. List/Icon styles
   • Any widget using <li> items with icons loses styling.
   • Browser bullets appear.
   • Icon + text alignment breaks.
   • This happens both inside the Mega Menu and inside the Breadcrumb widget.
3. Breadcrumbs widget
   • Breadcrumbs render as a vertical bulleted list.
   • Separators appear on their own lines.
   • All default HA styles are missing.

Thanks. I tested as well and still not working in Chrome or Safari. I just submitted a ticket.

I just received your submission, so I went into Incoginto and tried myself, and I’m still having the same issue. Just spinning..I can create a Loom if needed.

Hi, fatal error still happening. This time with updating to 19.0. Different site, different set of plugins and different theme.

Error Details
=============
An error of type E_ERROR was caused in line 228 of the file /nas/content/live/XXXXX/wp-content/plugins/wordpress-seo/src/loader.php. Error message: Uncaught Error: Class 'Yoast\WP\SEO\Routes\Configuration_Workout_Route' not found in /nas/content/live/XXXXX/wp-content/plugins/wordpress-seo/src/loader.php:228
Stack trace:
#0 /nas/content/live/XXXXX/wp-content/plugins/wordpress-seo/src/loader.php(212): Yoast\WP\SEO\Loader->conditionals_are_met('Yoast\\WP\\SEO\\Ro...')
#1 /nas/content/live/XXXXX/wp-includes/class-wp-hook.php(307): Yoast\WP\SEO\Loader->load_routes(Object(WP_REST_Server))
#2 /nas/content/live/XXXXX/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters(NULL, Array)
#3 /nas/content/live/XXXXX/wp-includes/plugin.php(476): WP_Hook->do_action(Array)
#4 /nas/content/live/XXXXX/wp-includes/rest-api.php(561): do_action('rest_api_init', Object(WP_REST_Server))
#5 /nas/content/live/XXXXX/wp-content/mu-plugins/wpe-cache-plugin/cache-db-settings.php(81): rest_get_server()
#6 /nas/content/live/XXXXX/wp-content/mu-plugins/wpe-cache-plugin/cache-db-settings.php(142): wpengine\cache_plugin\C

Hi Michael,

No, I have never used the Wincher integration on any of our sites.

Secondly, this has happened up with the upgrade to 18.6 on several sites, but as mentioned, it happens in ‘almost’ EVERY Yoast version upgrade that we implement, on several of our sites. There is no specific site or pattern that I can see that would lead me to believe it is a plugin or theme conflict. It clearly seems like a larger broader scale issue with Yoast in general and I see several people reporting the same errors.

One solution I read by someone in your support was deleting Yoast and reinstalling every time there is an update. Is this a suggested fix? Will this cause any data to be deleted (meta tags, etc)?

I would really appreciate more help here.

Thank you.