I upgraded the edition of my module, but the notice in my Magento admin area still mentions the old module edition and says that it has been cancelled, how to resolve that?
It is expected for the subscription of the old module edition to be marked as Cancelled, as it is replaced with new subscription for the upgraded edition (for example, if you upgraded from Pro to Premium). In order to eliminate the warning that is displayed in your admin area, you can remove the package with the old module edition from your instance. This is a wrapper package that doesn't contain any functionality inside, so, if you already have an upgraded package installed, removing the old package shouldn't influence the environment.
You can delete the package following these steps:
Make sure that you're removing only the wrapper package, and not the base packages with main module functionality. Wrapper packages normally mention module edition and subscription in their name (for example, Pro, Pro Subscription Package, Cloud Pro, etc.)
- Check that you already have the package with upgraded module edition installed;
- Create backups of your root Magento directory files in case any changes need to be reverted;
- Remove the package with the old edition:
- If you install modules manually via app/code directory, simply remove the folder from app/code/Amasty;
- If you're using composer to install modules, run this command, using the name of the old package instead of amasty/package-name:
composer remove amasty/package-name
Run the following commands for your instance to run properly after removing the package:
php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento setup:static-content:deploy
Related Articles
I see messages in my account and admin area that license registration is required, what should I do?
We introduced License Checker functionality inside our extensions in order to create a connection between the purchased products and Magento instances where the products are installed, it helps us make sure that module licences are used in accordance ...
I have inserted my instance registration key into admin area settings and assigned licenses to a project in my amasty.com account, but there's still a notice that some of Amasty subscriptions have been cancelled or have limited access, why?
There is a variety of reasons why a product license can be marked as cancelled or limited. We recommend reviewing order and subscription history in your amasty.com account to check if your case matches the examples below: A module was purchased ...
How to proceed if I need to update Amasty Base extension?
To finish license registration for your amasty.com account, you need to enter your Instance Registration Key into our Base module functionality that becomes available with v.1.16.0 and newer. In order to check your Base module version and its latest ...
How many projects and registration keys are needed for a multi-website Magento instance?
If you have several websites under one Magento installation, only one project and one registration key need to be created. When entering domain name for a project, you may use the domain name of Magento's backend.
Can we use one and the same extension license on several websites?
An Amasty extension is not domain-related, but installation-related. If you run each website on a new Magento installation, you need a separate license for each of them. However, if you run several domains on the same instance of Magento, you can use ...