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
Sometimes when core updates we cause the site to be truly broken if you don't run update.php. For example #2861863: InvalidArgumentException "Field is unknown" in ContentEntityBase. Users forgot about this and we offer unhelpful error messages when all they need to do is run update.php and everything is good.
Proposed resolution
If we need to rebuild the container because the version has changed we should force people to update.php
Remaining tasks
User interface changes
API changes
Data model changes
Comment | File | Size | Author |
---|---|---|---|
#2 | 2877643-2-2.patch | 3.62 KB | alexpott |
Comments
Comment #2
alexpottIf we go down this route we need to also ensure that update.php rebuilds the container even if there are no updates.
Comment #4
alexpott@catch has suggested checking this in error handler so if there is an error we could try to check if there are db updates and recommend going to update.php. Obviously we'd need to be careful about obscuring real errors.