Problem/Motivation

When I first activate the module, I get 4 warnings.
I don't see these warnings again after that. You can see below.

Any idea,please? Thanks

d10.site/admin/config/content/diff/general

Warning: Trying to access array offset on null in Drupal\diff\Form\GeneralSettingsForm->buildForm() (line 84 of /var/www/html/d10site/web/modules/contrib/diff/src/Form/GeneralSettingsForm.php)

Warning: Undefined array key "raw_html" in Drupal\diff\Form\GeneralSettingsForm->buildForm() (line 80 of /var/www/html/d10site/web/modules/contrib/diff/src/Form/GeneralSettingsForm.php)

Warning: Trying to access array offset on null in Drupal\diff\Form\GeneralSettingsForm->buildForm() (line 84 of /var/www/html/d10site/web/modules/contrib/diff/src/Form/GeneralSettingsForm.php)

Warning: Undefined array key "visual_inline_html5" in Drupal\diff\Form\GeneralSettingsForm->buildForm() (line 80 of /var/www/html/d10site/web/modules/contrib/diff/src/Form/GeneralSettingsForm.php)

Diff Pluss:1.1.0
Diff : 2.0.0-beta3
Drupal:10.3.6

Comments

pearls created an issue. See original summary.

dineshkumarbollu’s picture

dineshkumarbollu commented

Hi pearls,
Can you provide php version also for reproducing the issue.

pearls’s picture

pearls commented

Hi dineshkumarbollu ,
It's 8.3.
But, I don't remember the exact version when I created the issue. It may be 8.3.9 .

luke.leber’s picture

luke.leber
Primary language English
Location Pennsylvania
commented

I can reproduce this! I've opened an upstream issue with diff to see what the best way to resolve this is.

Thanks for reporting!

luke.leber’s picture

luke.leber
Primary language English
Location Pennsylvania
commented
Status: Active » Fixed

Great news! #3515557: Harden general settings form against newly added layout plugins landed upstream, fixing this for all implementations starting with the next release of the diff module.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.