Optimizely - update 388

Fixed an issue where the MaxMind geolocation criteria did not handle connections correctly because the DatabaseReader should be reused. See https://github.com/maxmind/GeoIP2-dotnet#database-usage.

Fixed an issue where the MaxMind geolocation criteria did not handle connections correctly because the DatabaseReader should be reused. See https://github.com/maxmind/GeoIP2-dotnet#database-usage.

There were duplicated criteria in languages other than English.

For content types that created from code, the Use adjusted default settings option was disabled when you should be able to change the default values for content types created from code. 

When the database was in readonly mode, you were redirected to the login page instead of showing a ReadOnly page.

In the following scenario, the Title field from the PageHeaderBlock would appear in the exported data, but not the AltText or Caption from the ImageBlock that it was using as a property.

Page :: GenericPage

• Block :: PageHeaderBlock
  • String :: Title
  • Block :: ImageBlock
    • String :: AltText
    • String :: Caption
• ContentArea :: Content

The Version gadget remained open when it should have been collapsed after edit view was loaded again.

In some cases, you could not drag and drop an allowed content item, or you could not drag and drop a restricted content item.

You can now set default values for additional fields in the content type management UI in CMS 12, just as you could with the UI in CMS 11.

You can enable a screen, that is displayed on first request to create an admin user, by adding services.AddAdminUserRegistration() in your startup class. You can configure which roles should be assigned to the user, and how and when this screen should be available. This feature works only if the configured UIUserProvider supports user creation.

Mapping CMS content in router broke StaticFileMiddleware's ability to provide embedded files. When you registered the routing for content, it overwrote the file providers within the StaticFileOptions instance, without regarding that the change affected the StaticFileMiddleware.

Previews for .SVG and .ICO thumbnails in Edit UI were broken.

Display a loading indicator whenever editor changes context such as:

• Navigating content (page, block, media, ...)
• Changing view setting (channel, visitor group, ...)

For more information, see Loading indicator whenever view or context is changed (optimizely.com).

Removed dependency to Az.Storage and Azure.Storage to make the module completely standalone.

Overwriting an existing code package is not supported (for CMS 12/Commerce 14 and above) and the deployment API throws an error when this is attempted. That error message was improved.