The following is a complete list of the bug fixes and enhancements provided in the August 2021 Release. Some of the bug fixes listed below may address existing Support Articles. A comprehensive list is at the bottom of this page.
Note: The 5.0.16 release is now available for developers to pull down and work with locally or to request for deployments.
There are no specific highlights for this release.
There are no high or medium priority breaking changes that occurred during this release:
Low risk changes are:
Added an index with a key of ParentId and TranslatedValue when the Name is “UrlSegment”. This significantly improves performance of pages like Product Detail for sites that have a large number of TranslationProperty records. SQL Server indexes keys cannot exceed 1700 bytes, which effectively limits UrlSegment translations to 842 bytes (16 bytes for ParentId GUID is 1684, which is then cut in half to 842 by the UTF-16 encoding of the nvarchar data type used for the TranslatedValue column.)
Resolved an issue with PageModel RequiresAuthorization affecting published status and preventing variants from being created in Spire. Retrieved PageModels were populating a dynamic value RequiresAuthorization. This value was not part of the page itself.
When publishing the page, this value was taken into account by some parts of code but not by others, leading to bugs like a page variant not being able to be created because the page was considered unpublished.
RequiresAuthorization was removed from PageModel, and added to the API call that retrieves a PageModel.
A redux selector getRequiresAuthorization has been added that can be used to retrieve the value from the redux state where it is now stored separately from the PageModel.
Implemented dynamic width calculation. The categoryItem width value will be calculated based on parent container and theme breakpoint values. Any value that was set will be replaced on load or window resize
Partners/Developers: You can view a cumulative list of breaking changes, including Spire breaking changes, in this spreadsheet. (Note the two tabs at the bottom of the spreadsheet: one for cumulative breaking changes, one for Spire breaking changes.)
