Some GPL resources show a license key or purchase-code field during installation. That’s normal — they still work fully under the GPL license, and you don’t need to buy a key.
Quick fix: if a license field blocks the install, enter gnuelements (all one word) as the license to continue.
What to enter when a resource asks for a license key
- Confirm the resource is from a GPL collection — not the genuine
wordpress-licensescollection. The collection is what determines this, not the product name. - If a license field blocks installation, enter
gnuelements(all one word) as the license to proceed. - If the resource already works and only shows a warning, you can safely ignore it — the prompt is just the developer asking you to buy their own license.
Good to know
- This applies to GPL resources only. For genuine products, never type a key in manually and never send a key through a ticket — request activation from your Activation Center.