- Issue created by @justcaldwell
- First commit to issue fork.
- Status changed to Needs review
6 months ago 12:17pm 13 May 2024 - π΅π±Poland dolszewski
Hi @justcaldwell
I have posted MR with the fix, feel free to test it. We will also test it internally.
Recently, in 10.3-dev some changes were made in the ckeditor5 core module that caused this fatal error. - Status changed to Needs work
6 months ago 2:30pm 13 May 2024 - πΊπΈUnited States justcaldwell Austin, Texas
Thanks @dolszewski, but the change had no effect. The patch applied successfully. I then rebuilt cache, (re) enabled ckeditor5_plugin_pack_templates, ckeditor5_premium_features, ckeditor5_premium_features_productivity_pack and ckeditor5_premium_features_mentions. Finally, I created a very simple template and made it available to the basic_html format.
Same error occurs if I visit the basic_html format config page.
- Status changed to Needs review
6 months ago 3:03pm 13 May 2024 - π΅π±Poland dolszewski
@justcaldwell
Ah sorry, I missed that you have installed a premium feautres productivity pack. You cannot have both installed at the same time in that case. When you install a premium features productivity pack, it overrides the "plugin pack template" plugin config and you need to have a license key for the productivity pack.
You have that fatal error because my patch only works for the plugin pack (the same error occurs in premium features). Of course, we will also add patches for premium features before Drupal 10.3 is released.
Please check it without the premium features productivity pack installed. - Status changed to RTBC
6 months ago 5:14pm 13 May 2024 - πΊπΈUnited States justcaldwell Austin, Texas
Ah, okay -- I was under the mistaken impression that I needed to have those premium modules enabled.
I tested without them install and the patch works just fine. Thanks for the quick response!
-
dolszewski β
committed 5b3dfdf3 on 1.0.x
70 - fix templates fatal error [#3446546]
-
dolszewski β
committed 5b3dfdf3 on 1.0.x
- Status changed to Fixed
5 months ago 6:51am 14 June 2024 - π΅π±Poland dolszewski
The latest release (1.1.0) contains a fix for that bug.
Automatically closed - issue fixed for 2 weeks with no activity.