Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting

WPBakery Not Showing Backend Editor: Causes and How to Fix It

WPBakery Not Showing Backend Editor: Causes and How to Fix It

Short answer

The WPBakery backend editor usually does not show because the block editor is active, the post type is not enabled in Role Manager, or your role has the backend editor turned off. Check WPBakery's General Settings and Role Manager first, then look for JavaScript errors if the editor stays blank.

Key takeaways

  • A missing button is usually a settings problem.
  • A blank editor is usually a script or conflict problem.
  • WPBakery is often enabled for pages only by default.
  • Role Manager controls post types and backend editor access per role.
  • Custom post types need editor support for WPBakery to appear.
  • Outdated theme-bundled versions often break after WordPress updates.

Why is the WPBakery backend editor not showing?

The WPBakery backend editor usually does not show because the block editor is active, the post type or your role is not enabled in Role Manager, or a JavaScript error stops it loading.

There are two different problems that people describe the same way. In one, the Backend Editor button is missing entirely. In the other, the button is there but the editor area stays blank or never finishes loading.

Missing buttons are usually settings problems. Blank editors are usually script or conflict problems.

WPBakery's own FAQ on using the builder on posts and custom posts covers the most common settings cause. For other builder issues, see our guide to WPBakery Page Builder not working.

Is the block editor hiding the backend editor?

WPBakery's backend editor is designed around the classic editing screen, so on sites using the block editor the button may be missing or placed differently until you switch editors or change WPBakery's Gutenberg setting.

WPBakery includes an option in its general settings to disable the block editor. Go to WPBakery Page Builder > General Settings and look for the Gutenberg-related setting.

Alternatively, install the Classic Editor plugin, which restores the older editing screen for all or selected post types.

Our guide on how to go back to the classic editor explains the options.

If you only want the change for one post type, see how to disable Gutenberg for a post type.

After switching, reload the edit screen. The Backend Editor and Frontend Editor buttons should appear above the content area.

Is the post type enabled in the Role Manager?

By default WPBakery is often enabled for pages only, so the backend editor will not appear on posts, products or custom post types until you enable them in the Role Manager.

  1. Go to WPBakery Page Builder > Role Manager.
  2. Open the settings for your user role, such as Administrator.
  3. Find the Post types option.
  4. Choose all post types, or choose custom and tick the ones you need.
  5. Click Save Changes.
  6. Reload the post editor.

Repeat this for every role that needs the builder, such as Editor or Shop Manager.

Changes in the Role Manager apply straight away, but a browser or admin page cache can show the old edit screen. Do a hard refresh after saving.

If the settings look correct but the button is still missing, check whether a second plugin also controls roles, such as a role editor plugin. Two tools changing the same capabilities can override each other.

Is the backend editor disabled for your role?

The Role Manager also controls whether each role can use the backend editor at all, so if it is disabled for your role, the button will not appear even on enabled post types.

In the same role settings, find the Backend editor option. Set it to enabled, or enabled and default if you want WPBakery to open automatically.

If you are not an administrator, ask one to check your role. Our guide to WordPress user roles explains how roles and capabilities work.

CauseWhere to checkFix
Block editor activeWPBakery General Settings or Classic Editor pluginDisable block editor for that post type
Post type not enabledRole Manager, Post typesEnable all or tick the post type
Role lacks accessRole Manager, Backend editorEnable for that role
Custom post type lacks editor supportTheme or plugin codeAdd editor support
JavaScript errorBrowser consoleFind and fix conflict
Outdated bundled versionTheme or plugin updatesUpdate WPBakery

Does the custom post type support the editor?

WPBakery needs the standard content editor to attach to, so a custom post type registered without editor support will never show the backend editor.

Developers control this with the supports argument when registering a post type. The WordPress register_post_type reference explains that editor must be included for the content editor to appear.

If the post type comes from a plugin, check that plugin's settings for an option to enable the editor. If it comes from your theme, ask the theme developer.

Adding support yourself is possible with a small code snippet in a child theme, but test it on staging first.

Is a JavaScript error stopping the editor?

When the button exists but the editor stays blank, grey or stuck loading, a JavaScript error from another plugin, the theme or an outdated WPBakery version is the usual cause.

Open the browser developer tools and check the console. Chrome's Console documentation explains how. Errors often name the plugin or script that failed.

Common culprits include optimisation plugins that minify or combine admin scripts, outdated add-ons for WPBakery, and themes that bundle an old builder version.

Test on a staging copy with a default theme and only WPBakery active. Our guide to fixing plugin conflicts explains how to narrow down the cause.

Is your WPBakery version outdated?

Themes often bundle WPBakery and update it only when the theme updates, so an old bundled version can break after a WordPress update and stop the backend editor loading.

Check the version under Plugins > Installed Plugins. Then check your theme's update notes to see whether a newer WPBakery is included.

Update the theme first, then use the theme's plugin installer to update WPBakery. If your theme is abandoned, you may need your own WPBakery licence to get updates.

Older builder versions also relied on older jQuery behaviour. Modern WordPress removed some of that, which is a known cause of blank editors.

Could server limits or security rules be involved?

Yes, low PHP memory, short execution times or a security rule that blocks admin requests can stop large layouts from loading in the backend editor.

Raise the PHP memory limit if pages with many elements fail while small pages work. Our guide on how to increase the PHP memory limit shows the steps.

Turn on WordPress debugging to catch PHP errors. The debugging documentation explains the settings to use.

Ask your host whether ModSecurity or another firewall blocked requests from the editor. Their logs will show this quickly.

What quick checks should you try first?

Clear your browser cache, try a private window, reload the editor, and check Screen Options and the editor tabs before changing deeper settings.

Browser extensions such as ad blockers sometimes interfere with admin scripts. A private window with extensions disabled rules this out.

On the classic edit screen, make sure the Visual and Text tabs are working. If the main editor itself is broken, WPBakery cannot load either.

If none of these steps help, our general guide to fixing a page builder that will not load covers more causes.

How do you stop this happening again?

Keep WPBakery and your theme updated together, test updates on staging first, and note your Role Manager settings so you can restore them quickly.

Avoid running admin-side minification from optimisation plugins. It saves little and often breaks builders.

If you are planning a redesign, consider whether to keep WPBakery long term. Our comparison of Gutenberg vs page builders can help you decide.

If you stay with WPBakery, our guide on how to use WPBakery Page Builder covers the editor basics, including when to use the backend editor and when the frontend editor is quicker.

Frequently asked questions

Why does WPBakery only work on pages?

WPBakery is often enabled for pages only by default. Go to the Role Manager, open your role, and set Post types to all or tick the specific post types you need, such as posts or products. Save the changes and reload the editor.

Do I need the Classic Editor plugin for WPBakery?

Not always. WPBakery includes a setting to disable the block editor, which restores the classic screen where its backend editor appears. The Classic Editor plugin is another way to do the same, with more control per post type.

Why is the WPBakery backend editor blank?

A blank or grey editor usually means a JavaScript error, often from an optimisation plugin, an outdated WPBakery add-on or an old bundled version of the builder. Check the browser console, update everything, and test for plugin conflicts on staging.

Can a user role stop the backend editor showing?

Yes. The Role Manager lets admins enable or disable the backend editor for each role. If it is disabled for your role, the button will not appear. An administrator can change the setting for that role.

Why is WPBakery missing on my custom post type?

The post type may not be enabled in the Role Manager, or it may have been registered without editor support. Enable it in the Role Manager first. If it still does not appear, the post type needs editor support added in code or plugin settings.

Sources

  1. I can not use WPBakery Page Builder on posts and custom posts WPBakery Knowledge Base
  2. Classic Editor WordPress.org Plugin Directory
  3. register_post_type() WordPress Developer Resources
  4. Debugging in WordPress WordPress Developer Resources
  5. Console overview Chrome for Developers

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.