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.There's code in update.manager.inc to ignore projects that only have -dev releases and force site admins to update those manually. I'm not really sure why it's there. If Update status is smart enough to know if the release is out of date (based on timestamps) I have no idea why Update manager can't be smart enough to upgrade your code. I'd honestly rather just remove this restriction than spend too much time cleaning up the UI at #602496-10: Clean up the update manager project selector page when updating your site (point E). If the only thing that requires manual updates is core (at least until #606592: Allow updating core with the update manager is done), it makes the UI a lot more obvious and simple.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | 613230-1.upgrade_dev.patch | 4.36 KB | dww |
Comments
Comment #1
dwwJacob should comment here before this is committed, but I tried it and it Just Works(tm). Attached patch simplifies a lot of code and UI, and removes an apparently pointless restriction. Definitely makes #602496: Clean up the update manager project selector page when updating your site a lot easier. Seems like all signs point to this being a good move, but maybe Jacob can explain why this restriction was in the original patch (other than the obvious answer that -dev release are evil and we should get rid of them entirely). ;) But, assuming we have them, we shouldn't special-case them here and prevent Update manager from dealing with them...
Comment #2
JacobSingh CreditAttribution: JacobSingh commentedI think this might have been from a missunderstanding way back when in update status. The original patch had dev releaases, but then along the way someone told me that it would offer a dev release if it was newer than a stable release which is currently running. Now that I know more about update status, I don't think this is true. Can you confirm that? If we are not offering people using stable releases dev versions, I'm fine with dev -> dev upgrades.
In the future, something like "config-set preferred_state alpha" (See the PEAR docs) would be ideal.
-J
Comment #3
dwwUpdate status never recommends -dev over stable releases. If it did, that'd be a critical bug.
Comment #4
JacobSingh CreditAttribution: JacobSingh commentedComment #5
webchickYay for removing feature crippling and more lines of code than it adds. :)
Committed to HEAD!
Comment #6
Dave ReidBravo! Very nice change. :)
Comment #8
Anonymous (not verified) CreditAttribution: Anonymous commentedI've just updated Chaos tool suite. The problem is that in the admin/reports/updates/update procedure there is no chance to opt for a -dev version. The update process go only for -alpha1 version.
Comment #9
dwwI believe your issue is being caused by #605318: Add some garbage collection to the update manager...
Comment #10
Leeteq CreditAttribution: Leeteq commentedFYI - Status update 2012..:
I just posted a question about the status of this over at:
#605318: Add some garbage collection to the update manager (comment #68)
(posting this info here, even if the issue is "closed", as this issue has a clearer title related to this issue, for people who find this issue when searching)
[FYI2: Feb. 2012: User name changed from "DanielTheViking" to "Leeteq".
(Adding this manually, as the user account signature doesnt seem to work...)]
Comment #11
dww(User signatures are not added to comments on issues, that's be design -- issues are already hard enough to scan and read -- the additional garbage of user signatures on most posts would be overwhelming noise).