The inline block editing functionality has been moved from the Episerver Block Enhancements Labs add-on to CMS UI.
This feature allows editors to edit block content in a "quick edit view" without changing the current content context. See Linh Nguyen's blog post and the developer guide topic Inline edit blocks for more information.
Note: If you have a previous version of EPiServer.Labs.BlockEnhancements installed, you should upgrade to version 0.10.0 as that is compatible with CMS UI 11.32.0.
New releases of Episerver CMS UI (inline block editing), Episerver Content Delivery API (constraint on Microsoft.AspNet.WebApi.WebHost has been bumped, Options method decorated adding full support for CORS), the Episerver Block Enhancements Labs add-on (inline block editing moved to CMS UI), and the Marketing Automation connector for Watson Marketing/Silverpop (API endpoint URLs updated). Bug fixes for Episerver CMS Core and Episerver Forms.
CSV reports from the Personalization Portal are localized (number formatting and CSV separator) according to your language setting. For example, English CSV files will have a comma (,) separator and a period (.) decimal point (such as Sep 2021, 11.49); German CSV files will have a semicolon ( separator and a comma (,) decimal separator (such as Sep 2021; 11,49). This makes it easier to import CSV files into localized versions of Excel.
The Shortcut field has not default value "No shortcut" if deleting a page after setting shortcut type to "Fetch content from another content item"
Steps to reproduce:
Page 1 is a product page with a published version. Page 2 is a product page and has content in the main body property. It is also published.
Page 1 has the shortcut type "Fetch content from another item" set and links to page 2.
Go to edit view and delete page 2.
Empty the trash.
Select page 1 in the page tree, go to All properties view and select the Settings tab.
The Shortcut field has value "No shortcut".
The Shortcut field has value: "Fetch content from another item".
On an Alloy sample site, access admin view and enable "English" - "en" and "English (United States)" - "en-US".
Set up multiple sites. The main site (site A) has 'en' master language and the secondary site (site B) has 'en-US' master language. Site B just contains a start page.
Under Manage Websites of admin view, select Use site-specific assets for both sites.
Configure site A with Culture = en, Type = Primary, Scheme = HTTP.
Configure site B with Culture = en-US, Type = Primary, Scheme = HTTP.
Remember to remove the wildcard host name.
Go back to edit view and select site A. In the assets pane, select Media and create a folder named image under For This Site.
Upload an image to the image folder.
Select a page that has version in "en" only, for example, Alloy Meet. Add the uploaded image to the Teaser image property of this page. Then publish the page.
Export the Alloy Meet page from site A by going to admin view > Tools and select Export Data. Leave the default options selected and click Export content items to export the page.
Import the Alloy Meet page to site B by going to admin view > Tools and select Import Data. Select the Update existing content items with matching ID check box, and select English (United States) in this step. Upload the export file.
Please note that the page exported does not have a en-us language version! However, some content has been imported.
Still in site B, check the Media assets pane. The image in the image folder has been imported.
It looks like it is related to Response.Flush called. When commenting out this line, it starts to work.
Similarly, when adding a Response.Flush() call after the synchronous transmit-method that will also start failing. Otherwise, when it copies with stream.CopyTo(), it will read/write to the stream without a flush and that works as expected.
According to Google, alternative links need to be outputted in an absolute URL format. This does not seem to be the case with the built-in alternate links extension in Episerver, resulting in incorrect behavior with Google complaining.
Inline block editing features have been moved from the Episerver Block Enhancements Labs add-on to CMS UI.
This feature allows editors to edit block content in a "quick edit view" without changing the current content context. A dialog box with an editable form is opened by selecting Quick Edit from the block's content menu.
In the inline edit dialog box, editors can also publish the block, mark the block as Ready to Publish, or send the block to review depending on the context and user's access rights.