Timeline for Disable modules via database
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 24, 2013 at 16:29 | vote | accept | user2516593 | ||
| Jun 24, 2013 at 15:36 | comment | added | Tim Bezhashvyly | please see my updated answer | |
| Jun 24, 2013 at 15:36 | history | edited | Tim Bezhashvyly | CC BY-SA 3.0 |
added 985 characters in body
|
| Jun 24, 2013 at 15:25 | comment | added | user2516593 | get it. the problem is that I'm trying to upgrade magento from 1.4.0.1 to 1.7 and I'm having problems because of the modules. will try and see... | |
| Jun 24, 2013 at 15:17 | comment | added | Tim Bezhashvyly | Agree with @PetarDzhambazov but on the other hand you can have classes of other extensions which are extending your extension's classes so w/o removing files the functionality will still be triggered. | |
| Jun 24, 2013 at 15:14 | comment | added | Petar Dzhambazov | Some times it is better to disable from modules/{config}.xml files and see if this will do what you want. If you remove all code files and you happen to have an attribute in DB which uses as backend any of the removed classes, you may have broken parts of the site. | |
| Jun 24, 2013 at 15:00 | history | edited | Tim Bezhashvyly | CC BY-SA 3.0 |
added 33 characters in body
|
| Jun 24, 2013 at 15:00 | comment | added | Tim Bezhashvyly |
Not only. To be 100% sure the module is disabled you also have to remove its files from app/code/community or app/code/local depending on a code pool.
|
|
| Jun 24, 2013 at 14:58 | review | Low quality posts | |||
| Jun 24, 2013 at 15:39 | |||||
| Jun 24, 2013 at 14:45 | comment | added | user2516593 | ok, so I need to disable them via xml files? | |
| Jun 24, 2013 at 14:43 | history | answered | Tim Bezhashvyly | CC BY-SA 3.0 |