v4.5.14 release

v4.5.14 had 26 bug fixes and five improvements.

Significant improvements

• Fields annotated with @CodeType can now display multiline text specified in the @Placeholder annotation.
• Updated JUnit response tests for GraphQL CDA endpoints following a previous improvement in error messages.
• The CMA delete mutation now includes a toolUser query variable by default.
• Improved accessibility in the CMS.
• Initial loading of all global content edit forms is more performant.

Significant defects addressed

• Corrected an issue in which editors could modify text in the rich-text editor that was marked as read only.
• Corrected an issue that prevented the prompt (Required) from appearing in password fields that were marked as required.
• Corrected an issue in which editors could add assets of a specific content type to a list even if the content type was excluded from the available selections. Technically, the annotation @TypesExclude({SharedModule.class}) on a field within a class SharedModulePlacement was not honored by List<T> fields annotated with @ToolUi.AddShared(sharedClass = SharedModulePlacement.class, field = "shared").
• Corrected an issue that threw a StackOverflowError error when doing an SQL-to-Solr copy.
• Corrected an issue that threw an UnsupportedOperationException error when attempting grouping operations.
• Corrected an issue preventing selection of a type in the field Content Types > Items > Query Field > Type.
• Corrected an issue that threw a JavaScript error when clicking multiple times on a shared overlay in the preview pane.
• Corrected an issue in which saving an editorial content type generated 500 or 503 server errors.
• Corrected an issue in which, after archiving an integration (such as Shutterstock), admins could still configure the integration.
• Corrected an issue that prevented correct display of production guides when the browser window has a width in the range 769px–1200px.
• Corrected an issue in which an asset's permalink did not include the default site's URL when the site itself is null.
• Corrected an issue which threw a FileNotFoundException error when using the annotation @InputProcessorPath to call a ToolPage servlet.
• Corrected an issue in which the annotation @SuggestedMaximum was ignored when applied to rich-text fields.
• Corrected an issue in which, after adding fields to a new version of a schema, those new fields were not highlighted when comparing the versions.
• Corrected an issue causing incorrect styling of the Advanced Query Builder widget.
• Corrected the following issues pertaining to preview-to-edit:
  
  • Editors could not edit assets using the preview-to-edit feature.
  • Clicking on a field in the preview pane scrolled the content edit form to a different field.
  • Not all of the fields in the preview pane were enabled for preview-to-edit.
  • In some configurations (front-end/preview URL on a domain different from the CMS; preview-to-edit disabled at the global level, enabled at the site and profile levels), preview-to-edit did not function.
  • Clicking a shared embedded child asset in the parent asset's preview pane opened a different, incorrect child asset in the content edit form.
• Corrected an issue causing the message key message.warning to appear in the content edit form instead of the actual message.
• Corrected an issue throwing a NullPointerException error when listing an editorial content type's assets associated with a pitch that are not associated with the pitch's site. For example, an editor is working on the site Brightspot. This site's Assignment Desk allows for assets based on the editorial content type Story. The editor publishes an asset based on Story, and in the asset's Sites widget selects None for Owner. The editor returns to the pitch and reloads. In this scenario, Brightspot displayed a NullPointerException.
• Corrected an issue that threw a ClassCastException error when attempting to retrieve an ExternalContentRichTextElement (such as TweetUrl or RawHtml).
• Corrected an issue in which custom style options were not available for assets inside of list modules.
• Corrected an issue in which the reply widget for a conversation's post allowed horizontal scrolling.
• Corrected an issue in which archived content-type modifications were not listed in the Content Type Modifications widget.