@YuvalBH - That error is from the settings_tray core module. There is a patch in this issue queue that fixes it: https://www.drupal.org/project/drupal/issues/3458067 🐛 Contextual links disappear intermittently leading to console errors Active
I implemented the patch in #8 and that works for me.
I can confirm that it's something with the update to the tb_megamenu, in alpha4.
I am getting the same problem with a site that has this module installed, not using bootstrap but gesso theme, and no webforms. It even happens when someone isn't logged in, and they are just viewing a basic page full of content (no video, no images, just text). All the user needs to do is click around / highlight text for roughly 60 - 90 seconds, and the entire page becomes unresponsive, causing the browser to crash.
Hello.
I've created a PR that resolves this issue. Please see above. I've tested this on sites built on 10.3 and with this module enabled, and this resolves the configuration validation issue.
Hello.
I've created a PR that resolves this issue. Please see above. I've tested this on sites built on 10.3 and with this module enabled, and this resolves the configuration validation issue.
CozyDrupalNerd → created an issue.
CozyDrupalNerd → created an issue.
I've tested trying to save the editor setup, but when I do I get this error:
Error message
'config' is not a supported key.
'spec' is not a supported key.
'help' is not a supported key.
'helplong' is not a supported key.This is after I've uninstalled CK Editor 5, cleared cache, and re-installed it, as well as removed all possible contrib modules that could tie into the module (Linkit, etc). This error is coming from a vanilla CK Editor instance, clear of any existing configuration (IE - no existing configuration).
Because of this, this makes trying to create a new site / project using D10.3 unable to be accomplished successfully.
For those who are looking to do a temporary "fix" by bypassing the code in the updated BigPipe.php file (as mentioned in #17 and #31), I've created a patch that comments out that piece of code. Testing this, Big Pipe still works and the theme hook for status-messages comes back, and this should only be used as a temp. fix / workaround until it can be fixed correctly.
This patch will help you upgrade to 10.3.
I tried what you suggested, and I am not getting any suggestions. I even went to manually update the Olivero twig template (just adding text of 'Hello World'), clearing caches, and still nothing.
This was done with a new minimal install, no custom modules.
I noticed this too. I'm not sure how expanding the core theme suggestions for block view modes would remove the hook entirely for theme suggestions for the status_messages.
I've created a merge request that would resolve this.
For those that need to patch before the merge request can go through, please use the following patch attached.
CozyDrupalNerd → made their first commit to this issue’s fork.
ACoolDevDude → created an issue.
Hello!
I wanted to help contribute a patch that I was able to write. It's for the 2.x branch of the module (this is the version our customer is moving onto from 1.x) but I based the start of it all from the patch on #80.
This patch is able to get the UI functionality for letting the administrative user be able to have the Translate links in the Operations dropdown for both the Group menu and Group menu links, and help avoid the WSOD errors that I was seeing when initially trying to re-roll the patch from #80 onto the base of the 2.x branch.
The only thing that needs work on, is that in the GroupContentMenuForm.php, I had to remove the $link->isTranslatable() check because when enabling the Group Content Menu's as translatable content, it's enabling it for the entity of group_content_menu but not for the links (and I was not seeing any way to be able to see how to make it enabled). I'm hoping someone might be able to expand on my work here and be able to include this.