6.48 release notes

The way components were added to standard pages is by submitting a form. When the form was submitted, page validation was executed, and any required fields caused validation to fail. Components with required fields could not be deleted until valid values were added to the fields. The fix now skips or forces validation to pass when deleting the component. Components can now be deleted without filling in their required fields.

An issue with strict code typing on certain trigger event actions caused triggers that watched for Before asset deleted events with a Trigger log message (Error) action to run after the HIPO job deleted the asset. This code typing behavior caused the trigger actions designed to prevent assets from being deleted based on the error status sent to the logging system to be ignored by the HIPO delete process. The strict code typing for the trigger action was relaxed so that the trigger action fired before the delete action ran in the HIPO job. If Error is selected in the trigger action, the Before asset deleted trigger condition prevents the HIPO job from deleting the asset.

Cloudflare was unable to refresh the cache for authenticated users. Authors could see old content on the frontend for an extended time. Stale requests from Cloudflare are now always rendered as the public user. The Cloudflare cache will now refresh for all user types.

Tracking used to prevent circular dependencies in keywords was stored in the session. If a fatal error occurred during an %assets_contents% keyword render, that user session could not later render anything with an %asset_contents%` keyword. This incorrect user session state would often result in all asset listings rendering without contents for the session and potentially entering the cache for other users. The circular dependency tracking was moved to track at the request level. Fatal errors within the circular dependency tracking no longer affect other requests or users.

The render time threshold was constrained to 60s. Legacy-hosted Content Management instances might have very large or slow-loading pages that could not be generated after upgrading to 6.47. The threshold restrictions were adjusted to ensure the value was an integer. Legacy-hosted Matrix instances can now generate large, slow-loading pages.