WoodMart fix
WoodMart Won't Update, or Broke After One? Match Theme and Core
Every WoodMart release comes in two parts, the theme and the WoodMart Core plugin, and WordPress delivers only the first. Miss the second and the store runs new theme code against an old plugin, which is where the missing elements and the critical errors come from. The repair is mostly a matter of doing things in the right order.
What you are seeing
- A notice says WoodMart Core requires an update and will not go away
- The update fails with a download error or a missing stylesheet error
- Product grids, banners or whole sections vanished after updating
- A critical error appears on the storefront or in the dashboard
- No update is offered though the theme is clearly years behind
Why it happens on WoodMart
Most common first.
- 1
Theme on the new release, WoodMart Core on the old
Theme updates arrive through the WordPress updater. WoodMart Core is bundled with the theme, so its update comes from the theme's own plugin installer as a separate step. Automatic updates and hurried manual ones do the first and skip the second, leaving new theme code calling functions the old plugin does not have.
- 2
This domain has no active license
One-click updates depend on a purchase code registered in the WoodMart dashboard. If the store was built on a developer's license, cloned from staging or moved to a new domain, activation is lost and the updater quietly offers nothing. Manual uploads still work, which is how stores end up updated once every two years.
- 3
The documentation package uploaded instead of the theme
ThemeForest offers two downloads: the full package with documentation, and the installable WordPress file. Uploading the full package produces the error about a missing style.css stylesheet. The installable file is the one WordPress wants.
- 4
Several major versions in one leap
A store several major releases behind meets many changes at once: settings that moved, elements that were rewritten, newer requirements for PHP and WooCommerce. The update installs, and the gaps show up as shifted layouts and options that no longer sit where they did.
- 5
Child theme files written for the old version
Templates and functions copied into the child theme keep running after the parent changes beneath them. An override of a WoodMart or WooCommerce template that worked two versions ago can now call something that no longer exists.
How to fix it, in order
Least invasive first. Stop at the step that fixes it.
- 1
Copy the store before you touch the updater
Take a full backup of files and database before anything else. If the host offers a staging copy, run the update there first. A store that takes orders should not be the test bench.
- 2
Compare the two version numbers
Appearance, Themes shows the WoodMart version when you click its thumbnail. The Plugins screen shows the WoodMart Core version. If the theme is ahead, the fix may be one click away.
- 3
Update WoodMart Core from the theme's plugin installer
Open the Plugins tab in the WoodMart dashboard, or Appearance, Install Plugins on older versions. Update WoodMart Core, then the page builder and any other bundled plugin showing an update. If a critical error locks you out of the dashboard, replace the woodmart-core folder in wp-content/plugins over SFTP with the copy supplied with the new theme version.
- 4
If the update will not install, do it by hand
Download the installable WordPress file from the Downloads page of the Envato account that bought the theme. Upload it under Appearance, Themes, Add New, Upload Theme and choose to replace the installed copy when WordPress asks. Then repeat the Core update.
- 5
Clear every layer that remembers the old version
Purge the cache plugin, the host cache and the CDN. WoodMart writes a stylesheet from your settings, so open Theme Settings and save once to regenerate it. Then look at WoodMart, Patcher for fixes released since the version you just installed.
- 6
Review the child theme, then place a test order
In WooCommerce, Status, find the Templates list. Any child theme override marked outdated should be rebuilt from the current file or removed. Finish with a test order, a filter click and a swatch selection on a phone.
Keep it from coming back
- Update the theme and WoodMart Core in the same sitting, theme first
- Leave automatic theme updates off so the theme never moves ahead of Core unattended
- Register the license to an Envato account the business owns
- Update a few times a year so no single jump crosses several major versions
The permanent fix
A faster Next.js build, with a CMS made for your business
If every WoodMart update needs a staging copy, a developer and a list of things to recheck, the store has become a set of parts kept in step by hand: theme, Core plugin, builder, WooCommerce and child theme. A Next.js storefront with a custom CMS has no theme release cycle and no plugin stack to match. Changes ship when you decide, not when four vendors do.
| On WoodMart 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 WoodMart 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
Yes. The theme goes first, then WoodMart Core straight after, from the theme's own plugin installer. The new Core version is delivered with the new theme, so it is not available until the theme has updated. Do both in one sitting, and do not leave the store between the two steps.
WoodMart is sold through ThemeForest, not the WordPress.org directory, so updates appear only once your copy is activated with a purchase code. Check the license screen in the WoodMart dashboard. If activation is not possible, download the latest installable file from the buyer's Envato account and upload it by hand.
Yes, if you took a backup first: restore the files and the database together. Putting back only the theme folder is less reliable, because an update can change saved data as well as files. This is the practical argument for testing on staging, where a bad update costs nothing.
Theme Settings, Header Builder layouts, HTML Blocks and pages live in the database and survive. Code edited directly inside the woodmart folder does not, since an update replaces every file there. Changes kept in a child theme survive too, though they may need revising to suit the new version.
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.
- 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.
- WordPress repair · WooCommerce Store Broken or Losing Sales? Where It Breaks and Why
- WordPress repair · Stuck With WPBakery? Repair the Site or Plan the Way Out
- Page · Moving from WordPress to Next.js
- Fix · WordPress Theme Broke After an Update
- Fix · WordPress White Screen of Death
- Fix · Site Broke After a PHP Update