Activation lives on your site. Ownership of the license lives in your account. When a site is unreachable, the account is the only place you can act.
This page matters most to people with several licenses, and to anybody moving between domains.
#Every item has three public resources
Documentation, a changelog and a roadmap, each belonging to that specific product rather than to the studio as a whole.
All three are public and reachable by direct link with no sign in. That is deliberate: so you can judge a product before buying, and so you can send a colleague a link to one section.
- Documentation
The product's manual. It is tied to the product and updated with it, so it describes the current version rather than the one that existed when you bought.
- Changelog
The history of changes by version: what was added, what was fixed, what behaves differently. The theme and Pro plugin have separate version lines, so it shows which of them changed, which is what decides whether you update one or both.
- Roadmap
What is planned and what state each item is in, grouped by status, with categories and rough periods. Some entries carry user votes. The roadmap is also where you ask for something - every product board has a suggestion button, and a request that lands there is read.
The cycle that connects them: a suggestion becomes a roadmap entry, a completed entry lands in the changelog, and the documentation section is updated. Which gives a practical habit worth having: if something is missing from the documentation, check the roadmap; if behavior changed, check the changelog before writing to support.
A roadmap is intent rather than a commitment to dates.
An entry can move, change shape or be dropped after what we learn building it, and the changelog is where you look for what actually shipped.
#Your version history
Your account holds the full version history of your product, not only the latest build. A purchased item does not narrow down to one file.
The theme and the Pro plugin are versioned and downloaded separately. One file does not update both.
There is no download clock. What you can reach is decided by the license you hold, not by a date it passes. The support window has an end; the version list does not.
#Two ways to get a version
From your site admin. The main route. Updates and rollback happen in Version Control without visiting your account and without moving files by hand. Faster and safer: nothing to download, unpack or place in folders.
Rolling back is a normal operation rather than an emergency hack. If an update causes trouble, going back is a few clicks. That is the answer to "what if an update breaks something".
Version Control is part of a direct license, not of a marketplace one.
A theme bought on ThemeForest carries the Regular tier, and the Regular tier has no update pipeline: the Version Control screen inside the theme admin is not available to it, so neither updates nor rollbacks run from there. You still hold every version, and you still download them from your account and install them by hand.
From your account. The manual route, and equally valid. You need it when the admin is unreachable, when you are putting the theme on a new site, when a file has to go onto a server by hand, or when you are handing it to a contractor. This is also where you pick a specific version from the list.
Two practical notes. Take a backup before a rollback or a manual replacement. And a manual replacement does not reset your settings: they live in the database, not in the theme files.
#Roll the pair back together
The theme and the Pro plugin are built against each other. Each release of one is tested with the release of the other that shipped alongside it, and the further apart the two versions drift, the less of that testing applies to what you are running.
So when you roll the theme back, look at the Pro plugin in the same sitting and take it to the version that shipped with the theme version you have chosen. The changelog shows both lines, which is what makes the pair visible.
A large gap between the two is the ordinary cause of a fatal error, a missing settings panel or a block that stops rendering after a rollback. It usually reads as "the rollback broke the site", and it is really the plugin calling something the older theme does not have yet, or the other way round.
#Where each license is in use
The license list shows, per item: the license type, where it was bought, its state, the domain an active license is bound to, the activation date, and the date support runs to.
The states in plain words:
- Not activated
Owned, and not yet bound to a domain. Nothing is wrong with it.
- Active on a domain
In use, on the domain shown next to it.
- Awaiting verification
Active, and the routine check has not reported back for longer than it should. The site keeps working. It is a prompt to look, not a lock.
- Blocked
Not usable. A refund is one of the reasons a license ends up here.
A refunded license is not a state you will see listed. The purchase is undone, so the license goes with it rather than sitting in the list wearing a label.
#Releasing a domain
The main action on this screen. You need it when the old site was deleted, the domain was handed over, the admin is unreachable, or the site broke and the deactivate button is out of reach.
The slot is freed in your account immediately, so you can activate on the new domain without waiting. The old site, if it is still running, only learns about it at its next scheduled check.
If you do still have access to the site, deactivating from inside it is faster and cleaner.
#How many domains you have
Your account answers this directly: how many units you own in total, and how many are in use.
#Common questions
Can I download a version from before I bought?
Yes, the history covers every release of the product rather than only the ones published since your purchase.
The download gives me a package rather than a theme file
The premium package holds the theme, the Pro plugin and the documentation together, so unzip it and upload the theme archive from inside it.
My support period ended. Do I lose anything?
No. The support window is what ends, and it decides whether you can open a ticket. It does not touch what is installed, and it does not close the version list in your account.
The list disagrees with what my site says
The account is the authoritative record, so clear the site's object cache first because a stale cached option is the usual explanation, and if the two still disagree then open a ticket with both pictures.
#Still stuck
Open a support ticket with the item, the domain, and what each side is reporting.
Last updated
