- Issue created by @tyler36
- π―π΅Japan tyler36 Osaka
Even a message output of "Please check for database updates by visiting the status page and clicking the link if required", run via the
post-update-cmd
would help new developer. - Status changed to Closed: works as designed
over 1 year ago 6:26pm 8 December 2023 - πΊπΈUnited States phenaproxima Massachusetts
This seems like it's not in the scope of the Automatic Updates module; it has nothing to do with running database schema updates. So I think I'm gonna close the book on this one, but feel free to reopen if I've missed something.
- Status changed to Active
7 months ago 5:21pm 22 September 2024 - πΊπΈUnited States tr Cascadia
This doesn't seem like it's in the scope of the Automatic Updates module, which has nothing to do with running database schema updates.
I think the OP stated things well. Specifically, a lot of users, especially those coming from environments where every update task is handled by Composer, might be unaware of the need to separately check for and run database updates after updating the code with Composer. OR might be aware and just forget to do it. It happens to all of us, and in many cases a site can run perfectly fine for a long time even if the database update was neglected.
Ensuring that all the steps are taken, including database updates, seems to be fully in scope for this module. And in fact the project page itself says:
Automatically detects database updates in an incoming update, and helps you run them during the update process.
Likewise, as the OP stated, the Drupal core issue β¨ Use composer scripts to automate schema update Closed: duplicate was closed by @cilefen and @longwave because, as they said, this issue is something that is being handled by the Automatic Updates initiative.
@phenaproxima: so please clarify - is this task something that belongs in Automatic Updates or does it belong in Core?
Using a composer script to automatically run update.php or to at a minimum output a message informing the user that updates need to be run (and how to run them) seems like a no-brainer improvement that will help stop some common problems and make Drupal easier to update. Which again, seems to be exactly what the Automatic Updates initiative is intended to do.