Jump to content

Edit History

pmates

pmates

Not sure, if my issue was the same as this, but I also had Could not perform action update for module undefined error when trying to update modules after upgrade of my shop from 1.6 to 1.7.
In my case the issue was inconsistency between the real version of modules and versions recorded in database. The store keeps the list of all modules and their versions in table ps_module. I'm guessing that modules were updated during upgrade process, but correct values were not updated in the database. In my case the store would tell that I need to update 40 modules. For example it says that the module Best Suppliers should be upgraded from version 1.4.1 to version 2.0.0. But when I looked to the module folder itself, the module was already on version 2.0.0. Updating line for statsbestsuppliers (which is the folder name of this module) in ps_module from 1.4.1 to 2.0.0 fixed the issue.

Going through all modules one by one can be a long work, plus guessing names of modules on top of it, but it seems to work.

UPDATE 1:

After many attempts to upgrade I came across another error, which seems to have solved the "module undefined" issue. As one of the comments suggested, the module Advanced EU Compliance (modules/advancedeucompliance) was causing some similar issues with updates of modules. After uninstalling this module before upgrade to 1.7, modules can now be properly updated. If you already upgraded to 1.7, deleting folder modules/advancedeucompliance may help the same way. The module should be completely uninstalled. Disabling does not seem to be enough. Don't ask me about explanation. This is pure try/fail experience.

Annotation 2020-01-19 212859.png

pmates

pmates

Not sure, if my issue was the same as this, but I also had Could not perform action update for module undefined error when trying to update modules after upgrade of my shop from 1.6 to 1.7.
In my case the issue was inconsistency between the real version of modules and versions recorded in database. The store keeps the list of all modules and their versions in table ps_module. I'm guessing that modules were updated during upgrade process, but correct values were not updated in the database. In my case the store would tell that I need to update 40 modules. For example it says that the module Best Suppliers should be upgraded from version 1.4.1 to version 2.0.0. But when I looked to the module folder itself, the module was already on version 2.0.0. Updating line for statsbestsuppliers (which is the folder name of this module) in ps_module from 1.4.1 to 2.0.0 fixed the issue.

Going through all modules one by one can be a long work, plus guessing names of modules on top of it, but it seems to work. 

Annotation 2020-01-19 212859.png

×
×
  • Create New...