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 issue, 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 that case, you may still be able of connecting the old license by triggering an additional license check from the site's manager. Instructions for that will be shown on the invalid license page.
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. Please let us know when the temporary environment is shut down, so we can close the license issues for you.
- 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.
You may have just assigned or transferred a license to the 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 can also help 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.
If you still cannot install the package, please make sure your server meets the minimum server requirements and check the installation log for detailed information.
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.
Sometimes. When you buy a license and download, that is the site the license is assigned to and expected to be used for.
If the domain name for the site changes (i.e. the MODX installation is moved or the domain pointer is updated), you can transfer a license through the invalid licenses page. There is no limit to this type of transfer, where the same site (for the same client/project) is simply moved.
In cases where you would like a license to be reused on a completely unrelated site from the one it was originally assigned to, we allow that when all of the following conditions are met:
- The license in question is a standard license - it's not part of an (expired) unlimited license subscription, and not a development license either.
- The license was purchased recently (less than a year ago)
- The package has been uninstalled from the site the license is currently assigned to, or the domain is no longer available.
If these conditions are not met, you'll most likely need to purchase a new license for your new project. If we were to allow unlimited reuse of license, that would essentially mean offering unlimited refunds, and we'd soon go out of business.
There are 2 exceptions to this rule:
- If you paid separately for development and production copies of a site many years ago (pre-2017), where the development domain has access to a free development license today, we'll gladly reset that for you.
- If you're building a new site for a specific client, which replaces an older site site for that same client that you also built, we may release the old license for you. We do need to, with some certainty, identify that the clients are in fact the same, and may decline if that can't be confirmed.
If you have questions or want to request a reset, please contact support.
It is possible to move licenses to a different account with help from support.
These are the steps you'll need to take:
- If needed, create the new account first.
- Contact support, including the domain, license IDs, and packages, found in your old account, plus the old and the new username. This request must come from the registered email address on the old account. Support will create new licenses on the new account.
- Create an API Key on the new account. Do not use the bookmark - take note of the provided username and API Key.
- Login to the manager of the site, go to Extras > Installer.
- On the Package Providers tab, edit the existing modmore.com provider. Change the username and API Key to the ones you generated in step 3. Save.
- Return to the overview of packages, and check for updates on all packages installed from modmore.com. This will create invalid license issues for all of them, on the new account.
- Go through each of the created invalid license issues, and assign the licenses provided to you by support (in step 2) by clicking on the Assign license block.
- Done? Reply to the support ticket, and we'll verify the licenses are properly assigned on the new account, before removing them from the old account.
Please note that this is a labour intensive process. We may need to charge an administrative fee for large or repeated requests. We may also decline transferring licenses if the original license was part of an expired subscription or for any other reason.