- 🇫🇷France dqd London | N.Y.C | Paris | Hamburg | Berlin
Not sure yet, which issue parents the other, but they are more than related. And I would bet that the referenced one would solve this issue here immediately.
If a site has been configured to display PHP notice/warning/error messages in the logs only (not on the screen), Drupal should respect that setting. But currently it ignores that on update.php and always displays them on the screen.
This can cause confusion for people who are not used to seeing such messages in the admin UI but then suddenly see them when they update to a new Drupal version and run update.php. I suspect (but am not sure) that this kind of confusion is evident in some of the comments at https://www.drupal.org/node/2487215 → .
Before I looked through Git history to figure out when/why this behavior was originally added, my guess was that it was probably added somewhere around 2004 and the likely reason was that update.php wasn't capable of sending messages to the logs at that time. I wasn't 100% correct, but pretty close :) #54003: Watchdog not logging update errors →
This behavior is no longer needed, so it should just be removed.
Needs work
11.0 🔥
After being applied to the 8.x branch, it should be considered for backport to the 7.x branch. Note: This tag should generally remain even after the backport has been written, approved, and committed.
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Not sure yet, which issue parents the other, but they are more than related. And I would bet that the referenced one would solve this issue here immediately.