First off, move your entire MODX installation (files and database) to the new domain. When that's done correctly, MODX and all our extras will continue to work as expected.
Next, go into the site's manager and use the extra in the back-end (for example for ContentBlocks, Redactor or MoreGallery you would edit a resource that uses those extras, and for Commerce you'd go to Extras > Commerce), which will trigger a license check right away.
When the license check is triggered, our system sends an email to the email address on your account alerting you of a new license issue. When you follow the special link in that email, that will give you the option to transfer, assign, or buy a license, depending on the status of your account and wether or not the system was able of detecting the domain you transferred from automatically.
When you've transferred or assigned a license, the next time you use the extra in your manager it will automatically download the updated license key and no further action from you is needed.
When you've received a license alert, but it does not offer you to transfer the license (instead only offering the option to assign a license from your account, or telling you to buy a new license), that typically means a problem related to the previously licensed domain.
If the license page does not tell you what the previous domain was, the license check was unable of detecting that automatically. That can happen when a license check was triggered by checking for updates in the package manager, rather than using the extra in the manager (e.g. editing a resource or viewing its component). In this case, please contact [email protected], mentioning both the new and the old domain (you can find this under Account > Licenses if you're not sure) and we will manually reset the license on the old domain to allow you to re-assign it.
If the license page does tell you the previous domain, but still doesn't offer you the option to transfer the license, that means the previous domain was covered by a free development license, but the new domain is not. You will need to assign a paid-for license in this case.
Generally, yes, but there are exceptions.
- If you expect the temporary staging environment to be shut down shortly (e.g. in less than two weeks), you can ignore the license issue. The unlicensed extras will continue to work, but they will show a big red license warning and you may notice a performance hit in the manager as the license check runs on every request.
- If the production environment is not yet licensed (e.g. you're working on a completely new site), you can assign the license you've bought for production to the staging environment. When you go live, you'll receive another license email that will allow you to transfer the license from staging to production.
If you need the staging environment to be available for the long term, we'd strongly recommend to pick a domain for it that allows free development licenses, so that you do not run into any license related issues at all.
Yes, you can install all our premium extras for free with free development licenses. You'll then need to buy a license when your site goes live.
Likely you just assigned or transferred a license to the current domain. At that point you will continue to run into license issues during the package (un/re)installation because each download is uniquely encrypted with the license key.
To resolve that, you'll need to either update to a newer version (if available), or do a force remove of the package and then download the latest version again.
It also helps to remove the
core/components/PACKAGE/.pubkey file. This sometimes contains a cached license key, and after removing it the next license check or package installation will put in place the proper one.
The "provider_err_nf" error means that the package is not assigned to a package provider. This can happen when you removed a package provider to recreate it with a new API Key.
To fix it, click on "View Details" for the offending package. In the form that loads, choose the modmore.com package provider at "Provider", and save with the button in the top right. Click on "Close" to go back to the package list, and now you should be able of checking for updates again.
If you don't have a configured package provider, follow the instructions at API Keys.