🇨🇴Colombia @yovanny.gomez.oyola

Hi @bburg,

We are encountering the same issue, but it only appears in Mozilla Firefox; there are no warnings in Google Chrome.

How can we resolve this? Is it necessary to apply a patch to the module, or can this be adjusted from the Drupal backend?

Thank you, and I look forward to your feedback.

Hi, you can try

composer require drupal/core-recommended:10.3.0 drupal/core-composer-scaffold:10.3.0 drupal/core-project-message:10.3.0 drupal/core:10.3.0 --update-with-all-dependencies

Added patch to fix this error. Working fine with Drupal core 10.3.1 and lightning_workflow 4

yovanny.gomez.oyola → created an issue.

I am attaching initial patch with Drupal 10 compatibility solutions.

yovanny.gomez.oyola → created an issue.

I'm agree whit @sime. Path number 12 does not work for me with PHP 8.1.

I add the patch with the adjustment.

I think so, it's duplicated. You need to add the next patches:

"drupal/ckeditor5_font": {
"3368736": " https://www.drupal.org/files/issues/2024-01-25/ckeditor5_font-schema-fix... → ",
"3350333": " https://www.drupal.org/files/issues/2023-04-21/3350333-5.patch → "
}

Yes, I have activated the filter, but when adding custom colors the filter does not perform any functionality, because the conditional is fixed with hsl. You can do the test, add some custom color in the plugin configuration, activate the "Convert color styles to class" filter and save. Go to some content, add a color and save.

You will see that the filter is not working correctly.

Hi @artemboiko,

Your fix is not working in my case.

1. when generating custom colors from the plugin administration, the plugin conditional does not work because it is only validating hsl and the custom colors are added with #.
2. With hsl colors, the plugin's conditional works, and the classes are changed. But when I return to the WYSIWYGs edition, the class disappears and only text remains.

Can you validate if I am correct?

Thanks!

Hi @kalalshehri, thanks for the clarification.

I have tried installing and uninstalling the indicated version and also version 2.5.3. But I have not been able to replicate the error.

Did your uninstallation process suddenly generate an error? Like some timeout or did you uninstall with drush?

Please try running the following with drush:
1. drush cr
2. drush en dxpr_builder -y
3. drush cr
4. drush pmu dxpr_builder -y
5. drush cr
6. Add new content.

If you have any error in any of them. Please add the screenshot

Regards,

I have not been able to replicate the error with the version 2.5.0, nor with version 2.5.3

Please enter the necessary steps to reproduce the error.

At the moment I think the best thing to do is the following:
1. Delete the /modules/contrib/dxpr_builder folder
2. Run composer require 'drupal/dxpr_builder:^2.5'
3. clear the cache.
4. Try to add content again.

Regards,

The next patch fixes the warning

yovanny.gomez.oyola → created an issue.

Patch #3 works as expected.

Drupal core version: 10.1.2
conditional_fields version: 4.0.0-alpha3

Hi

This warning was already solved in the ticket https://www.drupal.org/project/pathauto/issues/3328670 📌 PHP 8.2 compatibility Fixed

Thanks!

The following patch fixes the problem.

yovanny.gomez.oyola → created an issue.

The following patch fixes the warning.

yovanny.gomez.oyola → created an issue.

Hi,

Thanks for the patch. It works as expected for ldap: 4.4.0

Hi,

I tested the patch #2 and it work as expected.

Hi @piotrsmykaj,

we already have another patch por Drupal 10 compatibility and it worked as expected. https://www.drupal.org/project/views_arg_order_sort/issues/3299435 📌 Automated Drupal 10 compatibility fixes Fixed

I think we can closed this ticket.

Hi,

I implemented the patch#3 and it works as expected.

Drupal core version: 10.1.2

Hi,

This is a topic that is not very clear when changing to the module version 4.0.0-rc1. I have downloaded the mentioned version and the WIDGET_FORM_ALTER constant is no longer found, so an error is generated in Drupal.

It's a little hard to know which constant to use now. I think there is a lack of documentation about it.

It is not clear whether to use WIDGET_SINGLE_ELEMENT_FORM_ALTER or WIDGET_COMPLETE_FORM_ALTER

Regards,

Hi,

I have made a necessary adjustment in the patch for version 2.1.0-rc6 in D10

Hello everyone,

I have validated and the patch #16 works well with Drupal: 10.1.0-dev and PHP: 8.1.19

Regards,

#172 applies and works in 9.5.5. Thanks!

Hi @cilefen,

In the ticket you mention, only the error message is being changed when the !$image->isValid() function fails. But in this case what we want to validate is that the user cannot upload empty files to the CMS. I think they are 2 different things.

Hi @asmasiddiquiCG thanks for the patch.

I have validated it and it works fine on:
Drupal core version: 10.0.4
PHP version: 8.1.14
Mysql version: 8.0.31

The result is as expected. But I see that the test keeps failing. Can you validate it?