Closed mariosm1 closed 2 years ago
I'm able to reproduce the problem reliably with this template on 8.0.3 / 121. It looks like it happens when you try to drag an asset to a set of stacked widgets (for example in this screenshot) - all text widgets on that page are broken after that. Same issue does not happen in 8.1. z-home-2022-template.txt
@matomario8 Was unable to reproduce this on 8.1.1. We back ported a change to 8.0.3 release, https://github.com/percussion/percussioncms/pull/574/commits/a02b315ecd3f719f43b7f96e7046677223eeef1e, that should fix this in 8.0.3. Once the updated release kit finishes you should be able to verify.
Closing this out as it looks resolved by 8.0.3 build 123
Describe the bug If a template has been imported from another instance, it is possible for the rich text widget slots to not work. You can edit the slot but trying to save the changes will throw an error. The same thing happens when dragging a rich text shared asset onto the widget slot.
Workarounds Removing and adding back the widget slot in the layout properties for a template seems to fix the problem
To Reproduce Steps to reproduce the behavior:
Go to the Design section of the CMS
Click Actions > Import template
Import the attached template z-home-2022-template.txt
In the Finder, click an asset folder. Then click the create new asset button at the top right corner of the cms
Select Rich Text Asset
Add any text to the asset along with a title and click Save
Go back to the Design section of the cms. Edit the template that you imported
Click the Content tab on the template
While keeping the template editor open, navigate to the rich text asset you created in the Finder
Drag and drop the rich text asset onto this specific part of the template, where the widgets are stacked up. May need to have the 🚫 appear before dropping the widget.
Expected behavior There should be no errors on dragging assets to a template slot, if that template has been imported
Screenshots Error on dragging asset to template
A 500 error is returned after making this call, but there is nothing in the error log on the server