romulossp Posted April 9, 2019 Share Posted April 9, 2019 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 More sharing options...
romulossp Posted April 10, 2019 Author Share Posted April 10, 2019 In debug mode I found this error (attached image), I think the POST request is not correct, does anyone know what I can do? How to fix this? = / Thx. Link to comment Share on other sites More sharing options...
tdsoft Posted April 10, 2019 Share Posted April 10, 2019 I think you removed a module in Core of Prestashop You can do: restore each module for check Link to comment Share on other sites More sharing options...
romulossp Posted April 10, 2019 Author Share Posted April 10, 2019 I have already tried ... I reinstalled the entire system countless times, the problem is specific when I try to disable or uninstall the modules I have no more idea what to do =/ Link to comment Share on other sites More sharing options...
Janett Posted April 10, 2019 Share Posted April 10, 2019 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 ? 1 Link to comment Share on other sites More sharing options...
romulossp Posted April 10, 2019 Author Share Posted April 10, 2019 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 .... Link to comment Share on other sites More sharing options...
romulossp Posted April 10, 2019 Author Share Posted April 10, 2019 if you want see the url format: Link to comment Share on other sites More sharing options...
romulossp Posted April 10, 2019 Author Share Posted April 10, 2019 I see the possible problem ..... I intercepted the methods (old host and new) and saw this problem: (for some reason, prestashop is not completing the url ... which file is responsible for completing it? what can it be? Link to comment Share on other sites More sharing options...
Stickybit Posted August 19, 2019 Share Posted August 19, 2019 Did you ever manage to fix this problem? I get kinda the same error, when trying to upgrade a module. 😢 Error! Could not perform action update for module undefined Link to comment Share on other sites More sharing options...
leozhang84 Posted November 6, 2019 Share Posted November 6, 2019 hello friend. How is it now? I meet the same problem. When I try to disable/enable/uninstall a moudel. it says "could not performance action disable moudel undefined" Link to comment Share on other sites More sharing options...
dan__niel__ Posted November 12, 2019 Share Posted November 12, 2019 I have the same problem, but in my case this message does not even appear. Nothing just happens when I click to; update, configure, uninstall, etc. Link to comment Share on other sites More sharing options...
pmates Posted January 19, 2020 Share Posted January 19, 2020 (edited) 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. Edited January 21, 2020 by pmates (see edit history) Link to comment Share on other sites More sharing options...
eugenata Posted July 9, 2020 Share Posted July 9, 2020 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 2 3 1 Link to comment Share on other sites More sharing options...
Joaquin1982 Posted August 31, 2020 Share Posted August 31, 2020 (edited) Eugenata, your solution worked like a charm. Thank you for sharing. Edited August 31, 2020 by Joaquin1982 (see edit history) Link to comment Share on other sites More sharing options...
edigcrea Posted November 13, 2020 Share Posted November 13, 2020 Thank you Eugenata!!! your solution worked perfectly 😀 in my prestashop 1.7.5.2 Link to comment Share on other sites More sharing options...
cudiah Posted November 21, 2020 Share Posted November 21, 2020 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 More sharing options...
airjohn Posted January 6, 2021 Share Posted January 6, 2021 Worked for me too! Link to comment Share on other sites More sharing options...
maxantuan Posted January 19, 2021 Share Posted January 19, 2021 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 More sharing options...
karine44130 Posted March 5, 2021 Share Posted March 5, 2021 bonjour, je suis embetée , je n'y connais rien et quand j'ai mis en mode debug voila ce que j'ai eu. le souci je ne peux plus revenir sur mon BO comment faire??? Link to comment Share on other sites More sharing options...
karine44130 Posted March 5, 2021 Share Posted March 5, 2021 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 Link to comment Share on other sites More sharing options...
bebsi Posted May 23, 2021 Share Posted May 23, 2021 @eugenata Prestashop 1.7.7.3 - solution works great! Thanks Link to comment Share on other sites More sharing options...
Vazzo64 Posted December 23, 2021 Share Posted December 23, 2021 Great! It works perfectly. Thank you Link to comment Share on other sites More sharing options...
U1yss Posted January 24, 2022 Share Posted January 24, 2022 On 7/9/2020 at 2:08 PM, eugenata said: Tested on Prestashop 1.7.6.4 Doesn't work on my 1.7.7.1 Link to comment Share on other sites More sharing options...
fgb Posted February 6, 2022 Share Posted February 6, 2022 @eugenata Prestashop 1.7.8.3 - solution works great! Thanks Link to comment Share on other sites More sharing options...
Andrejkov Posted June 2, 2022 Share Posted June 2, 2022 (edited) 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 June 5, 2022 by Andrejkov (see edit history) Link to comment Share on other sites More sharing options...
eugenata Posted June 2, 2022 Share Posted June 2, 2022 @Andrejkov try intall module out of debug mode Link to comment Share on other sites More sharing options...
Andrejkov Posted June 2, 2022 Share Posted June 2, 2022 (edited) On 6/2/2022 at 6:31 PM, eugenata said: @Andrejkov try intall module out of debug mode Problem solved. Edited June 5, 2022 by Andrejkov (see edit history) Link to comment Share on other sites More sharing options...
webbrent Posted May 17, 2023 Share Posted May 17, 2023 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 More sharing options...
Rogério Santos Posted October 11, 2023 Share Posted October 11, 2023 Hi, I tried on prestashop 8.0.5, but still not working. Can you help me? Link to comment Share on other sites More sharing options...
Michele Boaretto Posted October 11, 2023 Share Posted October 11, 2023 5 hours ago, Rogério Santos said: Hi, I tried on prestashop 8.0.5, but still not working. Can you help me? Hi, me too, prestashop 8.0.5 and doesn't work, for me is a module i created last week, and i receive always "Could not perform action reset for module undefined" Link to comment Share on other sites More sharing options...
Satmedia Posted November 3, 2023 Share Posted November 3, 2023 (edited) 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 November 3, 2023 by Satmedia (see edit history) Link to comment Share on other sites More sharing options...
jose_ugs Posted November 22, 2023 Share Posted November 22, 2023 Same here, disabling mod_security from the hosting panel did it... and the error was 403, not 406. Link to comment Share on other sites More sharing options...
justmeagain Posted December 21, 2023 Share Posted December 21, 2023 On 4/10/2019 at 3:36 AM, tdsoft said: I think you removed a module in Core of Prestashop Does anyone know where there is an up to date list for PS 8.1.2 to compare against Cheers Link to comment Share on other sites More sharing options...
sinfocomar Posted June 17 Share Posted June 17 If you have any issues updating Modules (or anything else too really), first try disabling Back office token protection under Advanced Parameters, Security. You can reenable it after you're done upgrading. https://docs.prestashop-project.org/v.8-documentation/user-guide/configuring-shop/advanced-parameters/security 2 Link to comment Share on other sites More sharing options...
PhotoArt.it Posted July 19 Share Posted July 19 Salve a tutti Ho lo stesso problema ma con la versione PrestaShop 8.1.5 Versione MySQL: 10.6.18-MariaDB-0ubuntu0.22.04.1 Versione software del server: Apache Versione di PHP: 8.2.21 Limite di memoria: 256M Server gestito con plesk Ho lo stesso problema che andando ad aggiornare i moduli mi dice "Could not perform action update for module undefined" Ho provato tutte le soluzioni sopra descritte ma senza risultato. Grazie a tutti Link to comment Share on other sites More sharing options...
ash-f Posted September 28 Share Posted September 28 On 6/16/2024 at 5:39 PM, sinfocomar said: If you have any issues updating Modules (or anything else too really), first try disabling Back office token protection under Advanced Parameters, Security. You can reenable it after you're done upgrading. https://docs.prestashop-project.org/v.8-documentation/user-guide/configuring-shop/advanced-parameters/security Deleting cache files did not work, but this worked! Link to comment Share on other sites More sharing options...
ps8modules Posted September 28 Share Posted September 28 Hi. The problem is that deleting the cache in the administration does not remove everything and then problems can occur. The quickest solution is to delete everything in the ./var/cache/*.* folder. But it takes a long time. Many modules are developed to clear cache and unnecessary records. Link to comment Share on other sites More sharing options...
Master-Overlord Posted November 25 Share Posted November 25 On 6/17/2024 at 2:39 AM, sinfocomar said: If you have any issues updating Modules (or anything else too really), first try disabling Back office token protection under Advanced Parameters, Security. You can reenable it after you're done upgrading. https://docs.prestashop-project.org/v.8-documentation/user-guide/configuring-shop/advanced-parameters/security This worked with me PS 8.2.0. Thank you! Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now