Timeline for How to disable a troublesome module that causes admin/modules to not list all modules?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:46 | history | edited | CommunityBot |
replaced http://drupal.stackexchange.com/ with https://drupal.stackexchange.com/
|
|
| Feb 17, 2016 at 16:23 | history | wiki removed | Robert Cartaino | ||
| Oct 8, 2015 at 9:59 | history | made wiki | Post Made Community Wiki by avpaderno♦ | ||
| Oct 7, 2015 at 12:22 | history | edited | Pierre.Vriens | CC BY-SA 3.0 |
added 55 characters in body
|
| Jul 14, 2015 at 16:20 | vote | accept | Pierre.Vriens | ||
| Jun 15, 2015 at 7:42 | comment | added | Mołot | No problem. I only pointed that out because I screwed one of my sites that way. Nothing production, of course. For 2nd option - if one have BaM installed, he can save SQL command to file, and then use "restore" option. It will upload and execute file, any SQL file. | |
| Jun 15, 2015 at 5:29 | history | edited | Pierre.Vriens | CC BY-SA 3.0 |
added 326 characters in body
|
| Jun 14, 2015 at 20:12 | comment | added | Mołot | Deleting files is problematic, because it prevents you from ever running uninstall on module. Registry rebuild will not fix that, as far as I know. so generally 3 shouldn't be suggested without strong warning, and claim that another module may repair things is bold one. | |
| Jun 14, 2015 at 19:15 | history | answered | Pierre.Vriens | CC BY-SA 3.0 |