WSOD on node edit upon updating from 8.x-1.9 to 8.x-1.12

Just to be sure, the problem is when you start editing a node, not when you just have saved an Edit form?

Did you enable 'All messages, with backtrace information' on the following page? /admin/config/development/logging

Correct on both accounts.

I can also confirm this is present on PHP 8.1.25.

The only variable between my production and dev site that I am aware of is the module version.

What happens if you update per version? First 1.10, then 1.11, then 1.12?
Can you pinpoint to a specific version?

Do you see any relation with 💬 WSOD on node edit upon updating to 8.x-1.12 Active ?

I'll go ahead and test the intermediary versions. My apologies for the late response.

I've gone ahead and reverted to 1.10, and strangely, the issue persists.

Perhaps it could be related to a core update? I only go about updating the development domain when new features need to be implemented, so there are a handful of updates that were run at the same time.

I am wracking my brain for any other variables, and I'm coming up empty handed.

Then, the problem could still be in the upgrade from 1.9 to 1.10, correct?

Please check the field settings. And disable/resave any exceptions and season settings. Test, then enable, if needed. Let's see if you encounter a difference somewhere to pinpoint the problem.

Downgrading to 1.9 yields the same results, as does toggling and resaving the field settings.

I do recall that I had a similar issue on a D9 install a while back, though the error wasn't silent. I've checked the composer.json on this other domain, and it has a static version of 1.9.0.

If I call correctly, that issue had to do with seasons, though they weren't being used.

I'm not sure if this is relevant, but given that the same base composer.json was used initially for both of these installs, it could be connected.

Sorry, in comment #8 I added the wrong link. It is now corrected. It points to 🐛 Ajax error on [Add exception] button if "seasons" is activated Active .

Having both exceptions and seasons enabled in the widget was the root cause over there.
However, the error only appeared if you press the [Add exception] button.
Yo could try new dev version.

Dev also fails. Given this seems to be an isolated issue, should we table it for now and revisit it in the future? There doesn't seem to be too much to go off of, and I'm not sure what other information I could supply at this point.

Yes, I do not know how to proceed here.
But will you then NOT update, for now?

I suppose so, as this install has thousands of nodes with existing hours that my content team needs access to.

For now I will stay on a static version of 1.9.0 on production.

If I manage to produce an error I will bump the issue with any new information.

Thanks much for attempting to help me diagnose the issue.

BTW, as you have so many entities, what are your thought on ✨ Exceptions that apply to entire bundles Active ?
(please respond over there)

I've finally been able to produce an error through the Apache error logs, though it may not be too useful. This is the only trace of an error whatsoever, and only appears when in relation to Office Hours being present on the form. I assume this out of the scope of the project, and a deep rooted configuration issue?

[Tue Nov 21 15:36:28.727122 2023] [proxy_fcgi:error] [pid 1376:tid 47477690558208] [client {local ip}] Premature end of script headers: index.php
[Tue Nov 21 15:36:28.727182 2023] [proxy_fcgi:error] [pid 1376:tid 47477690558208] [client {local ip}] AH01070: Error parsing script headers
[Tue Nov 21 15:36:28.727188 2023] [proxy_fcgi:error] [pid 1376:tid 47477690558208] (22)Invalid argument: [client {local ip}] AH01075: Error dispatching request to :

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.

Strange that the issue cropped up specifically when I upgrade Office Hours. Either way, I've solved it.

Thanks!

Good to hear that.