Release notes for Optimizely CMS and Customized Commerce updates

Fixed an issue where the blocks that used the JsonIgnore attribute caused the UI to display an infinite loader due to an error on handling the ignored property while editing the block.

Fixed an issue that caused an error when application instances were started simultaneously and one of the application instances detected a ContentType or Property was updated by another application. The error prevented the ContentModel change from being applied.

Fixed an issue that cleared errors on ViewContext.ModelState when you rendered a partial content (such as  through a content area). For example:

1. Add following line to DefaultPageController.Index method.
   ModelState.AddModelError("AnError", "some error");
2. Put breakpoints in a view that renders a contentarea before and after the contentarea (such as StandardPage/index.cshmtl)
3. Access a page that contained an area item that is rendered with a view such as  https://localhost:5000/en/about-us/
4. In the breakpoint before the rendering of the contentarea, look at ViewContext.ModelState. The error was present in the breakpoint before rendering the content area but Errors was cleared after the rendering of the contentarea.

Fixed an issue that prevented a validation error (The number must be positive.) from displaying until after the page was published. This issue occurred when an inline block had a block type that used a custom validation attribute, so it appeared only during publish but not when a draft was auto saved. 

The new Content Type Management UI supports grouping of property data types. To let other products and apps (add-ons) add their property types to such groups, a GroupName property is added to PropertyDefinitionType.

Fixed an issue that generated a 500 Internal Server Error because a page included a block list with a Category property.

Fixed an issue that caused a "drift" in scheduled job times due to delays employed to reduce risk of resource starvation.

When several jobs have approximately the same scheduled execution time, the scheduler service adds a delay of 10 seconds between each job execution to reduce the risk of resource starvation (for example thread).

However if there are many short-lived jobs that are scheduled with a short time interval then they might "drift" in start time due to this delay; for example, runs every third minute instead of every minute as it was scheduled.

You can configure the delay configurable to define a shorter interval if it suits your jobs better.

Fixed an issue where removing an inline block from a content area showed an error message. Now, the edits are saved successfully. 

Fixed an issue where the Create button in the Create block dialog box was not clickable when default values (SetDefaultValues) were assigned on an inline block.

Fixed an issue where an infinite loop that caused the server to malfunction resulted from a metadata controller when a model contained a LinkItem property type.