Closed (fixed)
Project:
USWDS Ckeditor Integration
Version:
3.2.x-dev
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
13 Nov 2024 at 20:49 UTC
Updated:
9 Jul 2025 at 22:19 UTC
Jump to comment: Most recent, Most recent file

Comments
Comment #2
amplifier commentedI am experiencing this too.
Comment #3
smustgrave commentedthis actually needs some major refactoring
Comment #4
smustgrave commentedSo no secret and we got permission to do so but this was forked from ckeditor_bs_grid and bootstrap has container options.
So here we need to to turn that default option to a checkbox to add the container.
Move the container class to that Div vs uswds_grid which isn’t a real uswds class
Comment #6
smustgrave commentedTry this
Comment #8
smustgrave commentedGoing to go on a limb
Comment #9
smustgrave commentedPut a warning in the description this was a re write
Comment #10
srdtwc commentedThere seem to be a few issues with this upgrade
1) There are a number of errors present. These appear even after a "drush cr".
2) After creating a page with a grid the wrapper classes are saved successfully, but when I go to edit the grid again a large black triangle appears in CKEditor. I can confirm this did not happen in 3.1.2.
3) Embedded Content appears broken. Any page with an existing Accordion returns an error like this:
Additionally, when clicking the "Embedded Content" button when creating a new node, there is a 500 error in the console.
Comment #11
smustgrave commentedI don't understand how #1 and #3 are related to this issue
Comment #12
srdtwc commentedTested again, 1 and 3 were the result of upgrading with
--with-dependencies, which upgraded doctrine/deprecations and caused those errors.2 is still present when upgrading without
--with-dependencies.But I can confirm the intended functionality of being able to save the wrapper classes seems to be working.
Comment #13
smustgrave commentedSo I don't forget to take a look
Comment #14
smustgrave commentedThis whole plugin needs to be redone, probably going to start a new branch
Comment #15
smustgrave commentedComment #18
smustgrave commented