@cilefen

I tried to follow the steps to reproduce and although I think I am close, I don't fully understand the steps, or what is the expected behavior. Enhanced steps to reproduce, screen shots, or even a short video may explain more fully this bug.

xjm → credited cilefen → .

Drupal is ready to be set up properly to parse forwarded-for headers. At this stage you may wish to consult XAMPP support or with a systems administrator to debug your specific setup.

Again, this is not a bug in Drupal.

This is "needs work" for #5.

Would you execute a git bisect on a working copy of Drupal Core? That will quickly find the commit that changed this behavior, which is the best way to understand the situation.

Does this duplicate one of the issues related to 🌱 Dealing with unexpected file deletion due to incorrect file usage Active or is this a newly-identified bug?

Please submit this as a merge request so the bots can test it. Even though 📌 Make tests pass Active exists we need to know if there are new failures. This itself may need some regression tests added.

The merge is enormous. Something is wrong with the diff.

Are there CKEditor bug reports of the same?

As I said in comment 17, it would be nice if someone would compare the phpinfo pages of each PHP version on MAMP with a diff program and report back. That will probably explain the cause of your problems in PHP 8.3 with these platforms.

As a way to begin an investigation, please add to the issue summary the verified steps to reproduce the bug on a newly-installed Drupal site.

So do I understand that this is solved and that it's not directly connected to Webform?

What is the theme I see there?

Ok, let us know what you find in your investigation as to the cause.

I am closing this support request since it's been another year without an update.

I am closing this due to no updates in six months.

This would need to be profiled to have any idea what's going on.

There isn't much to go on with this reported critical bug, so we'll have to investigate based on more information from you.

• Was there a version of Drupal where this did not occur? That is, did a specific upgrade cause the change?
• Are there any errors logged by Drupal?
• You marked this issue as a bug in the "cache system" core component. Is the site using the default database cache backend or another?
• Are any patches applied to the site?
• Which modules are installed and what are their versions?
• Is the bug platform-specific? That is, have you been able to reproduce it on Drupal sites that are not hosted the same way?

Could we have screenshots/videos as appropriate and a merge request so the bots can test it?

I don't think anyone will merge a new global scope function.

It’s probably 💬 Updating phpstan and twig via Composer generates a blank page when editing a node Active . What is the Twig version?

function system_preprocess_block, which is what establishes this value, hasn't changed in 7 years, and the particular section that sets site_name hasn't changed in 10 years.

We'll have to investigate and gather more information from you to understand what is going on.

On which version of Drupal was this last working?

Can we get full bug reproduction steps on a clean Drupal 10.3 install?

If you would like to perform a git bisect on a Git working copy of Drupal Core, you will quickly find the regression commit.

We need the information from comment #19 to proceed. The steps you gave continue to cite S3. Provide the steps to reproduce the bug on a newly-installed Drupal site that you verify are reproducible.

I am making this a support request as there is no clear indication this is a Drupal Core bug. It's some setup issue with S3 and possibly an unanticipated use-case.

To keep our eyes on the changes: https://github.com/twigphp/Twig/compare/v3.14.0..v3.14.2

Indeed the next step is to profile → to find the exact cause.

The changes: https://github.com/twigphp/Twig/compare/v3.14.0..v3.14.2

Have you profiled → to find out what exactly is slow?

I think we have a regression report at: 🐛 Translating path aliases in workspace does not work Active .

@iselectweb Are you able to reproduce the bug on https://simplytest.me?

This is not critical because you can disable big pipe to work around it. Additionally, page_manger module doesn't have a supported stable release.

This is not critical because you can disable big pipe to work around it.

Are there error messages logged by Drupal or in the browser console?

Unfortunately, Drupal 9 isn't supported on drupal.org any more. Upgrade the site to a supported release and re-activate this issue if the bug occurs there.

There isn't much to go on with this critical bug report. It is probably 💬 Updating phpstan and twig via Composer generates a blank page when editing a node Active . Please confirm the version of twig.

@iselectweb We need that information in the issue summary or unfortunately this issue will not get attention.

@nikunj_24 See https://www.drupal.org/community/contributor-guide →

The test bots don't test patches any more. Please would you open a merge request?

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 .

It could be a platform problem on your end. Have you profiled the PHP execution?

Please update the steps to reproduce starting with installing Drupal, so others can duplicate the bug, because this seems unusual and I think there are other factors leading to the bug that are not shown.

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?

APCu is not always enabled by default on the CLI, if that is the use-case.

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 haven't been able to reproduce this given the steps above.

I did the following:

1. Installed Drupal 10 with https://simplytest.me.
2. Installed the Content Translation module and added a second language.
3. Configured the article content type to be translatable.
4. I created an article node in English.
5. I added a node translation in the second language.
6. I browsed to the published second language node.
7. I did not observe a performance problem.

So, you will have to continue to investigate on your own and you must provide much more detailed steps to reproduce that can be followed by contributors.

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

What is the output of composer show twig/twig?

We are not experiencing this on our end. Can you confirm the value of the VERSION constant in core/lib/Drupal.php?

What is the output of composer show twig/twig?

This looks like a duplicate of 🐛 Rewrite as URL adding equals sign to end of url. Needs work . Can you confirm?

This is 💬 Updating phpstan and twig via Composer generates a blank page when editing a node Active . Read the information there.

This is probably 💬 Updating phpstan and twig via Composer generates a blank page when editing a node Active . Can you confirm?

What problems does this normalization cause?

It’s probably 💬 Updating phpstan and twig via Composer generates a blank page when editing a node Active .

It’s probably 💬 Updating phpstan and twig via Composer generates a blank page when editing a node Active . What is the Twig version?

3.41.1 exhibits bugs in Drupal. See 💬 Updating phpstan and twig via Composer generates a blank page when editing a node Active .

This is not a bug because the delete form properly warns the administrator what will happen. We added that in 🐛 When deleting a content type field, users do not realize the related View also is deleted Fixed . In the past Drupal did not warn you!

This could be a feature request, but in that case it may not actually be save to adjust the permissions of views because that could make the views available to others, etc. It would have to be done carefully.

Finally, be sure to test on a supported release. 10.1.x is unsupported.

This is a bit of a classic support request for PHP platforms. It is quite likely you have different versions of PHP for the webserver than for the CLI. Type php --version and let's see the output.

30 minutes sounds impossibly slow to me also! How large is the configuration you are testing with?

The usual way is to add a conflict.

“Use replacement tokens be from the first row” isn’t English.

Does the error occur if you uninstall the custom/experience_builder module that is throwing an exception? Can you provide a stack trace?

I am marking this as needing more steps to reproduce because additional modules are needed for the setup that are not mentioned on the steps.

Which documentation page or file needs to change?

If this is local development your IP address is 127.0.0.1 and this working as expected. Which IP address were you expecting?

My advice is to use DDEV instead of XAMPP.

Thank you. Is that on a newly-installed site without added modules or patches?

This looks like a possible duplicate of a prior report.