Is It Safe to Use Block Templates on an Older WordPress Theme?
Last month I clicked something called “Editor” inside the Appearance menu of a 4-year-old classic theme. I just wanted to see what it did. 30 seconds later, my header had lost its logo, the sidebar had moved to the bottom of the page, and the Customizer settings I’d spent an afternoon adjusting were no longer applying. I ended up needing to turn off block templates in WordPress to get the original layout back.
That “something” was block templates. And if you’re reading this because the same thing happened to you, the good news is your theme isn’t broken. You can turn off block templates in WordPress and get your old layout back in about 5 minutes.
I’ll walk through what block templates actually are, how to tell if your site has them switched on, what tends to break, and the safest way to roll back to the classic Customizer. No code editing required for the easy fix.
What are “block templates” and why is my old theme suddenly using them?
Block templates are a feature WordPress added in version 6.0 that lets you edit your header, footer, and other site-wide layout pieces using the same block editor you use to write posts. On a fully block-based theme like Twenty Twenty-Five, this is how the whole site gets built. There’s no Customizer at all.
The catch is that WordPress also lets classic themes opt into part of this system. Theme authors call it “hybrid” or “classic with block template support.” When that’s switched on, you’ll see an “Editor” link under Appearance, even though your theme was built around the Customizer.
The risk is that classic themes weren’t designed for the Site Editor. The PHP that builds your header and footer was written before block templates existed. So when WordPress hands template control over to the block editor, the original PHP gets bypassed, and the visual result often looks nothing like the design you signed up for.
How do I tell if my theme is currently using block templates?
There are 2 quick checks. Either one will tell you in 10 seconds.
The first check is the Appearance menu. Log into your dashboard and hover over Appearance. If you see “Editor” listed alongside “Customize,” your theme has block template support active. A pure classic theme only shows “Customize,” “Widgets,” “Menus,” and “Themes.”
The second check is inside the block editor itself. Open any page or post for editing. Click on any block and look at the right sidebar. If you see a section labeled “Template” with an “Edit template” button, block templates are switched on for your site.
If neither of those checks turns up anything, you’re safe. Your theme is running in pure classic mode and this article isn’t your problem. You might still want to bookmark it for the day a theme update changes things.
Why you might want to turn off block templates in WordPress
This is where I learned the hard way. The damage tends to fall into 4 buckets.
First, layouts that rely on classic theme PHP get bypassed. If your theme used header.php to load the logo, navigation, and search bar in a specific order, the Site Editor can replace all of that with an empty block template. You’re left staring at a blank header.
Second, Customizer settings stop applying. Colors you picked, fonts you uploaded, header heights you adjusted – the block template doesn’t read any of that. It uses its own theme.json or block style settings instead.
Third, widget areas can disappear. Classic themes often define sidebars and footer widget areas in PHP. Block templates use block-based widget areas, and they don’t always map onto the old definitions. Your “Footer Widget Area 2” might just stop showing up.
Fourth, header and footer styling can lose its theme-defined polish. Spacing, dividers, the sticky header behavior – any of those can disappear because the original CSS was scoped to PHP-rendered markup that’s no longer there.
Not every classic theme breaks in all 4 ways. But if you turned on block templates and something looks off, those are the 4 places to look.
How do I turn off block templates in WordPress and go back to my Customizer?
The fastest fix is a free plugin called Disable Gutenberg. Install it from Plugins > Add New, activate it, and visit Settings > Disable Gutenberg. Tick the box to disable the block editor everywhere. This stops the Site Editor from loading and brings the Customizer back as the primary design tool.
If you only want to disable the Site Editor (not the post block editor), you have 2 lighter options. The free plugin Classic Widgets turns off the block-based widget editor and brings back the old drag-and-drop one. The plugin Classic Editor (the official one from the WordPress team) does the same for posts and pages.
For the technical option, you can add one line to your wp-config.php file via your hosting File Manager:
define( 'GUTENBERG_USE_LEGACY_TEMPLATES', true );
I only recommend the wp-config edit if you’re already comfortable opening that file. The plugin route is safer for most beginners and you can deactivate it instantly if anything goes sideways. My guide on where the WordPress Customizer went covers what you should see in the menu once block templates are off.
After you’ve turned off block templates, refresh your front end. The header, footer, and widget areas should snap back to whatever your theme was rendering before. If they don’t, the next section explains what often causes that.
My theme worked fine before – what changed?
If your site was running cleanly for years and suddenly the layout looks wrong, one of 3 things probably happened.
The most common cause is a WordPress core update. Versions 6.0 through 6.4 enabled block template features by default for classic themes that had quietly added support in their functions.php. You didn’t change anything, but the underlying flag flipped.
The second cause is a theme update. Theme authors sometimes add add_theme_support( 'block-templates' ) in a routine update without making it loud in the changelog. The next time you updated your theme, that one line opted you in.
The third cause is a plugin. Starter site importers, page builders, and some “WordPress optimization” plugins occasionally toggle block-related flags during their setup wizard. If you installed something new in the last week and your layout broke after, that’s a strong suspect.
To narrow it down, check Dashboard > Updates for the date of the last theme or core update. If it lines up with when things broke, you’ve found your culprit. From there, rolling back the theme update or reactivating your Customizer setup is usually enough to undo the damage.
When should I migrate to a block theme instead?
I’m not going to push you toward a block theme. Plenty of people use classic themes happily and there’s no rule that says you have to migrate. But there are 3 situations where a migration is genuinely the easier path.
The first is if you’re already mostly using block templates and they work fine for you. If your “broken” experience was actually just the unfamiliar Site Editor and not real damage, leaning into a block theme designed for that workflow will feel less awkward than fighting your classic theme.
The second is if your classic theme is unmaintained. If the author hasn’t pushed an update in 2 years, the risk of compatibility issues with future WordPress versions only goes up. Migrating now, on your schedule, is less stressful than migrating later when something actually breaks.
The third is if you keep hitting block-vs-classic conflicts. If every WordPress update brings new layout headaches, the constant fixes start to cost more time than a one-time migration would. When you do shop for a block theme, pick one that’s actively maintained and built for full site editing from the ground up rather than a classic theme with bolted-on support.
If none of those 3 apply to you, stay on your classic theme. It’s the right call.
Should I just stay on my classic theme without block templates?
Yes, for most beginners I talk to, this is the right answer. The Customizer is still fully supported in WordPress through 2026 and the team has stated they’ll keep it around as long as classic themes exist. That’s not going away in the foreseeable future.
Stay on your classic theme without block templates if 3 things are true. One: it works well for the kind of site you’re running. Two: the theme author still ships updates (check the last update date on the theme page). Three: you don’t need full site editing features like reusable patterns or block-based templates.
If all 3 are true, turning off block templates and using only the Customizer is a fine long-term setup. You’re not falling behind. You’re just using the tool that fits your site.
The only thing I’d add: keep the Disable Gutenberg or Classic Editor plugin installed and active so a future WordPress update doesn’t quietly switch things back on. I learned that lesson the slow way.
FAQs
How do I disable the Template Editor in WordPress?
If you’re using a classic theme, I usually recommend using a snippet of code in your functions file (remove_theme_support) to completely turn off block templates in WordPress so clients don’t accidentally break their layouts.
How do I turn off the Site Editor (Gutenberg) in WordPress?
The Site Editor is tied to Block Themes. If you want to turn it off completely, you have to switch back to a Classic Theme. I’ve found this is the only reliable way to get the old Customizer back.
Can I delete default block templates?
You can’t delete the default templates that come bundled with your theme through the WordPress dashboard. I can only clear my customizations to reset them back to how the theme author designed them.
What happens if I use a block template on a classic theme?
When I tried this, the block template completely hijacked my page layout, ignoring the header and footer I had set up in my classic theme’s Customizer. It’s safe, but it requires rebuilding those parts.
You don’t have to use block templates
Here’s what I want you to take away. Block templates are a feature, not a requirement. If you’re on a classic theme and turning them on broke your layout, the answer is to turn them off, not to throw out the theme.
Install Disable Gutenberg or Classic Editor, refresh your front end, and you’ll be back to the Customizer in 5 minutes. From there, you can decide on your own timeline whether to ever migrate to a block theme. That’s a choice you make once your site is working again, not while you’re panicking about a missing header.
Your classic theme isn’t outdated. It’s just a different tool, and WordPress still supports it.