Title: WordPress 6.9 broke site layout Last modified: February 5, 2026 --- # WordPress 6.9 broke site layout * [theinfoprovider](https://wordpress.org/support/users/theinfoprovider/) * (@theinfoprovider) * [4 months, 1 week ago](https://wordpress.org/support/topic/wordpress-6-9-broke-site-layout-crewbloom/) * After the automatic update to WordPress 6.9 (and/or Gutenberg plugin 19.5), the entire front-end design of our site is completely broken: - CSS seems not to load properly (many styles missing) - Layout is collapsed, fonts are wrong, spacing is off - Hero sections, buttons, and custom styling no longer appear as before - Happens on all pages, tested in Chrome, Firefox, Safari, and on mobile - Clearing all caches (server + Cloudflare + browser) didn’t help - Disabling all plugins except the theme didn’t fix it * Site was working perfectly on 6.8.3. This is a live Remote Staffing Agency website and the broken design is currently visible to all visitors. * Any quick fix or rollback advice for 6.9-specific regression? Thank you! - This topic was modified 4 months, 1 week ago by [Steven Stern (sterndata)](https://wordpress.org/support/users/sterndata/). Reason: removed redundant url; removed nsfw. spam? * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fwordpress-6-9-broke-site-layout-crewbloom%2Fpage%2F3%3Foutput_format%3Dmd&locale=en_US) to see the link]_ Viewing 9 replies - 31 through 39 (of 39 total) [←](https://wordpress.org/support/topic/wordpress-6-9-broke-site-layout-crewbloom/page/2/?output_format=md) [1](https://wordpress.org/support/topic/wordpress-6-9-broke-site-layout-crewbloom/?output_format=md) [2](https://wordpress.org/support/topic/wordpress-6-9-broke-site-layout-crewbloom/page/2/?output_format=md) 3 * [Lucas Karpiuk](https://wordpress.org/support/users/karpstrucking/) * (@karpstrucking) * [3 months, 3 weeks ago](https://wordpress.org/support/topic/wordpress-6-9-broke-site-layout-crewbloom/page/3/#post-18758001) * [@wildworks](https://wordpress.org/support/users/wildworks/) your fix works for me, thank you! * [@westonruter](https://wordpress.org/support/users/westonruter/) encountered this on a non-Elementor site (custom theme) * [@jorbin](https://wordpress.org/support/users/jorbin/) here’s an example of used code not working after 6.9 * ```wp-block-code add_action('wp_footer', 'my_footer_scripts');function my_footer_scripts() { if (is_front_page()) { wp_enqueue_style('slick', get_template_directory_uri() . "/assets/css/slick.css"); wp_enqueue_style('slick-theme', get_template_directory_uri() . "/assets/css/slick-theme.css"); wp_enqueue_style('home-page', get_template_directory_uri() . "/assets/css/home.css"); }} ``` * [Ingo Steinke (openmindculture)](https://wordpress.org/support/users/openmindculture/) * (@openmindculture) * [3 months, 3 weeks ago](https://wordpress.org/support/topic/wordpress-6-9-broke-site-layout-crewbloom/page/3/#post-18758479) * WordPress 6.9 introduced breaking changes comparable to the WordPress 6.2 update in 2023 when shortcodes stopped working on many sites and some default block styles changed for no good reason. I don’t know why WordPress 6.9 had to be released in December, and why new experimental blocks are an opt-out and not an opt-in feature. The new blocks alone would have been enough to confuse some website editors, but I had to fix multiple regressions or incompatibilities after the WordPress 6.9 update on several customers’ websites. Custom block variations vanished from the block inserter, while new experimental blocks and core block variations appeared instead. Enqueueing custom block variation styles in the backend seems to have changed slightly. * So have the cache keys, temporarily breaking several popular third-party plugins, and the default styles of wp-columns seem to have changed. The latter issue is kind of my own fault: we should never rely on default display:flex when we can just add it explicitly, even more so in a classic / hybrid theme where we write our own markup and so we can add unambiguous class names to avoid or at least reduce undesired side effects. * Lesson learned: if we have to support WordPress in 2026 and beyond, we’d better improve our restrictions, add tests, test early, and raise our invoices and rates accordingly. I wonder if customers will understand though, when every marketing department claims that “AI will do everything” now. * [Weston Ruter](https://wordpress.org/support/users/westonruter/) * (@westonruter) * [3 months, 3 weeks ago](https://wordpress.org/support/topic/wordpress-6-9-broke-site-layout-crewbloom/page/3/#post-18758739) * [@karpstrucking](https://wordpress.org/support/users/karpstrucking/) I cannot reproduce the issue you’re describing. I put together a [test plugin](https://gist.github.com/westonruter/30db2216eef07600cb1762ee8be67f18) which does the same as you showed: * ```wp-block-code add_action( 'wp_footer', static function () { if ( is_front_page() ) { wp_enqueue_style('enqueued-at-wp-footer', plugins_url( 'enqueued-at-wp-footer.css', __FILE__ ) ); } }); ``` * The enqueued CSS file `enqueued-at-wp-footer.css` is as follows: * ```wp-block-code body:after { content: "Stylesheet successfully enqueued at wp_footer!"; background: lime; padding: 1em; position: fixed; bottom: 0; right: 0;} ``` * On the front page, I successfully see the lime green message coming from the stylesheet: * > Stylesheet successfully enqueued at wp_footer! * I also see the stylesheet appearing in the `HEAD` as expected due to the hoisting in WP 6.9: * ```wp-block-code ``` * You can [try it on Playground](https://playground.wordpress.net/?blueprint-url=https%3A%2F%2Fgist.githubusercontent.com%2Fwestonruter%2F30db2216eef07600cb1762ee8be67f18%2Fraw%2Fblueprint.json). - This reply was modified 3 months, 3 weeks ago by [Weston Ruter](https://wordpress.org/support/users/westonruter/). * [Lucas Karpiuk](https://wordpress.org/support/users/karpstrucking/) * (@karpstrucking) * [3 months, 3 weeks ago](https://wordpress.org/support/topic/wordpress-6-9-broke-site-layout-crewbloom/page/3/#post-18759353) * [@westonruter](https://wordpress.org/support/users/westonruter/) for this particular site the issue was resolved using the snippet provided by [@wildworks](https://wordpress.org/support/users/wildworks/) * the site uses an older custom theme, so my guess is that it’s doing something elsewhere in the theme that isn’t “the WP way” but was, until 6.9, still working * [Weston Ruter](https://wordpress.org/support/users/westonruter/) * (@westonruter) * [3 months, 3 weeks ago](https://wordpress.org/support/topic/wordpress-6-9-broke-site-layout-crewbloom/page/3/#post-18759894) * [@karpstrucking](https://wordpress.org/support/users/karpstrucking/) As opposed to using the `should_load_separate_core_block_assets` filter, I [suggest](https://wordpress.org/support/topic/wordpress-6-9-broke-site-layout-crewbloom/page/2/#post-18746550) instead using the **[​Load Combined Core Block Assets](https://wordpress.org/plugins/load-combined-core-block-assets/)** plugin to do the same. This will allow you to easily turn off the workaround when the issue is fixed, and be able to test the fix in core before turning deactivating the plugin. * Additionally, it would be helpful to have details about how your theme is constructed to facilitate reproducing the issue. * [DevAny](https://wordpress.org/support/users/devanykr/) * (@devanykr) * [2 months, 2 weeks ago](https://wordpress.org/support/topic/wordpress-6-9-broke-site-layout-crewbloom/page/3/#post-18793606) * design breaks when using grid blocks. CSS value for is-layout-grid is empty. Disabling the admin toolbar restores the grid to normal. wow? * add_filter( ‘should_load_separate_core_block_assets’, ‘__return_false’, 100 ); * The above code worked. * Elementor is not involved. * [Weston Ruter](https://wordpress.org/support/users/westonruter/) * (@westonruter) * [2 months, 2 weeks ago](https://wordpress.org/support/topic/wordpress-6-9-broke-site-layout-crewbloom/page/3/#post-18794422) * [@devanykr](https://wordpress.org/support/users/devanykr/) Please use the **[​Load Combined Core Block Assets](https://wordpress.org/plugins/load-combined-core-block-assets/)** plugin instead (which involves the same code), since it makes it easier to test whether the issue is fixed once 6.9.1 is released. * It would be helpful if you could test [the fix](https://github.com/WordPress/wordpress-develop/pull/10601) for the [ticket](https://core.trac.wordpress.org/ticket/64354) as well. Not sure if you’re set up to do that. * [Pacotole](https://wordpress.org/support/users/pacotole/) * (@pacotole) * [2 months ago](https://wordpress.org/support/topic/wordpress-6-9-broke-site-layout-crewbloom/page/3/#post-18810712) * Do you know if the problem is solved with the WordPress 6.9.1 update? * [Silver88](https://wordpress.org/support/users/silvan/) * (@silvan) * [2 months ago](https://wordpress.org/support/topic/wordpress-6-9-broke-site-layout-crewbloom/page/3/#post-18810718) * [@xwolf](https://wordpress.org/support/users/xwolf/) Thank you! That fix is the only thing that works! * Hopefully 6.9.1 solved these issues. Viewing 9 replies - 31 through 39 (of 39 total) [←](https://wordpress.org/support/topic/wordpress-6-9-broke-site-layout-crewbloom/page/2/?output_format=md) [1](https://wordpress.org/support/topic/wordpress-6-9-broke-site-layout-crewbloom/?output_format=md) [2](https://wordpress.org/support/topic/wordpress-6-9-broke-site-layout-crewbloom/page/2/?output_format=md) 3 The topic ‘WordPress 6.9 broke site layout’ is closed to new replies. ## Tags * [release](https://wordpress.org/support/topic-tag/release/) * [update](https://wordpress.org/support/topic-tag/update/) * In: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) * 41 replies * 27 participants * Last reply from: [Silver88](https://wordpress.org/support/users/silvan/) * Last activity: [2 months ago](https://wordpress.org/support/topic/wordpress-6-9-broke-site-layout-crewbloom/page/3/#post-18810718) * Status: not a support question ## Topics ### Topics with no replies ### Non-support topics ### Resolved topics ### Unresolved topics ### All topics