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 ...What to do if I try to save Instance Registration Key in my admin area, but "Invalid key" error appears?
If you have just created a License Registration project in your amasty.com account and instantly proceeded to save its Instance Registration Key in your Magento backend at Amasty > Products, there's a chance that the information about the created ...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 ...Why some of my module purchases aren't visible in the "Assign the licenses" popup?
If you don't see some of your extension orders in a popup where licenses can be assigned to a project, there's a chance that they were shared to your account from another amasty.com account. If you're not sure about that and would like to check if ...How to check my Magento version and edition (Commerce/Enterprise or Open Source/Community)?
There are at least four simple ways to learn the current version of a Magento instance. Method #1. Admin panel Login to your Magento admin panel and scroll down any backend page to see the version in the bottom right corner: Although the edition is ...
Announcements
⚡ Have you enlarged the functionality of the Amasty extension with your own code? Share your improvements with us!
At Amasty, we understand that some of our clients require customized features to perfectly align the extension with their business needs. If you have developed new functionality within an Amasty module and would like to share it, please submit a ticket