You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
In some cases including Florentine and Hydra, the Customize -> Widget -> Call-to-Action visual editor includes the body class page-template-default which is set to display:none the call-to-action class, causing a blank visual editor.
This issue appears to be intermittent, I could replicate it but other testers could not. This might be related to the notice that accompanies affected sites, ERROR: Duplicate widget ID detected. To avoid content loss, please create a new widget with the same content and then delete this one. since it appeared to me but not other testers.
To Reproduce
Steps to reproduce the behavior:
Go to Customize -> Widgets
Edit the call-to-action widget with the visual editor
Inspect the body classes in the editor to see if page-template-default appears
Expected behavior
The visual editor should display all content in the CTA widget.
Screenshots
Desktop (please complete the following information):
Describe the bug
In some cases including Florentine and Hydra, the Customize -> Widget -> Call-to-Action visual editor includes the body class page-template-default which is set to display:none the call-to-action class, causing a blank visual editor.
This issue appears to be intermittent, I could replicate it but other testers could not. This might be related to the notice that accompanies affected sites,
ERROR: Duplicate widget ID detected. To avoid content loss, please create a new widget with the same content and then delete this one.
since it appeared to me but not other testers.To Reproduce
Steps to reproduce the behavior:
Expected behavior
The visual editor should display all content in the CTA widget.
Screenshots
Desktop (please complete the following information):
Additional context
This issue was reported in the BoldGrid Support Forum
The text was updated successfully, but these errors were encountered: