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.
Problem/Motivation
In hopes that we can get greater exposure to using the module, even if it is experimental (which it is), let's expose a link/button to manually update drupal core to the next minor version. This could be called an MVP for updating (manually).
Proposed resolution
No error update XML integreation. Just a link to trigger an in-place update of drupal core to the next minor version. The update will fail if there is *no* next version to update to i.e. trying to update to 8.7.10 won't work because that minor version doesn't exist.
Remaining tasks
User interface changes
API changes
Data model changes
Release notes snippet
Comment | File | Size | Author |
---|---|---|---|
#6 | interdiff_2-6.txt | 4.1 KB | heddn |
#6 | 3087214-6.patch | 8.25 KB | heddn |
Comments
Comment #2
heddnComment #3
heddnComment #4
ressa CreditAttribution: ressa at Ardea commentedIt works perfectly, I just updated from 8.7.6 over 8.7.7 to 8.7.8 flawlessly. It updated so fast, that at first I didn't believe it worked, but it did. Nice job! I assume database updates are run as well, after the files have been replaced?
Might it be worth considering logging which files were updated, as well as database and configuration changes somewhere, so the user can track it, or would that require a lot of work?
Comment #5
heddnGlad it went so smoothly for you.
This is really, really valuable feedback. I like the comments about more feedback. We should add an info log message for each file addition/deletion/modification.
No, there are no db updates in executed (yet). This is _really_ only exercising the download and apply of the update. Emphasis on "minimum" part of the MVP.
Comment #6
heddnComment #8
heddnBased on the feedback from #4, and the fact all that should be addressed... landing this thing.
Comment #9
ressa CreditAttribution: ressa at Ardea commentedThanks for clarifying that no db updates are executed yet. I thought as much, and can now actually also see it, since after updating from 8.7.4 to 8.7.8, I get presented with an option to update, if I visit
update.php
or rundrush updatedb
.