WPBakery fix
Can't Update the WPBakery That Came With Your Theme? Here Is Why
The update notice is real and the license request is not a mistake. A WPBakery that shipped inside a theme is licensed to the theme's author, not to you, and it was only ever meant to update when the theme hands you a newer copy. You have three ways to get one, and the right choice depends on whether the theme is still alive.
What you are seeing
- The Plugins screen announces a new WPBakery version with no working update link
- A notice asks you to activate WPBakery to receive updates
- The theme's purchase code is rejected in the WPBakery license field
- The Product License tab is missing from WPBakery's settings
- The theme's plugin screen calls WPBakery up to date when it plainly is not
Why it happens on WPBakery
Most common first.
- 1
The theme author holds the WPBakery license
Theme authors buy a license that lets them include WPBakery in their product. It does not pass to their customers. Your marketplace purchase code proves you bought the theme, and WPBakery's activation has no use for it.
- 2
Updates were designed to arrive through the theme
A bundled copy is updated by the theme's own installer, commonly a required-plugins screen under Appearance or in the theme's dashboard. That screen can only offer the version packed into the theme release you have installed. WordPress sees the newer public release, announces it and cannot deliver it.
- 3
The theme itself is not registered or not current
Many themes will not serve bundled plugin updates until the theme is registered with its purchase code, or until the theme is updated first. If the theme was bought on a former developer's marketplace account, the code exists. It is in the inbox of someone who left the company.
- 4
The theme author stopped shipping new bundles
When a theme's releases slow down or stop, so does its bundled builder. No setting fixes this. The only newer copy of WPBakery available to that site is one you license yourself.
- 5
The theme hides WPBakery's own updater
Themes can tell WPBakery it is running as part of the theme. That switches off the license tab and the plugin's own update prompts, which is why the place you would enter a license may not be there at all.
How to fix it, in order
Least invasive first. Stop at the step that fixes it.
- 1
Establish what you have
On the Plugins screen, note the WPBakery version. Under Appearance, Themes, open the theme's details and note its version, then compare both with the current releases on the vendors' own pages. Find out who holds the marketplace account the theme was bought on.
- 2
Copy the site before any plugin is replaced
A builder update touches every page at once. Make a staging copy, or at the least a full backup of files and database that you have tested, and do the update there first.
- 3
Update the theme, then its bundled plugins
Register the theme with its purchase code on the theme's registration screen, update the theme and then open its required-plugins screen, often Appearance, Install Plugins. If a newer bundled WPBakery is offered, update it from there. This route costs nothing and keeps the pairing the theme author tested.
- 4
Take the plugin from the newest theme package
If the dashboard route fails, download the latest full theme package from the marketplace account. Theme packages commonly carry the bundled plugin zips in a plugins folder. Upload that zip under Plugins, Add New Plugin, Upload Plugin and let WordPress replace the installed copy.
- 5
License WPBakery directly when the theme has stalled
Buy a license from WPBakery's own site, install the official copy on staging and activate it under WPBakery Page Builder, Product License. Check every theme-made element and any builder templates the theme overrides before going live. If the license tab is hidden, the theme is suppressing it, and its documentation or a developer can lift that.
- 6
Do not reach for an unofficial copy
Sites offering the latest WPBakery as a free download are distributing modified plugins, and modified plugins are a common way for malware to arrive. If neither the theme nor a direct license is an option, the honest next step is planning the move off the builder.
Keep it from coming back
- Keep the theme's purchase code and marketplace login in the business's own records
- Check the theme's changelog twice a year for how recently it shipped a builder update
- Update the theme and its bundled plugins together, on staging, in that order
- If you buy a direct license, note its renewal date beside the domain's
The permanent fix
A faster Next.js build, with a CMS made for your business
If the theme is maintained, this is a registration chore. If the theme has gone quiet, a direct license fixes the builder and leaves the theme's own elements aging underneath it, and you will be back here in another form. That is the point at which a Next.js build with a custom CMS earns a quote: there is no bundled plugin, no marketplace code and no second vendor whose schedule decides when your site gets patched.
| On WPBakery today | On Next.js with a custom CMS | |
|---|---|---|
| What you keep updated | WordPress, the theme, its builder and every bundled plugin, all in step | Nothing on a schedule. There is no theme or plugin stack to fall out of step |
| How a page is served | Built from the database on each visit, through the theme and its builder | Built ahead of time and served as finished files from servers near the visitor |
| How you edit it | A general-purpose builder with every option the theme ships | A CMS built around what your business actually changes: services, prices, photos, posts |
| What can break it | An update to any one of those parts, or a license that lapses | A change someone makes on purpose, tested before it goes live |
Your content, your addresses and your rankings come with you: every page is moved, every old address is redirected, and you get a login to an editor that only shows what you need. A repair is still the right call for many sites, and we will say so when it is.
Want this fixed on your WPBakery site?
Tell us what you are seeing. We look at the site, tell you plainly what is wrong and what it takes, and quote a fixed price before any work starts.
Which of these sounds like you? (pick any)
Frequently asked
Because the two are separate products with separate licenses. The code identifies your purchase of the theme. WPBakery's license field wants a license bought for the builder itself, which a bundled copy never came with. The field is not broken, and neither is your code.
Ignoring the notice is fine. Ignoring the version gap is not. The notice only tells you a newer public release exists. What matters is whether your theme has shipped a bundle recent enough to include the builder's security fixes and to run on your host's PHP version.
The pages are stored in the database and both copies read the same tags, so standard rows, columns and elements carry over. The risk sits in what the theme added: custom elements, overridden templates and styling written for the bundled version. That is why the swap belongs on staging first.
Usually on a required-plugins or plugin-installer screen the theme adds, under Appearance or inside the theme's own dashboard menu. Some themes also rely on the marketplace's updater plugin to deliver the theme itself. The standard Plugins screen shows the notice and not the update.
Keep reading
- ServiceFixing WordPress PluginsOne bad plugin can take your whole site down. We fix plugin conflicts, fatal errors, and security holes fast — and build custom plugins when the off-the-shelf ones fall short.
- ServiceWebsite Hosting & Maintenance PlansThe watching after launch: managed hosting, tested updates, backups that restore, security and uptime monitoring, and small edits done within a day, month to month.
- ServiceMalware Removal & SecurityA hacked site costs you customers and Google's trust at the same time. We remove the malware, close the hole that let it in, and harden what is left.
- WordPress repair · The7 Theme Repair: What Breaks, Why and What Is Worth Fixing
- WordPress repair · Bridge Theme Broken, Slow or Years Behind? What Repair Can Fix
- WordPress repair · WordPress Site Hacked? How Malware Removal Actually Works
- Page · Moving from WordPress to Next.js
- Fix · WPBakery Page Builder Not Working
- Fix · WordPress Theme Broke After an Update