@cilefen

A pager system unit test failed on the branch.

@lazzyvn: You did report it, here. @lendude, from comment 4, is a Views maintainer. As far as I can see you did not reply to their comment.

In 📌 Update stylelint rule unit-allowed-list to include container query units Fixed , this was the CSS component, so I'm just moving it there and updating the category to match. I don't see a reason not to do this.

@nicxvan The stack track says otherwise. Is that the problem here?

This is more to remind myself: we are looking for invocations of hook_preprocess_node when the node key is missing from the $variables array, and then to determine what removed node.

Believe it or not, there isn't much more to debuggers, so you are getting experience right now!

Yes, you are in the right place. You want to check the $hook value where you put your breakpoint to be sure you are only looking at the arguments for hook_preprocess_node, because every hook invocation will pass through that function.

If that's frustrating because of the large number of callers, you could move your breakpoint up the call stack into ThemeManager, around line 293, where the preprocessor hooks are determined. There you will see only theme-related hook invocations.

@euk It's not my issue. @yuliang061 opened this in Drupal Core.

A next step would be to set a breakpoint in Drupal\Core\Extension\ModuleHandler->invoke and watch how $variables, which may have a different name inside invoke, changes as each hook executes. This will provide insight into when node is removed.

There are many existing issues about international telephone validation, some of which are organized at 🌱 [meta] International Telephone Validation Support Active .

Can you examine the call stack when stopped at those breakpoints?

I fixed an its vs it’s typo in the title.

This is possibly a duplicate of 📌 Make cron time limit a variable Postponed: needs info . Can you verify?

@walterp, can you get the call stack when at that breakpoint? That will, I hope, show the prior hook function invocations.

@walterp You will have to halt execution to see the values, using something besides dpm. I'm sorry that wasn't clear. dpm is limited by not being able to run through errors or exceptions. Alternatively, you could use a real debugger, like Xdebug, and set a breakpoint on that line.

@walterp It is necessary that you debug $variables above the line on which the error occurs.

What is that output in 11.3.x? This is what I add am asking for.

Is this resolved?

"Needs review" is a status, not a tag, and it's for when there is a proposed code change to review.

Please add the steps needed to reproduce the bug to the issue summary. To be effective, the steps should be validated by you, using a new Drupal install.

There isn't much to go on here.

Would you update this issue’s title and add steps to reproduce to the issue’s summary?

Steps to reproduce validated by you on a newly installed Drupal site will be most useful to finding a resolution to this bug.

@l.b.

To accelerate a release, test code in the sub-issues and provide feedback. Test the 6.3.x branch releases to uncover any undiscovered bugs.

What are the contents of the $variables array when node is null within it?

This is a theme hook so let’s leave this issue in the theme system for now, unless you have identified the Core commit that changed the hook’s behavior and it’s in the Node system.

What is the content of $variables in this case?

This was discussed on a prior issue and in fact there is a documented way to exclude the file. I understand this issue has different ideas.

Would you answer my question?

Some are reporting the same on another issue.

There are more steps to reproduce the bug which need to be documented.

Is there an update?

@drupal_developer2022: If you are uncomfortable with debugging but comfortable with installing patches, I can provide you with a patch that will provide more information to help resolve this issue.

You assigned this issue to yourself, so I assume that means you are debugging it. To start, I would like to know what the contents of $this->definition in FieldPluginBase.php, line 484, are when this occurs.

What was the upgrade process you took? I am tentatively marking this a support request due to the resolution of 🐛 Upgrade to 6.3-beta3 fails (both auto and manual) Active .

Add the multilingual setup to the steps to reproduce.

It isn’t clear whether commenters are saying this bug is a recent regression. If it is a regression, a community member who can reproduce the bug could perform a git bisect on a working copy of Drupal Core to quickly find when the bug was introduced.

Is Bootstrap Layout Builder absolutely necessary to reproduce the bug?

A maintainer couldn’t reproduce the bug which suggests there are additional steps to reproduce it.

I add m sorry I misread this. It looks like a problem with the Token module.

This is the sixth report.

It's probably not pertinent to this specific task, but release target tags would be better as milestones in GitLab.

This looks like another duplicate of 🐛 White screen and "try again later" error after updating from Drupal 11.2.10 to 11.3.0 Active .

The following is the documentation to debug these browsers:

• https://developer.chrome.com/docs/devtools/remote-debugging
• https://firefox-source-docs.mozilla.org/devtools-user/about_colon_debugg...

Upgrade Node on the system.

The error message says "Check your browser's developer console for more details." What does the browser's developer console say about this error?

Thanks for this report. I commented to mention this on 🐛 Remove duplicate "add block" link from block content type view's "Results not found" message Postponed .

The config update change added an explicit dependency on the Views module.

Would you perform a git-bisect operation on a working copy of Core to find the regression commit?

I overlooked WebformSubmissionLogManager in my findings. That's probably the one! It looks like a simple fix.

I had a quick and cursory look at the Webform codebase, and only at a glance, I see users_field_data being aliased to u but not to user.

@vasyok May we see the output of composer install -vvv? I doubt whatever fails is silent in that output.

This is tagged "BC break". In which specific Drupal release did this break?

I can't reproduce the bug. By setting a limit of 3 and trying to upload four, there is a validation error: "Field field_image can only hold 3 values but there were 4 uploaded."

Update the steps to reproduce.

This could be 🐛 Stale field settings used by options_allowed_values prevents widgets from updating the allowed values. Needs work .

We need the output of composer patches-repatch -vvv. It is very unlikely something to do with Drupal but the debug log will help you.

Let’s get all debug information for some support.

I don’t see how Core could solve this for the contributed module.

Are query strings effective in all cases? As I write this, 33 thousand Drupal sites use the Purge module → for managing CDN caches.

I did some testing and everything is working on a site that I have with many patches. Follow the composer-patches troubleshooting guide as some things have changed.

Probably Drupal itself is not involved in your difficulties.

Actually, the configuration should be the same between versions. Let’s please see the verbose Composer output

What are the reasons to implement these changes as a sub module?

Do you have some Composer debug logging? Did you configure the patch tool → as documented?

May we see the composer.json file?

That’s understood. But the debugging steps are in the “steps to reproduce section” above, which confused me, because they aren’t the steps to reproduce the bug.

Can we close this as unneeded because production site shouldn’t be installed this way?

What is the evidence that it is incompatible? That information is missing from the issue summary.

So the steps to reproduce in the issue summary are debugging actions.

What are the bug reproduction steps?

🐛 Settings tabs get lost Active

Do these issues share a common cause?

Why is route_name null there?

What do the steps to reproduce mean?

Let's make this easier to find.

I read the issue summary but unfortunately I don’t understand exactly what it is saying about the bug. There is code to be added but I don’t know why.

The issue title and summary need updating with information from comment 5 or this will languish.

Actually I think it’s likely the patch itself breaks something in Drupal, which will make this a duplicate of ✨ Refactor ImageStyleDownloadController so derivatives can be generated by contrib modules Needs work .

With any command failure it’s important to know the command you typed. Add that to the summary.

What is the PHP version and the Composer version?

I am making this a support request pending bug reproduction.

It’s possible the patch itself is to blame but let’s get more information.

A site can use separate text formats, which only loads the library if an applicable text filter is active.

There are too many suggestions in this issue to be done at one time, and some ideas duplicate those in existing issues.

These errors are in the web server’s logs.