<h-sweet>WF Bug wassup<h-sweet>
Hey! Joe here. First, this bug does not break Sweet Text. You can use everything as instructed and there will be no negative impact on your published site.
When you restore your site from a backup, Designer sees the <angle-brackets> and tries to close them at the end of the rich text block. For example, if we use Sweet Text like this, "Have you used <sweet2>Sweet Text<sweet2>?" - Designer will update that text to "Have you used <sweet2>Sweet Text<sweet2></sweet2></sweet2>?"
Webflow confirmed this is a bug on their end. There is no note on when this may be fixed. Again - this does not influence Sweet Text usage. The closed brackets do nothing and do not show up on the published site.
This issue only happens with static rich text using Sweet Text. CMS field rich text and CMS connected rich text are unaffected.
If this does not work well for your setup, we have a different script for you to use. This script below uses [brackets] instead of <angle-brackets>. This script uses Sweet Text like this: "Have you used [sweet2]Sweet Text[sweet2]?"
What the heck is Sweet Text?
Sweet Text in CMS
Establishing classes in Designer to use with Sweet Text
Create alternate style options for Rich Text using Sweet Text
Technical review of Sweet Text with Chrome inspector
Adding classes to parent elements inside rich text, like p, li, ul, h2, etc.
Create draggable text elements inside a rich text element
Create a sortable list of elements inside a rich text element
Trigger custom popup interaction via CMS rich text field, Sweet Text, and Webflow Interactions
A 'not bad' Webflow bug we found when using Sweet Text. We have a temporary update if this bug affects you.