Why are my styles missing?

WordPress 6.9 Is Doing Something Weird With Your Styles

Well, WordPress 6.9 dropped on December 2nd, and if your website suddenly looks like it forgot to get dressed this morning, you’re not alone.

What’s Happening

The WordPress core team made some performance improvements to how stylesheets load. The short version: they increased the inline style limit from 20KB to 40KB and changed how block styles load on-demand for classic themes. These are genuinely good changes for page speed.

The problem is that some themes and plugins—Elementor sites in particular—are now missing CSS. Layouts are collapsing. Fonts are wrong. Hero sections have wandered off somewhere. It’s the kind of thing that makes you stare at your screen and quietly say “huh” for longer than you’d like to admit.

The Fix

There’s a one-line code snippet that tells WordPress to load block styles the old way:

add_filter( 'should_load_separate_core_block_assets', '__return_false', 100 );

You can drop this into your theme’s

functions.php

file or create a simple must-use plugin. If those words mean nothing to you, that’s okay. Keep reading.

Your Options

Option 1: Turn off automatic updates and wait

This is the “I’ll deal with it when they fix it” approach. WordPress will patch this. They always do. In the meantime, you can disable auto-updates for core and stay on 6.8.3 until the dust settles.

To disable auto-updates, add this to your

wp-config.php:

define( 'WP_AUTO_UPDATE_CORE', false );

Option 2: Apply the fix yourself

If you’re comfortable editing theme files or creating a must-use plugin, the code snippet above should sort you out. Back up your site first. Always back up your site first.

Option 3: Hire someone to fix it

If you’d rather not touch code, we can apply the patch for you. It takes us just a few hours to get in there, verify the issue, apply the fix, and test everything. Our rate for this kind of quick fix is $500.

Contact us to schedule a patch.

Should You Panic?

No. This is just WordPress being WordPress. The open-source sausage gets made in public, and sometimes a piece of gristle gets through. The core team is aware of the issue, Elementor is working on compatibility updates, and life will go on.

If your site looks fine, congratulations. You can close this tab and get back to your day.

If your site looks like a ransom note made of mismatched fonts and collapsed columns, well, now you know why.


Design Web Louisville helps businesses and nonprofits keep their WordPress sites running smoothly. If you’d rather not think about things like inline style limits and block asset loading, we offer monthly maintenance plans that handle updates, backups, and the occasional “WordPress is doing something weird” situation.

Navigating the Choppy Waters of WordPress 6.4: and why you may want to revert it back to 6.3

Today was a day for the books – the kind of day that serves as a stark reminder that in the digital world, not all updates come bearing gifts. If you’re part of the WordPress community, you might want to buckle up because version 6.4 has hit a snag—a bug, to be precise. Before you hit that update button, let’s talk about why 6.4 might be a version to skip for now.

It seems that 6.4 has a penchant for breaking PHP cURL, an essential feature for WordPress sites that allows them to communicate with other servers. What does this mean for you? Well, if you’re looking to install new themes or update your existing plugins, you might find yourself at a dead end.

The WordPress core team is not only aware but also already on deck, working hard to patch things up. In the digital seas, it’s not about avoiding all storms—it’s about weathering them with grace. And the community’s response? Nothing short of nimble.

For those interested in the nitty-gritty, or if you’re feeling particularly tech-savvy today, dive into the depths of the issue on GitHub (https://github.com/WordPress/Requests/issues/838) or float over to the WordPress support forums (https://wordpress.org/support/forum/how-to-and-troubleshooting/). Here, you’ll find fellow navigators of the web discussing workarounds and sharing updates in real-time.

If your site has already set sail with 6.4, it’s time to turn the ship around. Rolling back to the safe harbor of 6.3 is your best bet until the storm passes. And while you’re at it, make sure to drop anchor by disabling core updates in your wp-config.php file—just to ensure you don’t get caught in the squall again.

But fear not, intrepid web wanderers, for this tale has a silver lining. The problem has been identified and fixed in the upcoming WordPress 6.4.1. The core team has even made adjustments to the WordPress.org mothership to help afflicted sites update smoothly, despite the troubled waters.

Interestingly, this digital tempest seems to have only rocked a subset of sites, with many of the larger hosting providers bearing the brunt of it. It’s a reminder that sometimes, size does matter—especially when navigating the high seas of the internet.

So, what’s the moral of this story? Stay vigilant, keep your site’s lifejackets close (backups, folks!), and remember that in the world of updates, sometimes patience is more than just a virtue—it’s a necessity. Keep a weather eye on the horizon for WordPress 6.4.1, and until then, happy sailing!

Curious about what people are saying about this on Reddit and other WordPress Community Forums?

Read more here: