Status report page not functioning with PHP above 7.4 in D7.98

Created on 27 October 2023, over 1 year ago

Problem/Motivation

In D7.98 the Status report page is blank if PHP8.0 or higher is used

Steps to reproduce

Run D7.98 on PHP8.0 or higher and go to /admin/reports/status and you will notice that the page does not work so to read the Status page, I have to downgrade to PHP7.4. I can't find any error message anywhere. The only message is the message on the page itself saying "Le site Web a rencontré une erreur inattendue. Veuillez essayer de nouveau plus tard. / The website has encountered an unexpected error. Please try again later."

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

🐛 Bug report
Status

Postponed: needs info

Version

7.0 ⚰️

Component
Other 

Last updated about 2 hours ago

Created by

🇫🇷France hassebasse

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @hassebasse
  • Status changed to Postponed: needs info over 1 year ago
  • 🇸🇰Slovakia poker10

    Thanks for reporting this. The status page is working on clean D7 install on all PHP versions, but this issue can be caused by some contrib modules which are not upgraded for PHP 8+ compatibility, or do not have this compatibility yet. I suggest to check the Drupal logs (Reports -> Recent log messages) to get the full error message, so that we can figure out which contrib module is the root cause of this issue.

  • 🇫🇷France hassebasse

    Hi

    Does this help you? It is in french but I guess you can follow

  • 🇫🇷France hassebasse

    It gives the above error everytime I try to reload /admin/reports/status

  • 🇸🇰Slovakia poker10

    I would start looking for the error message here in the search . It seems like it is mentioned in a bunch of modules (mostly D8+), but there seems to be some D7 as well (for example Workbench Scheduler). If you are using such module, that could be a root cause of this problem.

    This can also be caused by a custom module, if you have one.

  • 🇫🇷France hassebasse

    Safe cache_form Clear made the trick! If I desactivate it it all work fine, and there are others having experienced the problem, there is even pathces out there.

    https://www.drupal.org/project/safe_cache_form_clear/issues/3307395 🐛 Improper fetchCol() use in hook_requirements causes TypeError Needs review

    I've forgotten how to implement a D7 patch, so I have to figure that out first. Or maybe I don't need to use the module, I'll try that first.

    Thank you for the help !!!

Production build 0.71.5 2024