10.3.7 edit missing for all nodes

Don't know why I can't edit any nodes after updating to 10.3.7, but reverting to 10.3.6 restored the edit page for the nodes. This should not happen.

Likely due to: https://www.drupal.org/project/drupal/issues/3485956 💬 Updating phpstan and twig via Composer generates a blank page when editing a node Active

Try updating twig to the version in that issue.

See 💬 Updating phpstan and twig via Composer generates a blank page when editing a node Active . I think this is yet another duplicate.

This is not a blank page, it's a page not found error for any /node/nodenumber/edit page

Oh, I see. Unfortunately there isn't much to go on here. I am not experiencing this bug on sites that I manage so there needs to be more investigation on your end to understand why this occurs.

The 10.3.7 release notes → show all changes. Does anything on that list suggest to you a reason node edits on that site could be broken with this release?

If you are comfortable with Git and can perform a git bisect on a working copy of Drupal core where you can reproduce the bug, you will find the regression commit quickly.

I'm not sure how I would use git bisect. I thought this problem would be universal enough that someone would recognize what happened. It's definitely only when updating to 10.3.7 on my RHEL 9 with nginx and php 8.3.13, 10.5.22-MariaDB.

Nothing in the release notes looked familiar

Changes to the node module are only comments so that can't be it. In fact the difference between 10.3.6 and 10.3.7 is overwhelmingly comments updates. There are just a handful of bug fixes in it.

It's time to look into all the enabled modules on the site. Which are those and what are their versions? Does the site use workspaces? Are any patches applied? If so, which ones?

The only contrib modules I have installed are block_class, google_analytics and backup_migrate. I uninstalled them and couldn't eliminate the problem of not getting any /node/nodenumber/edit to load. They only get the page not found error.
I went back to 10.3.6 and have no problem editing any node. I'll have to stay there until I can figure out what is happening with 10.3.7.

Have you tried updating twig like the linked duplicate?

I have never had to update twig. I don't know how to do that separately from my RHEL updates or within Drupal

This is not the same issue. It's a page not found for any edit of any node.

Could be a similar cause, but why would anyone have to update twig outside of the Drupal core?

It depends how you manage dependencies and contributed modules, but you need twig 3.14.2

If you're not sure how to manage those dependencies then I would recommend waiting for Drupal 10.3.8 that should fix the issue as well.

I have never had to update twig

Neither have I, but when an upstream breaks you need to update it.

This is not the same issue. It's a page not found for any edit of any node.

I'm not convinced it's a different issue. You can confirm by updating twig or waiting for the next release of drupal.

Could be a similar cause, but why would anyone have to update twig outside of the Drupal core?

Because twig broke something, they also fixed it really quickly and that was released already.

Yes, I understand what you are saying and thank you for that, but I wonder if I should try to install something without a specific error about it. I have checked my php installed modules and don't want to try a php-twig addition because it might cause other issues.
I also went through everything I could find in any logs, but I just get the page not found error.
I will keep looking at my logs and try to figure out more details. But if this same issue gets addressed by others soon, hopefully in Drupal core, I would rather get that update than break anything I have working now.
I hope that's safe. I think the 10.3.7 update was not a security patch, so I will wait for a few days and keep searching for answers.

Do you use composer?

I don't use composer, but all dependencies are addressed by our RHEL 9 updates and I have run through the PHP modules to make sure they had the correct dependencies installed also.
The last time I saw something like this, it was a while ago, but it had to do with going from PHP 7.x to 8.x. Missing modules solved the problem then.
Can't find a reason for this one now.

It has nothing to do with system level dependencies.

If you're not using composer then unfortunately your best bet is probably to wait for the next release?

Just out of curiosity how do you update drupal without composer? The tarball?

Yes, the tarball. It's been reliable over different situations when I have to adapt to different VMs provided. I have had to adapt to RHEL, Ubuntu LTS and FreeBSD. I can always use the tarball.

You cannot always use the tarball it as it is slated to no longer be provided: 🌱 [meta] Deprecate tarballs, because they are incompatible with Composer-managed dependencies, Automatic Updates, Project Browser, and release managers' health Active .

For what it's worth I also am not convinced this report is different from 💬 Updating phpstan and twig via Composer generates a blank page when editing a node Active .

If it's the same cause, will there be an update in core that takes care of this? Having to maintain twig updates somehow is something entirely new.

Yes, if you follow the issue we've linked a few times, it's already been fixed, the new release just has not been made yet.

Thanks, that's what I needed to know.
As for composer, it's been a political football for the people I have to rely on for my VMs. When I could roll my own, it was a different situation. But I now have other things to do, which is a good thing, but I still have to run our Drupal to develop the best theme and to host the embedded content my people create.
I can probably convince the others to allow something newer to them, like using composer. Hopefully, this will happen before we move to Drupal 11.x.

10.3.8 does fix my issue of a page not found for any node edit. My error was different than the blank page from the linked bug report.
https://git.drupalcode.org/project/drupal/-/commit/d6c8acf0b3dfc0d2d04b6...
Most likely the same cause, but maybe my nginx installation had timeout or memory related issues with the endless loop and never loaded the page, triggering the classic page not found to be displayed. I hope anyone who gets the page not found can find the solution.
In any case, my thanks to everyone for a pretty quick new release to fix this issue.

Thanks for confirming the 10.3.8 release fixes this for you. Closing as a duplicate of the linked issue as 10.3.7 shipped with Twig 3.14.1 which we know had issues with infinite recursion.