Jump to content

Problem prestashop Module - module undefined


Recommended Posts

 

Hello everybody, I'm having a problem with my prestashop, after migrating from server when I'm going to disable or delete a module following message is returned:
 

"Error! Could not perform action disable for module undefined"

I already tried everything but nothing solve
What should I do =/?
Link to comment
Share on other sites

In your screenshot, the request as a missing / in url. http://zugbox.commanage/action/disable/ps_banner?_token=blabla       instead of http://zugbox.com/manage/action/disable/ps_banner?_token=blabla

Can you go in Advanced Parameters -> Information and take a screenshot ?

  • Like 1
Link to comment
Share on other sites

2 hours ago, Janett said:

In your screenshot, the request as a missing / in url. http://zugbox.commanage/action/disable/ps_banner?_token=blabla       instead of http://zugbox.com/manage/action/disable/ps_banner?_token=blabla

Can you go in Advanced Parameters -> Information and take a screenshot ?

Of course my friend ....

Screenshot at 2019-04-10 08-11-44.png

Screenshot at 2019-04-10 08-11-56.png

Link to comment
Share on other sites

  • 4 months later...
  • 2 months later...
  • 2 months later...

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

Edited by pmates (see edit history)
Link to comment
Share on other sites

  • 5 months later...

HI guys

I've had the same problem. It seems to be due to a wrong cache.

Solved in this way:

1) Clear the cache using the appropriate command in Advanced parameters> Performance
2) enable debugging (Advanced parameters> Performance)
3) Reload or open the Modules section (Modules> Module Manager)
4) Clear the contents of the / var / cache / folder
IMPORTANT: you must delete both / dev and / prod folders
5) Remove the debug mode

That's all.

Go back to the Modules section and try to deactivate or uninstall a module, it should work.

Note: sometimes enabling the debug mode we may receive an error page with the list of exceptions. This makes it impossible to see the back office. In this case it is necessary to edit manually the configuration file al line 29:

/config/defines.inc.php

From:

define('_PS_MODE_DEV_', true);

to:

define('_PS_MODE_DEV_', false);

Tested on Prestashop 1.7.6.4

  • Like 2
  • Thanks 3
  • Sad 1
Link to comment
Share on other sites

  • 1 month later...
  • 2 months later...
On 7/9/2020 at 2:08 PM, eugenata said:

HI guys

I've had the same problem. It seems to be due to a wrong cache.

Solved in this way:

1) Clear the cache using the appropriate command in Advanced parameters> Performance
2) enable debugging (Advanced parameters> Performance)
3) Reload or open the Modules section (Modules> Module Manager)
4) Clear the contents of the / var / cache / folder
IMPORTANT: you must delete both / dev and / prod folders
5) Remove the debug mode

That's all.

Go back to the Modules section and try to deactivate or uninstall a module, it should work.

Note: sometimes enabling the debug mode we may receive an error page with the list of exceptions. This makes it impossible to see the back office. In this case it is necessary to edit manually the configuration file al line 29:

/config/defines.inc.php

From:


define('_PS_MODE_DEV_', true);

to:


define('_PS_MODE_DEV_', false);

Tested on Prestashop 1.7.6.4

Thank you.

Your solution worked.

Link to comment
Share on other sites

  • 1 month later...
  • 2 weeks later...
On 7/9/2020 at 1:08 PM, eugenata said:

HI guys

I've had the same problem. It seems to be due to a wrong cache.

Solved in this way:

1) Clear the cache using the appropriate command in Advanced parameters> Performance
2) enable debugging (Advanced parameters> Performance)
3) Reload or open the Modules section (Modules> Module Manager)
4) Clear the contents of the / var / cache / folder
IMPORTANT: you must delete both / dev and / prod folders
5) Remove the debug mode

That's all.

Go back to the Modules section and try to deactivate or uninstall a module, it should work.

Note: sometimes enabling the debug mode we may receive an error page with the list of exceptions. This makes it impossible to see the back office. In this case it is necessary to edit manually the configuration file al line 29:

/config/defines.inc.php

From:


define('_PS_MODE_DEV_', true);

to:


define('_PS_MODE_DEV_', false);

Tested on Prestashop 1.7.6.4

Thanks, It works

Link to comment
Share on other sites

  • 1 month later...

j'ai trouvé ça

Si vous n'avez pas accès au backoffice :

Utilisez votre client FTP habituel pour ouvrir votre fichier /config/defines.inc.php sur votre serveur d'hébergement

Dans ce fichier passez à ON l'option display_errors
remplace define('_PS_MODE_DEV_', false);
par define('_PS_MODE_DEV_', true);

Enregistrez votre fichier sur votre serveur

 

je trouve bien le fichier /config/defines.inc.php, mais pares comment j'ai accès à la suite, je ne vois pas???

merci de votre aide

debug suite.png

Link to comment
Share on other sites

  • 2 months later...
  • 6 months later...
  • 1 month later...
  • 2 weeks later...
  • 3 months later...

Hello,

I have same problem but soulution from @eugenata doesnt work for me. 

When i try to update module i got error2.jpg, error3.jpg.

When i try to install new module i got this error1.jpg (but in folder modules they are created new folder with module files but in backoffice is look like not installed). 

Can someone help me?

=======================

Problem solved

 

 

Edited by Andrejkov (see edit history)
Link to comment
Share on other sites

  • 11 months later...
On 7/9/2020 at 1:08 PM, eugenata said:

1) Clear the cache using the appropriate command in Advanced parameters> Performance
2) enable debugging (Advanced parameters> Performance)
3) Reload or open the Modules section (Modules> Module Manager)
4) Clear the contents of the / var / cache / folder
IMPORTANT: you must delete both / dev and / prod folders
5) Remove the debug mode

Thank you @eugenata this worked for me and sorted out my problems as well...

Link to comment
Share on other sites

  • 4 months later...
  • 4 weeks later...

Hi,

same problem on 8.1.2. Cache solution was not working for me 😞

I took a look in the browser console . I got this  Error 406 on POST xhr

https://presta.******.com/******/index.php/improve/modules/manage/action/upgrade/ps_facetedsearch?source=https%3A%2F%2Fapi.prestashop-project.org%2Fassets%2Fmodules%2Fps_facetedsearch%2Fv3.14.0%2Fps_facetedsearch.zip&_token=_*********************

error.log on Apache Server shows this:
[Fri Nov 03 08:07:07.229400 2023] [:error] [pid 482930:tid 140311305103104] [client ***.***.***.***:0] [client ***.***.***.***] ModSecurity: Access denied with code 406 (phase 2). Pattern match "=(?:ogg|tls|ssl|gopher|file|data|php|zlib|zip|glob|s3|phar|rar|s(?:sh2?|cp)|

Solution: Disable mod_security (firewall) on Server. Update the modules --> all OK. Enable mod_security again 😉

 

regards, Roland

Edited by Satmedia (see edit history)
Link to comment
Share on other sites

  • 3 weeks later...
  • 5 weeks later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...