Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Recently, the official Drupal 5.x seems to have become unsupported. This is causing the Update Status module to report daily module problems. Would it be possible to keep the 5.x branch supported until the Drupal 5.x Core is no longer supported, at least?
Comments
Comment #1
vm commented5.x never had a stable release leaving a -dev release marked as supported when the developer is no longer supporting it doesn't really make sense just so your update status module doesn't report it as unsupported when that is what it is. IMO.
I'll leave this active for the dev to mark as fixed. Also changing category to support request.
Comment #2
deekayen commentedIt was no mistake for me to un-support 5.x and I am aware of the chaos it causes in update status.
Comment #3
vivianspencer commentedIs there a reason you've decided to no longer support 5.x, the dev version works fine for me
Comment #4
deekayen commentedI don't run anymore 5.x sites as of 2 days from now, which makes reproducing bugs and testing fixes a bit harder. It's been several months that D6 has been out and D7 is going to be somewhat involved in coding updates, so I'm dropping 5.x on all my modules to spend more time on 7.x.
Comment #5
vivianspencer commentedJust as reference for others, you can remove the unsupported notices displayed by the Update Status module if you remove or comment out the project line in the modules .info file
Comment #6
junyor commented@vivianspencer: There is no project line in the Drupal 5.x version of the user_readonly.info file.
Comment #7
vm commentedyes there is: marked in bold below:
Comment #8
junyor commentedAh. I'm using a version checked out from CVS, so it doesn't have the stuff added by the drupal.org packaging script.
Comment #9
hapydoyzer commentedGo to admin/logs/updates/settings and mark "User Read-Only" as Warn if out of date: NeverSorry, this not works actually.