Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.When there is an update available to Drupal or a contrib module I get a warning message on the 'Administer' (/admin) page which takes me to the 'Status report' (/admin/reports/status) page, which then again takes me to the 'Available updates' (/admin/reports/updates) page. There I look which modules (etc.) are outdated, download and override the new ones and then go to update.php. In terms of a streamlined user interface the 'Status report' page should anticipate the visit to update.php similarly to what you find on the 'Modules' (/admin/build/modules) page:
Each time a module is updated, it is important that update.php is run.
Since it doesn't only refer to modules I altered the text to read:
Each time Drupal core or a contributed module or theme is updated, it is important that update.php is run.
Why did I mark such a minor thing CNW?
Even though the patch applies fine there are two issues that aren't quite perfect (that are probably just caused by me being incredibly stupid...)
1. The link to update.php isn't example.com/update.php but example.com//update.php (but the link works, so I'm guessing it's just a problem on my machine
2. I get following error: "Notice: Undefined variable: base_url in update_help() (line 63 of *****\modules\update\update.module). I'm also guessing that this is just a problem with my particular setup.
By the way, if anyone already read this far:
In line 61 of update.module (the patch refers to line 63 of update.module so I guess this is remotely relevant) you read:
$output = '<p>' . t(' ***and so on***
Shouldn't .= be used instead of = ?
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | available-updates.patch | 1.7 KB | swentel |
| available-updates.patch | 1.3 KB | tstoeckler | |
Comments
Comment #1
tstoecklerForget the last four lines, I read through some PHP documentation. Sorry...
Comment #2
swentel CreditAttribution: swentel commentedNice Usability touch. Patch attached fixes the $base_url notice.
Note: I've put the global statement of $base_url inside the case statement of 'admin/reports/updates' since we only need it there - not sure if it makes any difference memory wise, if not, I'll post a patch where it's called just underneath update_help.
Comment #3
tstoecklerTested the patch and it resolves the error logs and does what it should :-). Since this is just not really a big one, I'm setting this to RTBC.
Comment #4
webchickThanks! Committed this to HEAD. :)
It introduces a new string, so I can't really set it back for 6.x. But new users in 7.x will appreciate this, I'm sure. :)
Comment #5
PasqualleIs there a rule, that new strings can't be added to D6?
Comment #6
webchickGenerally, yes. It breaks translations.
Comment #7
moshe weitzman CreditAttribution: moshe weitzman commented/admin actually tells you when you have a pending update. seems better to do that here than to pester the user telling him to go there anytime there is a change.
Comment #9
dddave CreditAttribution: dddave commentedFrom #1210260: adding a link to "update" from /admin/reports/updates: Is this string problem still blocking a backport now that localize.drupal.org eases translations?
Comment #10
smussbach CreditAttribution: smussbach commentedI think we can close this really old issue. It has been pushed to HEAD once and been stripped out again on 09/10/15 with commit 6abcc4.
Since then nothing.