Flatsome fix
Flatsome Won't Update or Accept Your Purchase Code? Fix Both
Flatsome updates from the dashboard only once the site is registered with a ThemeForest purchase code. When that code is missing, in use elsewhere or owned by a developer who has moved on, the theme quietly stays at the version it launched with. Getting current is two jobs: settle the license, then update without breaking the store.
What you are seeing
- The Flatsome dashboard says the theme is not registered
- The purchase code is rejected or reported as in use on another site
- Appearance, Themes offers no update though Flatsome is years old
- The update starts, then stops with a download or package error
- Uploading the theme zip ends with a missing style.css message
Why it happens on Flatsome
Most common first.
- 1
The purchase code belongs to someone else
Whoever bought Flatsome on ThemeForest holds the code. On a store built by a freelancer or an agency that is often their account, and one code may have been used across several client sites. It goes unnoticed until the registration is checked, and then your store is the one left without updates.
- 2
The code is still attached to another address
A registration is recorded against a site address. Move the store to a new domain, or register a staging copy first, and the live site is told the code is already in use. The registration has to be released from the old address before it will attach to the new one.
- 3
The store was never licensed
Some stores were built from a copy of Flatsome that did not come from ThemeForest. There is no purchase code to find because none was issued. Those copies cannot update, and theme files from an unofficial source deserve a malware scan before anything else is done.
- 4
The wrong zip, or a theme folder with the wrong name
ThemeForest gives you two files: the full package with documentation and extras, and the installable theme file. Upload the full package and WordPress reports that style.css is missing. A related fault is a theme folder named something other than flatsome, left by an earlier manual upload. New versions then install beside the active theme, and a child theme loses track of its parent.
- 5
A blocked connection, an expired token or an old server
Registration and updates both need your server to reach UX Themes, and a host firewall that blocks outgoing requests stops both. Older installs that update through the Envato Market plugin stop when its API token expires. A current Flatsome also expects a reasonably current PHP and WordPress, so a neglected server can be the thing refusing the update.
How to fix it, in order
Least invasive first. Stop at the step that fixes it.
- 1
Find the purchase code and its owner
Sign in to ThemeForest with the account that bought the theme, open Downloads and get the license certificate for Flatsome. The purchase code is printed in it. If the account belongs to a former developer, ask for the code and for the old registration to be released, or buy a license in the business's own name. Either is quicker than arguing with a registration form.
- 2
Back up, then work on a staging copy
An update across many releases replaces every theme file and can change templates the store relies on. Take a full backup of files and database and make the first run on staging. Check UX Themes' current terms for staging sites so the copy does not take the registration your live store needs.
- 3
Enter the code on the registration screen
Open the Flatsome menu in the dashboard, go to its registration screen and enter the code. If it reports the code as already in use, release the old registration from that site's registration screen or from your UX Themes account, then try again. If it fails with a connection error, ask the host whether outgoing requests are blocked.
- 4
Run the update from the dashboard
Go to Dashboard, Updates and press Check Again so WordPress asks afresh. Update Flatsome there or under Appearance, Themes. If the store is many releases behind, update WordPress and WooCommerce on the same staging copy so the three are tested together.
- 5
Or update by hand with the right file
In ThemeForest Downloads choose the installable WordPress file, not the full package. Go to Appearance, Themes, Add New, Upload Theme, select the zip and accept WordPress's offer to replace the installed copy. Afterward confirm the folder is still named flatsome and the child theme is still active.
- 6
Check what the update changed
Clear every cache. Open WooCommerce, Status and read the Templates section for child theme files that are now out of date. Open UX Builder, place a test order and look at the header on a phone. Only then repeat the update on the live store, in a quiet hour.
Keep it from coming back
- Hold the ThemeForest account and purchase code in the business's name, not a contractor's
- Update Flatsome a release or two at a time, not once every few years
- Keep custom code in the child theme so nothing is edited inside the flatsome folder
- Write down which address the license is registered to, staging copies included
The permanent fix
A faster Next.js build, with a CMS made for your business
A theme that cannot update because nobody owns its license is an ownership problem, and fixing the license fixes it. If the update keeps being postponed because every release threatens the child theme and the checkout, the store has become expensive to keep current. A Next.js build with a custom CMS has no theme to register and no purchase code to lose, because the site is your own code served as static files.
| On Flatsome 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 Flatsome 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
Inside the ThemeForest account that purchased it. Open Downloads, find Flatsome and choose the license certificate. The purchase code is in that document. If you never had a ThemeForest login, someone else bought the theme on your behalf and holds the code.
A regular ThemeForest license covers a single end product, which in practice means one live site per purchase. A developer who used one code across several client stores has left all but one of them unable to register. Rules for staging copies are set by UX Themes, so read their current terms before registering one.
It usually installs. The risk is in what the jump changes: templates your child theme overrides, options that were renamed and elements that behave differently. Do it on staging, read the theme's change log for the major releases you are crossing and test the cart, checkout and UX Builder before touching the live store.
Theme options, UX Builder pages and UX Blocks are stored in the database and stay put. What an update replaces is every file inside the flatsome folder, so code edited straight into the parent theme is lost. Changes kept in a child theme remain, though a child template may need revising to match the new parent.
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 · WordPress Site Hacked? How Malware Removal Actually Works
- WordPress repair · WooCommerce Store Broken or Losing Sales? Where It Breaks and Why
- Free tool · Website health check
- Page · Moving from WordPress to Next.js
- Fix · WordPress Theme Broke After an Update
- Fix · “Another Update Is Currently in Progress”
- Fix · Site Broke After a PHP Update