Timeline for Update hooks not being run when module enabled - chicken and egg problem
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 21, 2014 at 18:06 | vote | accept | mtndan | ||
| Mar 14, 2014 at 6:01 | comment | added | Randell | I encountered this very same problem today. Seems so straight-forward, but not. Did you find a solution to this? | |
| Sep 27, 2013 at 15:17 | history | tweeted | twitter.com/#!/StackDrupal/status/383611357457035264 | ||
| Sep 27, 2013 at 13:56 | answer | added | Steven | timeline score: 0 | |
| Sep 27, 2013 at 13:54 | comment | added | Beebee | It seems like a logical thing to do, to put those functions into the hook_install since it's the first time you're enabling the module. Or you can try to enable it without the hook_update_n functions (cut them out), then after enabling it, add it back into the .install and run the db update. | |
| Sep 27, 2013 at 13:38 | history | asked | mtndan | CC BY-SA 3.0 |