I upgraded the edition of my module, but the notice in my Magento admin area mentions the old module edition and says that it's not found, how to resolve that?
It is expected for the subscription of the old module edition to be marked as Not Found, 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 new 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 installed 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’m trying to install the module via composer, but the package is not found. How to resolve it?
Composer is the dependency manager that allows you easily download the required files on your server. The files are located on a remote server, or a repository, that you need to add to the list of “known” ones and authenticate to using the username ...
Why do products have "Not Found" status in the admin area?
There can be several reasons why module licenses aren't found when Instance Registration Key has already been saved in the registration form: Module license isn't linked to the License Registration project. Check if the license is assigned to the ...
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 ...
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 may be several reasons behind that. To find the exact one, navigate to Products tab of your amasty.com account, find the necessary license by ...