This happens when a content type has both a MediaLibraryPickerField and the LayoutPart attached.
The layout editor renders the field, whose shape template accesses the MediaParts property, which is not initialized for new content items.
Fixes#5489
This fixes the issue when you try and use address formats such as "User <user@domain.com>" and adds support for sending HTML as part of the message body.
Fixes#5298
This fixes two issues:
1. Adding a Form element (and selecting the content type to create using the submitted values) and then adding a form element would not cause the Bindings tab to appear.
2. Adding nested containers (such as Grid, Row and Column) to a Form element would prevent the Bindings tab from appearing when adding a form field element such as TextField to a nested container.
Work Item: #5445
This fixes the issue where the default layout data string would not be applied when creating new content items of a content type with the LayoutPart attached.
For example, creating new Form content items would start out with an empty canvas instead of with a default Form element and a submit button.
The issue was that when you save a content item (without publishing it) while checking the "Set as homepage" checkbox, it would lose its checked status after save.
With this change, the checkbox is again rendered but in a checked status, so that when you do publish, it will become the homepage.
Fixes#5467
This prevents a SO exception when you for example have a Projection element that renders content including the content item rendering that Projection element.
This change instantiates an actual HttpContext object during background sweeps so that Razor templates using Html Helpers (that require HttpContext.Current to be not-null) won't fai lwhen being rendered.
This will ensure that an actual HttpContext object will be available in case of background task operations thanks to the way HttpContextBase is registered (providing a placeholder object in case of background operations).
When using a SELECT input control, that control itself would be initialized with the call to "toggleWhatYouControl" instead of its child OPTION elements.
This fixes an issue where, even though the posted values would not be saved, the user is not presented the form with validation errors, being redirected to the configured url instead.
- Implemented HTML filters for Html, Text and Paragraph elements
- Tokens are only processed on the front-end, not in the editor page itself. This also prevents an exception when the {Shape.Execute} token is used with a theme specific shape.
Work Item: 21304
This fixes an issue where "complex" form field names aren't properly mapped to key value pairs, such as "Parts%5B0%5D.Bindings%5B0%5D.Name" instead of "Parts[0].Bindings[0].Name"
The issue is that the media item element renders the selected media items with the Thumbnail display type.
The Media shape templates for that display type do not include necessary styling themselves; instead the media library picker UI includes the necessary stylesheet.
This enables custom elements that render an image to be responsive within the layout editor by applying the "img-responsive" class to either the image itself or any of its parent HTML elements.
The issue was that the snippets harvester included the Elements_Snippet shape which itself is not a snippet.
This also fixes an issue where it would not find snippets defined in the current theme.
This changeset also renames the service to IClientAddressAccessor and refactors the settings into being configurable from HostComponents instead of through a site settings part.
Work Item: 21237
The reason for doing this is that the Container module itself queries for available _ListViewProviders_, which could potentially yield zero providers if the *Lists* module is not enabled.
The issue was that during page initialization, the Content element's HTML would be serialized with the URL encoded version of its contents, but shortly after that HTML would be URL decoded, causing a difference in the serialized JSON between the initial serialization and final serialization (upon page unload).
The issue was that by combining existing element data with posted element data, the existing items would retain their values in case no such item was posted, which is the case for unchecked checkboxes; their name/value pair will be not posted, so the original value would be retained.
This is fixed by no longer combining existing data with hosted data, but instead relying that an element editor will post all data that it is concerned with.
Sipke Schoorstra