Difference between revisions of "Unable to delete modules after updating"
From Joomla! Documentation
m (→What is the cause: Added words used in reports on the forum) |
m (→How to fix: Added sql statements) |
||
| Line 5: | Line 5: | ||
In order to delete modules, you will first need to open the module(s) you want to delete for editing and save them. After this, you will be able to delete the module(s). | In order to delete modules, you will first need to open the module(s) you want to delete for editing and save them. After this, you will be able to delete the module(s). | ||
| + | As an alternative you can use statements below in phpMyAdmin:<br> | ||
| + | delete from #__modules_menu where moduleid in (select id from #__modules where published = -2)<br> | ||
| + | delete from #__modules where published = -2 | ||
| + | |||
| + | As always, replace #_ with your own prefix. | ||
<noinclude> | <noinclude> | ||
[[Category:Version 3.2.0 FAQ]] | [[Category:Version 3.2.0 FAQ]] | ||
</noinclude> | </noinclude> | ||
Revision as of 12:24, 21 November 2013
What is the cause[edit]
When a site is upgraded to 3.2, users are unable to delete modules and are shown a generic "An error has occurred" message. This also applies to trying to empty trash in the module manager.
How to fix[edit]
In order to delete modules, you will first need to open the module(s) you want to delete for editing and save them. After this, you will be able to delete the module(s).
As an alternative you can use statements below in phpMyAdmin:
delete from #__modules_menu where moduleid in (select id from #__modules where published = -2)
delete from #__modules where published = -2
As always, replace #_ with your own prefix.