Timeline for Explain the N-rules in hook_update_N
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 10, 2016 at 8:15 | vote | accept | ostry.sn | ||
| Jan 4, 2016 at 21:44 | answer | added | avpaderno♦ | timeline score: 2 | |
| Jan 4, 2016 at 21:36 | history | edited | avpaderno♦ | CC BY-SA 3.0 |
improved grammar and punctuation
|
| Jan 4, 2016 at 20:55 | comment | added | avpaderno♦ | As far as I recall, what described there was planned, but the actual code just executes any update that has not been yet executed, without making any difference between 71xx and 72xx. I cannot find anything in the code that checks if the installed module was 6.2.x, or 6.1.x. | |
| Jan 4, 2016 at 18:37 | history | edited | ostry.sn | CC BY-SA 3.0 |
Someone suggest me to enhance title
|
| Jan 4, 2016 at 18:18 | comment | added | mona lisa | Perhaps retitle something like "Explain the N-rules in hook_update_N". | |
| Jan 4, 2016 at 17:59 | comment | added | ostry.sn | I can spread it into multiple issues questions related. But I'm not sure that it is the best way because all sub questions are in fact related to a same global issue (N version in hook_update_N) | |
| Jan 4, 2016 at 0:01 | comment | added | mona lisa | It seems that as you are asking multiple questions, it will be difficult to answer. Is there a specific real-world question you are asking? | |
| Jan 3, 2016 at 14:54 | history | edited | ostry.sn | CC BY-SA 3.0 |
added 1 character in body
|
| Jan 3, 2016 at 5:31 | history | tweeted | twitter.com/StackDrupal/status/683520939322138624 | ||
| Jan 2, 2016 at 15:21 | history | edited | avpaderno♦ |
edited tags
|
|
| Jan 2, 2016 at 12:24 | history | edited | Bala |
edited tags
|
|
| Jan 2, 2016 at 11:16 | history | asked | ostry.sn | CC BY-SA 3.0 |