Before anything else, here’s the fact that keeps you from going down the wrong path: the item asking for a license doesn’t mean something went wrong. That screen comes from the vendor and shows up on every installation, with or without a license. Whether it’s just a notice or the feature is actually locked is exactly what the five scenarios below sort out.
Worth saying this up front because the most common path from here is the wrong one: you see the notice, conclude the file must be corrupted, download it again, sometimes even pull an old download back from the trash, and run into the exact same notice, because there was never anything wrong with the file.
Below are the five real scenarios, in the order worth checking. Each one has a signal that sets it apart from the others.
1. The item asks for a license, but works
The theme or plugin installs, activates, and works; it just shows a notice asking for a key, sometimes pinned to the top of the panel. This is the scenario most often mistaken for a defect, because the message disappears when you close it and comes back on your next visit.
use the feature you want. Build a page with the builder, open the theme’s options panel, create the form. If it works, everything’s fine: the notice is cosmetic and you can live with it.
download it again. If the item opens and works, the file is intact, and a second download will behave the same way.
2. The Activator is missing — it ships separately
Some vendors only unlock premium features when a companion plugin is installed alongside the main one. In the catalog it shows up as its own item, with “Activator” in the name: YITH Activator, WPC Activator, wpDiscuz Activator, WP-Statistics Activator, among others.
the item installs and activates, but the premium options simply don’t exist in the menu — it’s not that they’re locked, they just don’t appear.
search the site for the vendor’s name followed by Activator. If it exists, download it and install it alongside the main item, like a regular plugin.
3. The item validates the key on the vendor’s server
Some items don’t check the license locally: they query the vendor’s server on every attempt. In those cases, no key you enter will pass.
the error message references the vendor’s address or returns something like Invalid license key. The decisive sign is that any key produces the same error, including a made-up one, proof that validation is happening outside your site.
nothing local fixes this. This item depends on a real activation on your domain, which is scenario 4. If it’s not on the list of available activation, the item keeps working for anything that doesn’t depend on the vendor’s server.
4. Real activation on your domain
For part of the catalog we offer activation tied to your domain. It’s free on the Developer I (1 domain), Developer III (5 domains), Developer IV (10 domains), Monthly Agency (10 domains), Quarterly Agency (100 domains), Semiannual Agency (50 domains) and Annual Agency (100 domains) plans, with domains counted per product, and requests are made at My Licenses.
the item’s own page notes when activation is available. It’s not the whole catalog: it depends on the vendor.
the request goes through requested, under review, and granted. It’s a flow with manual checking, so it’s not instant. Provide the exact domain where the item is installed.
One detail that causes rework: a subdomain is a different domain. If the site runs on store.yoursite.com, that’s the address that needs to be activated, not yoursite.com. Installations in a subfolder follow the same logic: provide the full path.
Envato Elements has its own flow, described in Envato Elements Activation.
5. It was activated and stopped
There are two different situations here, and they’re resolved in different ways.
The key was revoked by the vendor. It happens: third-party keys can be deactivated on their end, without notice. The sign is that the item worked for weeks or months and stopped all at once, with nothing having changed on your site. There’s no local action that reverses this.
The panel says “already activated,” but it doesn’t work. This is the case where the record and reality have diverged, and it’s the only one on this list you can’t resolve yourself, because a new request gets rejected precisely because a record already exists. Open a ticket describing this: that’s the information that lets us fix the record instead of replying with the steps you’ve already tried.
Add-on that won’t activate
A separate case, and common enough to deserve its own paragraph: an add-on won’t turn on because the main plugin isn’t licensed. The add-on installs, shows up in the list, but its option stays unavailable.
resolve the main plugin first, using the scenarios above. The add-on usually starts working right along with it.
If none of the above solved it
When you open a ticket, four pieces of information are usually the difference between resolving it on the first reply and going back and forth three times:
- Item name and version: the version shows up on the item’s page here on the site and in your WordPress panel.
- The exact domain, including subdomain and subfolder if there is one.
- The error text, copied or as a screenshot. The literal message usually identifies the scenario on its own.
- Whether you’ve already requested activation for that domain, and what the panel showed.
With that in hand, it’s almost always possible to say on the first reply which of the five scenarios your case is.
