v4.2.11 release

Significant improvements

• The Lead widget now includes a Recently Used list to quickly add a component to an item. Filed under: content form
• Prior to this release, the rich-text editor did not adequately preserve attributes for objects with no fields. Starting with this release, the rich-text editor preserves attributes for such objects. Filed under: rich-text editor
• In some cases, toggling a field on or off did not correctly change the toggle’s color. Brightspot now renders the toggles with the correct color depending on the “on” or “off” value. Filed under: content form
• The GraphQL implementation was enhanced to reduce unnecessary overhead. Filed under: GraphQL
• Admins have a new Site Redirects feature that redirects traffic from one domain to another. Filed under: URL

Significant defects addressed

• Updates to the rich-text editor caused a regression error with the track changes feature. Track changes now works as expected. rich-text editor
• When clicking on a saved search, Brightspot intermittently displayed a message Request URI too long. Clicking on saved searches no longer results in this error. Filed under: search
• An update to localization caused a regression error the display of Brightspot widgets in the InDesign plugin. The widgets now appear as expected. InDesign
• Tabs with the same display name caused incorrectly nested layout of fields in the content edit form. Tabs with the same display name now render fields correctly. Filed under: content form
• The Description field in the SEO tab did not always display the correct value. The correct value now appears. Filed under: SEO
• Hidden content types appeared in drop-down lists of content types. For example, if the Author content type is hidden, Author appeared in drop-down lists of content types. Hidden content types no longer appear in such drop-down lists. Filed under: content form

• Field-level locking in revisions. Consider the following scenario:

  • Editor A creates an item, creates a new revision of that item, and tabs into a field.
  • Editor B opens the same revision, and tabs into the same field. Editor B sees the warning that Editor A has already locked the field.
  • Editor A makes a change, saves the item, and tabs out of the field.
  • Editor B receives an indication that the field is no longer locked.
• In this scenario, Editor B can now modify the field. However, the text Editor B sees in the field is not the most recent version that Editor A has saved. When saving the item, Editor B overwrites Editor’s A latest text. Starting with this release, Editor B must refresh the content edit page before making changes in the revision. Filed under: revisions
• Prior to this release, the Resources widget for a site did not correctly display fallback resources available at the global level. Starting with this release, a site’s Resources widget displays resources at the global level unless overridden at the site level. Filed under: content form

Breaking changes

• Package name prefix and ViewModel suffix are removed by default for type and field names generated from Java class names in the GraphQL CDA. There are now “Truncation Settings” available in the CDA endpoint configuration to revert this functionality.
• Removed duplicative types in the CDA by only including one GraphQL type per @ViewInterface type as opposed to also including one for each concrete view model that implements the interface. As a result, classes that extend ContentDeliveryApiEndpoint will now have package name prefix, View suffix, and ViewModel suffix field truncation turned on by default. These are optional and can be turned off by overriding the isTruncatePackageName and/or isTruncateViewAndViewModelSuffixes methods. New instances of CustomContentDeliveryApiEndpoint will also have these settings turned on by default; however, existing instances will not.

• Decoupled the graphql-java library implementation from the core GraphQL plugin APIs, so other libraries can be used in the future without breaking API signatures. This decoupling has the following effects:

  • Site and API keys can no longer be specified via the HTTP body.
  • The corsDomainWhitelist field is removed from CustomContentManagementApiEndpoint and CustomContentDeliveryApiEndpoint in favor of the new corsConfiguration field. The relocateCorsDomainWhitelist method now exists to migrate corsDomainWhitelist data to corsConfiguration.
  • The entryViewClasses field is removed from CustomContentDeliveryApiEndpoint in favor of the queryEntryViewClasses field. The relocateEntryViews method exists to migrate entryViewClasses data to queryEntryViewClasses.
• We simplified CDA schema input fields by only including the path argument for content that implements Directory.Item. With this change, path will no longer be recognized as a parameter for querying records that do not implement Directory.Item. For retrieving such items via permalink, the path must instead be passed via the id parameter.

• The addition of vanity redirects to Brightspot mandated the following changes to tool roles:

  • Wildcard Redirect : admin/wildcardRedirectSearch -> redirects/wildcardRedirectSearch
  • Vanity Redirect: admin/vanityUrlRedirectSearch -> redirects/vanityUrlRedirectSearch
• All roles that restrict or give access specifically to these admin areas will need to be updated.