The patch fixes incorrect Shared Layout modifications behavior from the Experience Editor.
-
Updated
Oct 4, 2016
The patch fixes incorrect Shared Layout modifications behavior from the Experience Editor.
Items might not be loaded in the 'Multilist with Search' field, when using the 'Field Editor' dialog that is called from either 'Experience Editor' or 'User Manager'.
Allows to save the 'Multi-Line Text' field without losing line breaks after editing it using 'Field Editor' in 'Experience Editor'.
Experience Editor not triggering workflow state while Content editor does
Fixes the issue with XFrameOptionsHeaderModule during content personalization in Experience Editor
Experience Editor breaks the Layout Delta when template inheritance is used
The "chorme" parameter may be null on adding a new component in the Experience Editor
Fixes an issue where Save button might've been disabled, but still clickable in Experience Editor.
Enforce Version Presence breaks languages switching in the Experience Editor
Prevents too many redirects when access an item with MVC layout using Experience Editor after session expiration
When clicking the 'Lock and Edit' button, a new version is not selected if date was changed.
Remove the '<p>' tags wrapping for single line of text in the 'Rich Text' field when using inline editing in the 'Experience Editor'.
Consider the context language of an item when using the search command in Experience Editor
MVC personalization conditions cannot be seen after performing rendering changes in the Experience Editor
Link field value with special characters cannot be saved correctly in Experience Editor.
Unable to change the test variants in Experience Editor if test is created in non-English language
Experience Editor validates a field in the wrong language version
A proof of concept that combines React and Sitecore
“Denied” Language Write does not prevent inserting pages in Experience Editor
Wrong goal name is displayed when inserting a form through Experience Editor.
Add a description, image, and links to the experience-editor topic page so that developers can more easily learn about it.
To associate your repository with the experience-editor topic, visit your repo's landing page and select "manage topics."