Resolve Issues with Header and Footer Embeds

If users added plain text that included special characters to the header embed, a toastr error (syntax err) would be thrown on the buyer page. And if users added any non script tags in the footer, it would break the page -- not show the page content and not allow users to click on any links on the app.

To resolve this, plain text AND plain text with special characters/symbols are no longer supported in the footer or header. Also, <script> tags are the only tags supported in the footer embeds.

If there's an existing issue with the header or footer embeds, they won't be appended to the head/body on the buyer page. Instead, the errors will be logged in the console. With that being said, the page should load with the correct content, not see the syntax toastr error, and function properly (e.g users are able to click on other links on the app if the footer has non script tags)

Additional changes to help users understand what is supported in the embeds:

• Added tooltips next to the header and footer embeds with text describing what is supported in each embed
• Added a REMINDER text in the Embeds tab to remind users that the header and footer embeds are used for any tags needed for third party integrations

Fixed Pasting Bug

2.0.1

:bookmark: 2.0.1

Breaking Changes v2.0.0

Replace HeadstartSDK with CMS sdk

The headstart middleware no longer has these cms endpoints. In SEB we were unable to simply set a different baseurl like Winmark did because it would also change the baseurl for our other middleware endpoints which we don't want.

This change requires implementors to:

install @ordercloud/cms-sdk version 1.0.1
Set token, baseApiUrl and baseAuthUrl in CmsConfiguration from @ordercloud/cms-sdk

fix video full width even on desktop

1.0.4

:bookmark: 1.0.4

fix video preview cutting off

1.0.3

:bookmark: 1.0.3

Fix dynamic text replacements overwriting removal of contenteditable attribute

If dynamicTextReplacement data was provided, content was being set to the result of page.Content with the text replacements, but was losing the result of the stripEditableAttributes method. Pass updated content to method to replace text with given dynamicTextReplacement data.

Fix: Images still not responsive

1.0.1

:bookmark: 1.0.1

First non-beta version (fixes image responsive issue)

Images in page preview weren't responsive

Prevent toggling "Show in Navigation" for slugs in requiredSlugs

It was decided that slugs provided in requiredSlugs should not be allowed to be toggled for "Show In Navigation", because it provides a loop-hole to hide that navigation title.

Optional input for downloadable file types

1.0.0-beta.51

:bookmark: 1.0.0-beta.51