Theme repair · Salient
Salient Theme Broken, Slow or Stuck on an Old Version? Start Here
Salient is not one piece of software. It is a theme, a modified edition of WPBakery and a family of companion plugins that expect to be updated together. Most Salient trouble starts when one of them moves and the others stay put, and most of it can be repaired once you know which piece is out of line.
- FailSalient Core vs. themeBehind
- FailStandard WPBakery presentYes, active
- WarnUpdate routeNone connected
- WarnHome page sliderVideo, 4 slides
- WarnUnused demo pages41
- PassChild theme activeYes
Signs the trouble is in the Salient stack
- The page editor opens to a blank panel or a spinner that never stops
- Pages show bracketed shortcodes where a slider or a row used to be
- The dashboard keeps asking you to update plugins named Salient something
- The home page slider arrives late, or not at all on phones
- An update finished and the header, fonts or colors changed
- Nobody knows which Envato account bought the theme
What goes wrong on a Salient site, and why
Most common first, each with a way to check it yourself.
- 1
A theme ahead of its companion plugins
Salient keeps its page elements in a plugin called Salient Core, its builder in Salient WPBakery Page Builder and its sliders, portfolio and widgets in plugins of their own. Each theme release expects particular versions of them. Update the theme and skip the plugins, and elements lose settings, rows shift and the editor starts throwing errors.
Check it: Open Plugins and look at everything whose name begins with Salient. A dashboard notice asking you to update any of them, left since the last theme update, is the mismatch.
- 2
The standard WPBakery installed over Salient's edition
Salient's builder is a modified WPBakery made to work with the theme's own elements. Someone sees an old builder, buys the regular plugin and installs it. Now two builders claim the same pages, and the one that wins does not know what a Nectar Slider is.
Check it: In the plugin list you should find Salient WPBakery Page Builder and nothing named plain WPBakery Page Builder. If both are present, that is the first thing to fix.
- 3
No route for updates to arrive
Salient is sold on ThemeForest, so WordPress cannot fetch new releases the way it does for free themes. Updates come through the Envato Market plugin, connected with a token from the account that bought the theme, or by downloading the new release and uploading it. When that account belonged to a designer who has moved on, the site stays on the release it launched with while WordPress and PHP keep advancing.
Check it: Look for Envato Market in the dashboard menu and see whether Salient is listed there. If the plugin is absent or the list is empty, nothing is delivering updates.
- 4
Motion on every screen
Full-screen Nectar Sliders with video, parallax backgrounds, columns that animate in and transitions between pages. Each effect is reasonable alone. Stacked on one home page they add scripts, large media and work the phone must finish before a visitor can read anything.
Check it: Load the home page on a phone using mobile data, not office wifi. Count the seconds before the first headline is readable.
- 5
A demo import nobody cleaned up
Many Salient sites began as an imported demo. The pages the business uses were rewritten. The other forty stayed, along with demo sliders, portfolio items and plugins the demo needed and the business never did. They clutter the admin, load code and sometimes sit in Google's index under your domain.
Check it: Go to Pages and order the list by date. A block of pages created on the same day, with titles you do not recognize, is the demo.
- 6
Layouts written in Salient's own shortcodes
Pages are stored as builder shortcodes, and many of the elements, such as nectar_slider and nectar_btn, belong to Salient Core. A different theme cannot draw them, and neither can a standard WPBakery. That is no fault in the site, but it sets the price of any future move.
Check it: View a page's raw content in the editor's text mode and look for tags beginning with nectar_ or vc_. The more you see, the more a change of theme has to translate.
The Salient problems we fix most
Each has its own page: what you are seeing, why, and the fix in order.
- Page Builder Not LoadingA blank editor, an endless spinner or a save that never lands. Usually the wrong builder edition or plugins out of step.See the fix for Page Builder Not Loading
- Update ProblemsUpdates that fail, never appear or leave the theme ahead of its plugins. The order that keeps Salient matched.See the fix for Update Problems
- Demo Import FailedAn import that stalls, doubles the content or leaves gray boxes for images. Clean up, check the plugins and run it once.See the fix for Demo Import Failed
- Slow Salient WebsiteVideo sliders, animated rows and fonts by the dozen. Where a Salient page gets its weight and what to cut first.See the fix for Slow Salient Website
Do this today
Open Plugins and read the names. You want to see Salient Core and Salient WPBakery Page Builder active, and no second plugin called simply WPBakery Page Builder. Then note whether an update notice for any Salient plugin is waiting. Those two facts explain most Salient problems and take two minutes to collect.
How we work through a Salient repair
- 1
Inventory before touching
We record the theme release, the version of every Salient plugin, whether a second builder is installed, where the child theme stands and which Envato account holds the purchase.
- 2
Move the risk to a copy
Updates, plugin removal and builder repairs happen on a copy first, so the live site keeps taking calls while we find out what breaks.
- 3
Bring the stack to one release
Theme first, then Salient Core, the builder and the remaining Salient plugins, followed by cleared caches and a pass through every template the site uses.
- 4
Lighten, then measure on a phone
Sliders, animation and leftover demo content are trimmed on the pages that earn business, and the result is checked on a real mobile connection.
What a repaired Salient site looks like
The right builder, and only one
Salient's edition active, any standard WPBakery removed and the editor opening and saving on every post type you use.
Theme and plugins on a matching release
Salient, Salient Core and the rest brought current together, with the layout checked page by page afterward.
An update route you own
The Envato Market connection set up under an account the business controls, and custom code moved into a child theme so the next update is uneventful.
Faster pages with the same look
The opening slider slimmed or replaced, animation kept where it helps, demo leftovers removed and Salient's performance settings working with your cache instead of against it.
Repair it, or start over?
The honest answer depends on the site, not on what we would rather sell.
Repair it when
- The design still suits the business and the faults began with an update
- The trouble traces to one cause, such as a second builder or lagging plugins
- Your team is comfortable editing in the Salient builder
- Speed improves measurably once the slider and animations are trimmed
Rebuild it when
- Every update breaks something and each rescue is paid for separately
- Mobile speed stays poor after the motion has been cut back
- A redesign is due, so every shortcode page would be touched anyway
- You would rather edit content than maintain a stack. A Next.js build with a custom CMS has no theme, builder edition or companion plugins to keep matched
The permanent fix
A faster Next.js build, with a CMS made for your business
When a Salient site spends more time being repaired than being used, the stack is the problem, not the last update. A Next.js build replaces the theme, the builder and the plugins with one codebase made for this site, and a CMS that shows your team only what they actually change.
| On Salient 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.
When to bring someone in
Call before you install a different page builder, switch themes or run a multi-year update on the live site. Each of those is simple to do and slow to undo on a Salient site, because the pages depend on plugins that must agree with one another. Call as well if the editor is down and the site needs changing this week, or if speed work has stalled and you want numbers before choosing between repair and rebuild.
Repair Salient, or move on from it?
Describe what the Salient site is doing and when it began. We will check the builder edition, the plugin versions and the update route, then say plainly whether this is a repair or a reason to rebuild.
Which of these sounds like you? (pick any)
Frequently asked
ThemeNectar modifies the builder so it works with the theme's elements, row options and styling, and ships that edition with the theme as Salient WPBakery Page Builder. It is updated alongside the theme. A separately purchased WPBakery is a different plugin and is not a substitute for it.
Salient Core and Salient WPBakery Page Builder are the two that pages depend on. The others cover specific features: Nectar Slider, Portfolio, Social, Widgets and the Demo Importer. Before deactivating one, confirm on a staging copy that no page uses what it provides.
No. A ThemeForest purchase includes theme updates, and paid support is the part that runs out. What you need is access to the Envato account that made the purchase, or a copy of the current release from whoever holds it.
Test a plain page with no slider, such as a privacy policy, and then the home page. If both are slow to start loading, look at the host. If the plain page is quick and the home page drags, the weight is in what Salient was asked to put there.
Repair when the design still works and the faults have a cause you can name. Rebuild when breakage follows every update, when speed stays poor after trimming or when a redesign is coming regardless. In that case a Next.js site with a custom CMS removes the theme and plugin stack altogether, and one migration carries the content across.
The words and images stay in the database. The layouts do not travel, because they are written in shortcodes that Salient Core and its builder interpret. On another theme those pages show bracketed tags until they are rebuilt, so plan a theme change as a migration.
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.
- ServiceWordPress Speed & OptimizationA slow site loses customers before they read a word. We tune WordPress for speed, stability, and search — measured, not guessed.
- ServiceReplacing WordPressWhen WordPress becomes the thing you fight instead of the thing that works, it's time to move. We migrate you without losing rankings.
- ServiceWebsite Migration ServicesMove off WordPress, a page builder, an e-commerce platform or a slow host without losing rankings, forms or tracking — inventoried, redirected, watched.
- Hub · WordPress Repair Hub
- WordPress repair · Stuck With WPBakery? Repair the Site or Plan the Way Out
- WordPress repair · Slow WordPress Site? What Speed Optimization Actually Involves
- Page · Moving from WordPress to Next.js
- Free tool · Website health check
- Fix · WPBakery Page Builder Not Working
- Fix · WordPress Theme Broke After an Update
- Fix · Site Broke After a PHP Update
- Guide · WordPress vs. a Custom Website: The Business Decision
- Guide · WordPress vs. Next.js: The Technical Difference, in Plain Words