Error logs on a few of my sites were getting filled with warnings and I could not find culprit in backtrace. Applying this patch to core (#23) has resulted in clean logs, finally!
Error logs on a few of my sites were getting filled with warnings and I could not find culprit in backtrace. Applying this patch to core (#23) has resulted in clean logs, finally!
Applying this patch on a site that utilizes PHP 8.3 fixes the PHP error related to guess changing but results in the following error in watchdog:
No php-http message factories found. Note that the php-http message factories are deprecated in favor of the PSR-17 message factories. To use the legacy Guzzle, Diactoros or Slim Framework factories of php-http, install php-http/message and php-http/message-factory and the chosen message implementation.
Confirming same problem Drupal 10.2.6 using the formatted field in the display for a content type. Applying patch via composer works and fixes issues.
Bump, patch works can we get this in a main release?
Confirming patch #5 addresses 8.3 deprecation notices I was experiencing when testing.
I have also reviewed the pending merge request changes on a D10.1.6 site of mine that depends on bfd and confirmed the upgrade to D10 is successful and no errors/regressions are present.
Thanks. 2.3.1 release fixed the console error related to library and all is good now. Never had issues with library being found in status report so I can't speak to that being resolved or not.
Same symptoms here as #7. Status report is clean but the "keyword var" error pops up in js console. Forcing downgrade to 1.6 or adding semicolon fixes.
In my opinion, the issue is different because #2980299 is related to the UX components and the destructive action as you perform it. In this case, I cannot find a way to expose UX elements for the element within question (menu_link_content.layout_builder__layout) to work with it and purge data.
The simplest explanation would be that I'm simply overlooking where this could be but I have dug and dug without any success, which is why I came here and referenced the other issue because it is "kind of close but not quite" to this particular issue.
I keep asking myself: "If there was a page to manage menu displays, where would it be?" -- I have never seen such a thing. But maybe layout builder had one at one time way back when?