Let's say users have just uploaded new versions of some modules or update core. We should let them know on the status report page that they need to run update.php. Right now it's just a crap shoot. You update some modules, then go to update.php to see if something needs updating. Lots of users think that they have to go to update.php no matter what.
Have a row something like cron...
Database update script - Needs to be run
Modules have recently been updated to newer versions requiring that the database update script be run. Run the database upgrade script.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | update_21.patch | 1.53 KB | RobRoy |
| #1 | update_status.patch | 1.52 KB | Steven |
Comments
Comment #1
Steven commentedHere's a quick patch to do it. The item is shown on the status report (Database schema: up to date / out of date) with a link to update.php if needed. Thanks to the magic of requirements checking, it also outputs a message on /admin, if it's out of date, with a link to the status report.
Bling:
http://acko.net/dumpx/update_status.png
Moving to 5.x because it's a real usability improvement for dealing with modules, and the code is trivial.
Comment #2
Steven commentedComment #3
RobRoy commentedYou are a badass sir. Works perfectly. I added periods to the comments.
Comment #4
dries commentedComment #5
(not verified) commented