Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.hey there,
the update page advises us to not run the update script twice "as it may cause problems". but twice when? twice in a row? twice in a week?
say I make an upgrade on a module, run the script, then upgrade ANOTHER module within an hour: should I run the update script?
regards,
Luciano
| Comment | File | Size | Author |
|---|---|---|---|
| #12 | upgrade_clarity_2.patch | 1.42 KB | ainigma32 |
| #9 | upgrade_clarity.patch | 660 bytes | 13rac1 |
Comments
Comment #1
stevenpatzComment #2
dave reidCould you please link to the page you're talking about?
Comment #3
13rac1 commentedDave: spatz is talking about http://www.yourdomain.com/update.php.
Spatz: "Don't upgrade your database twice as it may cause problems." means that you shouldn't do it again without reason. It is correct to run it again when there are new changes to the system, such as a new module.
Comment #4
ainigma32 commented@rmrfstar: errm.. that would be lucoweb asking the question ;-)
@lucoweb: please post back whether rmrfstar's info answers your question.
I suppose the question is if this text should be changed/improved or not and, if so, what the new text should be.
- Arie
Comment #5
13rac1 commentedI wrote lucoweb! I didn't write a different name! Haha.
Maybe change "Don't upgrade your database twice as it may cause problems." to "Upgrade the database only when there has been changes to the system, otherwise it may cause problems." ?
Comment #6
ainigma32 commentedOK now if you could put that into a patch http://drupal.org/patch/create it might make it into core...
- Arie
Comment #7
ainigma32 commentedLooks like rmrfstar won't be posting any feedback so I'm setting this to fixed.
Feel free to reopen of you think that is wrong.
- Arie
Comment #8
13rac1 commentedBeen too busy.. I will make a patch shortly.
Comment #9
13rac1 commentedIt was super fast. I just needed to get a project done.
Comment #10
luco commentedyes, that's it. thanks for the clarification o/
Comment #11
luco commentedyes it does. I aggree with the text change. thanks!
Comment #12
ainigma32 commentedPatch doesn't apply. Rerolled.
- Arie
Comment #13
tr commentedThis is not an issue in Drupal 6.x, 7.x or 8.x, as the upgrade text has been changed quite a bit.
Changing status to won't fix because 5.x is no longer supported.