WSOD on existing node edit pages after updating to D10

Created on 29 November 2023, 12 months ago
Updated 12 March 2024, 8 months ago

Problem/Motivation

I'm looking to update my production site to D10, but there are two standing issues. One stems from this module, and the other from the Office Hours module.

Both suffer from a strange issue that I cannot seem to reproduce outside of my development domain.

I am getting a WSOD with no errors on-page. The only place I can produce errors are the Apache logs. They are as follows.

Trying to access the edit page directly, e.g. /node/1/edit.

[Wed Nov 29 10:09:19.663263 2023] [proxy_fcgi:error] [pid 16442:tid 47477654836992] [client {public ip}:0] Premature end of script headers: index.php
[Wed Nov 29 10:09:19.663323 2023] [proxy_fcgi:error] [pid 16442:tid 47477654836992] [client {public ip}:0] AH01070: Error parsing script headers
[Wed Nov 29 10:09:19.663329 2023] [proxy_fcgi:error] [pid 16442:tid 47477654836992] (22)Invalid argument: [client {public ip}:0] AH01075: Error dispatching request to :

Trying to access the edit page via the content panel.

[Wed Nov 29 09:42:49.584846 2023] [proxy_fcgi:error] [pid 16440:tid 47477690558208] [client {public ip}:0] Premature end of script headers: index.php, referer: https://{domain}/admin/content
[Wed Nov 29 09:42:49.584918 2023] [proxy_fcgi:error] [pid 16440:tid 47477690558208] [client {public ip}:0] AH01070: Error parsing script headers, referer: https://{domain}/admin/content
[Wed Nov 29 09:42:49.584923 2023] [proxy_fcgi:error] [pid 16440:tid 47477690558208] (22)Invalid argument: [client {public ip}:0] AH01075: Error dispatching request to : , referer: https://{domain}/admin/content

If I remove the element from the content type's form display, the error is no longer present.

I have created a node with data identical to a problem node's data and confirmed they were stored the same in the database.

At this point, I am at a loss for how to proceed. Any help would be much appreciated, as this is a production-blocking issue preventing me from updating to D10.

Steps to reproduce

Cannot reproduce outside of my D10 development environment.

πŸ’¬ Support request
Status

Fixed

Version

2.0

Component

Miscellaneous

Created by

πŸ‡ΊπŸ‡ΈUnited States FrankieD3

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

Comments & Activities

  • Issue created by @FrankieD3
  • Status changed to Postponed: needs info 10 months ago
  • πŸ‡­πŸ‡ΊHungary nagy.balint

    Hi!

    Yes, unfortunately I cannot reproduce it either.

    Could be something related to server configuration, or collision with another module.

  • Status changed to Fixed 9 months ago
  • πŸ‡ΊπŸ‡ΈUnited States FrankieD3

    I've finally stumbled across a solution. It seems to have been caused by the http.response.debug_cacheability_headers parameter in development.services.yml being set to true.

    Setting http.response.debug_cacheability_headers: false fixed things right up.

    Thanks!

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024