Bridge fix
Bridge Theme White Screen After an Update? Find the Mismatch
You updated Bridge, or Bridge Core, or your host updated PHP for you, and now the site is a blank page or one line about a critical error. On Bridge this is rarely random. The theme, its core plugin and the bundled plugins are released as a set, and a white screen usually means one member of the set is on a different version from the rest.
- [01-Oct-2026 09:14:02 UTC] PHP Fatal error: Uncaught Error:
- Call to undefined function bridge_qode_options()
- in wp-content/plugins/bridge-core/bridge-core.php:41
- #0 wp-settings.php(545): include_once()
- #1 wp-config.php(96): require_once('wp-settings.php')
- WordPress: recovery mode email sent to site admin
What you are seeing
- A blank page, or 'There has been a critical error on this website'
- The front end loads but wp-admin is white, or the other way round
- Sections replaced by raw shortcodes right after the theme updated
- Portfolio pages return a 404 and Qode sliders vanish
- An email from WordPress naming Bridge Core or the Bridge theme
Why it happens on Bridge
Most common first.
- 1
Bridge and Bridge Core on mismatched versions
Bridge Core calls functions that live in the theme, and the theme calls functions that live in Bridge Core. Update one from ThemeForest and leave the other where it was, and one of them asks for something that is no longer there. PHP stops at that line and the page stays blank.
- 2
An old install updated across many versions at once
Early Bridge releases kept shortcodes and post types inside the theme. Later ones moved them into Bridge Core. A site that jumps from the old arrangement to the current theme without installing the plugin loses its shortcodes, portfolio and sliders in a single step.
- 3
Bundled plugins left behind by the theme update
Updating Bridge does not update WPBakery, Slider Revolution or LayerSlider on its own. The old copies stay active until someone updates them from Appearance, Install Plugins. Old builder and slider code is often the first thing to fail on a newer PHP version.
- 4
A PHP upgrade underneath an old Bridge
The host moved the server forward and nothing on the site moved with it. A Bridge release from several years ago was never tested against the PHP your host runs today. Our fix page for a site that broke after a PHP update explains the general case. On Bridge the cure is bringing the whole set current.
- 5
Old template copies in the Bridge child theme
Child themes for Bridge often copy template files or call the theme's internal functions. Those have been renamed and reorganized over the years. After an update the child theme can call a function that no longer exists under that name.
How to fix it, in order
Least invasive first. Stop at the step that fixes it.
- 1
Read the error before changing anything
WordPress emails the site admin a recovery link when a theme or plugin crashes, and the message names the file. A path containing bridge-core, themes/bridge, js_composer or revslider tells you which piece failed. If no email came, the white screen guide linked below shows how to switch on the debug log.
- 2
Back up, then get into wp-admin
Take a backup from your hosting panel. Then use the recovery link, or connect by SFTP and rename the folder the error names, for example wp-content/plugins/bridge-core to bridge-core-off. That deactivates it without deleting anything. Pages will look wrong for a while. The aim is only to reach the dashboard.
- 3
Install the Bridge Core that matches your theme
Download the current Bridge package from your ThemeForest account so the theme and its plugins come from one release. Update the theme under Appearance, Themes, Add New, Upload Theme, where WordPress offers to replace the installed copy. Then open Appearance, Install Plugins and update or install Bridge Core from there, not from an old zip.
- 4
Update the bundled builder and sliders
On the same Install Plugins screen, update WPBakery Page Builder, Slider Revolution and LayerSlider to the copies shipped with the new theme. A bundled plugin that refuses the update has its own fix page in this section.
- 5
Put PHP back only as a stopgap
If the host's PHP upgrade caused the crash and you cannot update today, switch to the previous PHP version in the hosting panel to bring the site up. Then update Bridge and its plugins on a staging copy and move PHP forward again. Treat the rollback as a few days of cover, with a date on it.
- 6
Test the child theme and rebuild the styles
Under Appearance, Themes, activate the parent Bridge theme for a minute. If the error goes, the child theme holds outdated code that needs rewriting against the new version. Last, open Qode Options, save once and clear every cache so Bridge regenerates its stylesheets.
Keep it from coming back
- Update Bridge, Bridge Core and the bundled plugins in one sitting, never one alone
- Run that sitting on a staging copy first and click through the key pages
- Keep custom code in a child theme and review it at each major Bridge release
- Try a new PHP version on staging well before your host's deadline
The permanent fix
A faster Next.js build, with a CMS made for your business
One white screen after a skipped update is a repair. A white screen at every update means the site has become five or six products that must all agree, looked after by nobody in particular. A Next.js build with a custom CMS has no theme, core plugin or bundled builder to keep in step, and because its pages are served as static files, a bad change tends to fail in the build and not in front of customers.
| On Bridge 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 Bridge 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
The theme, then Bridge Core straight after, in the same session. The plugin copy that matches each theme release ships inside the theme and appears under Appearance, Install Plugins once the theme is updated. Do not leave the site between the two steps.
No. The pages are intact in the database. Shortcodes appear as text when the plugin that renders them is inactive, which after a Bridge update usually means Bridge Core or WPBakery is missing or deactivated. Install and activate the matching versions and the layouts return.
Yes, and if the site earns money that is a sensible first move. It returns you to the old versions, though, with the same update still waiting. Restore, then repeat the update properly on a staging copy.
The theme's changelog on ThemeForest states which PHP versions the current release supports, so check there first. The failures we see come from old copies of Bridge and its bundled plugins meeting a PHP release that arrived years after they were written.
Keep reading
- ServiceFixing Broken WebsitesSite down, hacked, or falling apart? We diagnose it fast, fix what's broken, and tell you straight how to keep it from happening again.
- 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.