Optimizely - update 403

Improved the error message for the ZipArchiveVirtualPathProvider.FileDataLoader method to include diagnostic details.

You can use simple addresses as outgoing URLs (when simple URLs are available).  The following example shows how to set PreferredUrlFormat to Simple or Hierarchical (default) in startup.cs (or in appsettings.json).

public void ConfigureServices(IServiceCollection services)
{
    // omitted for brevity

    services.Configure<RoutingOptions>(o => o.PreferredUrlFormat = PreferredUrlFormat.Simple);
}

Fixed an issue where a job was stuck in a running state after an application crash by adding a Stop button that terminates the job.

You can have friendly media URLs (like https://www.something.se/en/research/research-support/contentassets/some-document.pdf) that are based on the content owner by entering the following configuration code:

public void ConfigureServices(IServiceCollection services)
{
services.Configure<RoutingOptions>(o =>
{
	o.ContentAssetsBasePath = ContentAssetsBasePath.ContentOwner;
});
}

You can now migrate ASPNET Identity data with CMS 12.

Content Cloud supports the editing of tiff files.

Although the default list may have file extensions that may not work with editing, the ImageEditorOptions.SupportedEditExtensions option is writable,

In Commerce Cloud 14.3.0, usage of BinartyFormatter was removed, which caused issues with Find.Commerce. Those changes were reverted to bring BinaryFormatter back in 14,3,1,

Fixed an issue where a block with an image property was created in Quick edit but was stored in the For this page folder instead of the For this block folder.

Fixed an issue where the Management site layout broke when subpages were opened.

Fixed an issue where the Cache-Control headers in CMS UI and Shell responses were missing endpoints.

Language Manager is now supported in .NET 6.

Fixed an issue where properties of type EnumMultiValue or DictionaryMultiValue are synced to PIM with wrong ControlType descriptors: TextField, DropDown, MultiSelect, RadioButton; these should only be MultiSelect.

Fixed an issue where no properties were auto-mapped in PIM when syncing models containing at least one decimal-backed property (float/decimal/etc.).

Fixed an issue where content type properties decorated with any validation attribute (StringLength/RegularExpression/Range) occasionally caused an error when publishing from PIM; these attributes are now ignored if the property is synced to PIM.

Fixed an issue where the publish job fails with an access denied error message after changing parent category for a product in PIM.

Steps to reproduce:

1. Create a profile filter definition with params being number data types (int, long, double):

{
  "Name": "Int_data2",
  "Description": "Number equal a value",
  "Query": "Payload.number eq {{value}}",
  "Parameters": {
    "value": "int"
  },
  "Category": "Profiles",
  "Type": "Profiles"
}

-> Create successfully

2.  Create a segment with filter definition in step 1 and insert a negative number in param like this:

{
  "Parameters": {
    "value": -2
  }
}

Expected result:

Returns 201 Created.

Actual result:

Returns 500 Internal Server Error.

Note: It does not occur in the event filter definition.