🇺🇸United States @bajah1701

bajah1701 → created an issue.

@trickfun I took the patch from the merge request in gitlab.

https://git.drupalcode.org/issue/drupal-3478628/-/commit/53479799d82fb27...

I can confirm that the patch worked and no new error was introduced. The only error that appears in relation to themes is

[error]   (Currently using Removed core themes You must add the following contributed themes and reload this page.
 * Stable [1]
 * Classy [2]

But this was there before the issue appeared in 10.3.6, so not sure how relevant it is.

Nonetheless the patched works.

I too ran into this same issue and taking the time to deal with missing modules solved the issue. thanks for the step in the right direction.

This is still an issue and is serious enough to warrant more attention. Was expecting this to be included in the latest update as in 3.0.4, but its not. Please add.

bajah1701 → created an issue.

bajah1701 → created an issue.

bajah1701 → created an issue.

+1 @kbrodej I modified mine using the is_null() function but yours is simpler.

bajah1701 → created an issue.

Patch #9 works however i noticed that the error message is displayed twice. No sure why that is the case, couldn't identify anything in the patch that would allow for that to happen. Also, drupal fields uses JS to display the error message on a required field in context, such that the form is not submit to the server, this functionality doesn't seem to be present with fivestar fields.

The patch introduced a new error on line 151 of the BackToTopSettingsForm.php file.

Parse error: syntax error, unexpected token "->" in
/var/www/html/modules/contrib/back_to_top/src/Form/BackToTopSettingsForm.php on line 151

The error is really on line 150 because a semi-colon was added. Removing the semi-colon should solve the issue.

The module page does not say so but ensure that the library is in the libraries folder via the path /libraries/dompurify/
You can download the library from github https://github.com/cure53/DOMPurify
change the name of the folder to "dompurify"

Apparently on production sites, the cache needed to be refreshed after updating the settings.

bajah1701 → created an issue.

It appears that it is required to select a default value for it to appear

bajah1701 → created an issue.

bajah1701 → created an issue.

@dineshkumarbollu I'm on Drupal 10.2.3 with php 8.2.
@abhishek_gupta1 I will test it on Monday when I return to work.

bajah1701 → created an issue.

I was able to successfully uninstall the module after applying the patch.

In response to the question, Yes! Real Time Collaboration was enabled but not yet configured. Unfortunately we couldn't find any errors with that message in watchdog.

Hi @salmonek,

1. Yes the error did appear on my first attempt to uninstall the module. The error also shows up when navigating to the edit page of a page that uses the template feature (I only tested this). Hence, there is no way to edit that page. I also experience that error on the page that allows you to add the different ckeditor features, it occurred upon saving that page. However, it only happen on my first attempt, once I narrowed down the number of features the error went away.

2. I tested it on Drupal Core 10.1.2

3. I tried to uninstall via both methods and got the same error.

Because we can't go back to the edit page of the node, to test more templates this is a bit of a setback, so a quick workaround would be appreciated.

bajah1701 → created an issue.

Turns out layout builder was not the main cause. There was another error message just before the layout builder error which referenced the aggregator module that was deprecated in drupal 10. Once I added the aggregator module as a contrib module the database updates proceeded without any issues.

@VladirmirAus

I don't have an error log but going through the steps you provided solve the issue. Thank you

I'm getting this error when running drush updb on a fresh instance of Drupal 10.1.2. I'm using drush 12.1. As mentioned before unhiding stable9 should not be the correct way to fix this issue.

My understanding is based on this response https://www.drupal.org/project/drupal/issues/3331347#comment-15009425 💬 After saving a node the CKEditor model of an element changes Closed: works as designed
It's the last part of the comment. However, after trying a few things out I realized that it only works with manual decorators and these must be defined in the configuration which displays them by default in the LinkUI. The workaround was to hide it from the LinkUI using CSS but I don't know if this is the right way to go about this.

@idiaz.roncero I understand that you can pass the values from your own button UI to the Link UI. I'm thinking that the button UI can have the fields for selecting the options and then base on what is selected the decorators that match the options are passed to the Link UI.

It doesn't work in Drush 10 either.

@idiaz.roncero I have tested it with the Linkit plugin and it works without any issues. I added 2 manual decorators, one for converting the link to a bootstrap button and another for making the button full-width.

A workaround is to make use of the LinkAPI. See the explanation in the link below.
https://www.drupal.org/project/drupal/issues/3331347#comment-15009425 💬 After saving a node the CKEditor model of an element changes Closed: works as designed

@mgsy Thank you, thank you, thank you. I was not aware that this was possible. Greatly appreciated.

Thank you @idiaz.roncero, I will be looking forward to what you come up with.

Well my hands are tied here. How to reproduce it would eventually require writing lots of boilerplate code anyway. I really don't know how else I can explain the problem other than what I have already written.

I started working on this inhouse focusing only on the necessary features but ran into a conflict with the Link Plugin taking precedence on the tag. See the issue I raised here https://www.drupal.org/project/drupal/issues/3331347, maybe my code can be used as a starting point if nothing has already been written.

If this might help someone. I got this exact error message but this patch didn't work. I took @cilefen recommendation of the duplicate issue and decided to try its patch instead and voila, it works.

So while the error message may be different, the solution is the same.

I'm experiencing this issue in Drupal 9.5.2 and the patch fails because there appears to be differences in the codebase at this line.
What is the recommendation for raising this same issue but for a different version of Drupal?