Sitefinity Cloud
Release Notes

What's new

Output caching for the .NET Core Renderer

The .NET Core Renderer can now serve fully rendered pages from a shared output cache rather than re-rendering them on every request. The cache is shared across the entire deployment, so a page rendered once is served from cache to all subsequent visitors regardless of which instance handles the request. Cache entries are invalidated automatically by the CMS when content is published, so visitors always receive current content without a manual purge.

This significantly reduces the time to first byte for pages that are not already cached at the CDN edge, and reduces load on the CMS during traffic spikes and after cache invalidation. The capability requires Sitefinity CMS 15.4.8635 or later and is enabled per environment. It is being rolled out gradually across projects.

Learn more about caching and performance here.

View Users permission

A new read-only View Users permission has been added to User Management. Users assigned this permission can open User Management and see the list of users and their group assignments, but cannot invite, edit, or remove users or change group membership.

This makes it possible to give team leads, auditors, and support staff visibility into who has access to a project without granting them the ability to change it. The permission is available as a group alongside the existing Manage Users group and is assigned the same way.

Learn more about User management here.

What's improved

• Fixed an issue where the Admin App Extensions deployment step reported success even when the files were not published, so failures are now surfaced in the pipeline.
• Fixed an issue where CI/CD failed with a request for a Redis host name in projects that do not use Redis.
• Fixed an issue where the cache flush step in CI/CD targeted an incorrect resource and caused deployments to fail.
• Fixed an issue where cached data created by an earlier CMS version could cause the application to fail after an upgrade, by automatically clearing the output cache during upgrades that require it.
• Fixed an issue where only the 404 error page could be configured per site, so all custom error page types can now be set individually for each site in a multisite project.
• Fixed an issue where automatic Sitefinity version upgrades failed during the build validation step in projects using non-standard build configurations.
• Fixed an issue where resetting multi-factor authentication for a user failed when their default second-factor method was a phone or SMS method.
• Added validation and a clear error message when an access rule expression exceeds the maximum supported length.
• Improved application warm-up during deployments so the application is verified as fully initialized before traffic is switched over.
• Upgraded the platform-hosted Redis service to the latest version for improved stability.