6.50 release notes

If there was an issue loading a manifest or schema for a component, the content page could not be saved and an error is shown. Users were unsure which component or variation needed to be removed to save the page because the error was not tightly linked to the component or variation with the manifest error. An error is now shown for the component or variation in question so that the user can identify which component needs correction before the page can be saved successfully.

When a content page component was loaded with a manifest fetching error, the only way to fix the error was to delete the whole block because the manifest fetching error could remain and block users from saving. When deleting a variant that contains errors on a component, the cache refresh now runs to clear up any errors persisting in the cache from the erroneous variant and allows the page to save.

LDAP bridge assets now offer a configurable Network Timeout field. This field allows setting the timeout for a connection to the LDAP server and defaults to 10 seconds. Ten seconds was the previous limit, but it could not be configured per bridge.

A race condition was observed when React.js components took over 1 second to load on the Metadata screen. The unsaved popup appeared even though no changes were made on the Metadata screen due to the screen’s state being empty. The state is now re-initialized inside the Metadata screen code, which prevents the popup from appearing if no changes to the screen are made.

The RenderTimeLimitException, introduced as part of the Enable Render Short Circuiting beta feature, was unhandled on some code paths. The unhandled exception could cause unexpected fatal server errors. RenderTimeLimitException is now handled on the identified code paths and prevents errors from occurring.