Squidex v4.0.0 Release Notes

Release Date: 2019-11-13 // over 4 years ago
  • ๐Ÿ’ฅ Breaking Changes

    List Fields

    ๐Ÿš€ This feature contains a major update how reference fields and list fields are managed. In previous versions, schema fields had the properties IsListField or IsReferenceField to indicate whether a field should be shown in content lists or not. This was hard to manage in the UI and you could not specify the order. With this release schemas contain list of field names that should be used as list fields or reference fields. List field names can also contain meta fields like the content id or the content author. But we have decided not to implement a migration for that. If you use the feature you have to configure these fields again. Please not that the API is not affected and it is very likely not a breaking change for your consuming applications.

    .NET Core 3.0

    ๐Ÿ”ง Migration to .NET Core 3.0. This also includes some code changes such as cleanup of configuration and proper nullable support.

    โšก๏ธ This version does not use alpine image with self contained image any more. Therefore the final image is larger than before but the Squidex layer itself is smaller, which means a reduced disk size and download size when you update Squidex or when you have multiple versions installed or other .NET Core applications on your servers.

    Clustering

    ๐Ÿš€ This version introduces a new storage to communicate cluster members. Therefore it is recommended not to use a rolling deployment and restart the entire cluster instead.

    ๐Ÿ”‹ Features

    • ๐Ÿ’ป UI: New approach to manage list fields and schema fields.
    • ๐Ÿ’ป UI: Many small UI / UX improvements.
    • ๐Ÿ’ป UI: Improvements to the Geolocation editor.
    • ๐Ÿ’ป UI: Improved dialog to connect a client.
    • ๐Ÿ’ป UI: Improved Rule Wizard dialog.
    • ๐Ÿ’ป UI: Integrated cluster monitoring UI.
    • ๐Ÿ’ป UI: Improved schema UI.
    • ๐Ÿ’ป UI: Confirm dialog before removing contributor.
    • Workflows: Restrict when a content item can be updated by setting an expression or roles.
    • Workflows: Define multiple roles for workflows.
    • Rules: Action to write comments.
    • API: Migration to .NET Core 3.0
    • API: Configuratiopn option to recreated the superadmin whe nyou loose the password.
    • GraphQL: Flat content structure.
    • Clustering: Clustering improvements.

    ๐Ÿ›  Bugfixes

    • ๐Ÿ’ป UI: Fixed the buttons to change the status of multiple contents.
    • Rules: Fixed saving of rule names.