v4.2.15 release

Significant improvements

• Translations and localizations:

  • The reconciliation process between Brightspot and external services (such as Lingotek and AWS) has been improved.
  • The Translation widget was redesigned to improve usability.
  • Error reporting from Google Translate was improved. Filed under: translation
• Editors or administrators can now copy themes. Filed under: theme
• The integration with LinkedIn was upgraded to use LinkedIn’s latest API. Filed under: social link
• When an item is created on one site and published on another site, the available tags for the item are those associated with the publishing site. For example, an editor publishes an item to Site A; that editor can apply to the item only those tags associated with Site A. Similarly, if an editor publishes the same article on Site B, that editor can apply to the item only those tags associated with Site B. Filed under: tag
• In the Site Analysis widget, hovering over a point in the graph displayed a tool tip. The number in the tool tip corresponded to a date. Starting with this release, the actual date appears in the tool tip. Filed under: analytics
• DIMS URLs now include a strip path parameter. This parameter indicates if metadata should be stripped from the image. Filed under: image
• The rich-text editor’s find-replace widget was repositioned and redesigned so that it does not cover the editing area. Filed under: rich-text editor

• Audiences:

  • Editors can now created audiences at the site level.
  • Editors can search for archived audiences. Filed under: audience
• An editor locked out of an item can now see the locking editor’s avatar. For example, if Editor A is locked out of an item by Editor B, Editor A can see Editor B’s avatar (and ask that Editor B unlock the item). This was a feature in Brightspot version 3 that has been added to version 4. Filed under: locking
• In the content edit form, an error indicator appears at the cluster level (if it exists) in addition to the message or indicator at the field level. Filed under: content form

Significant defects addressed

• Certain settings for rich-text elements caused errors on save. This defect has been addressed. Filed under: rich-text editor
• Pagination by weekly buckets in the Scheduled Events widget caused the widget to display incorrectly. This defect has been addressed. Filed under: dashboard, schedule
• When Editor A opens an item in the content edit page, Editor B sees Editor A’s avatar in the Recent Activity widget. In some scenarios, Editor A’s avatar did not appear as expected. This defect has been addressed. Filed under: dashboard, locking
• Items published prior to January 1, 1970 appeared with publication date N/A. The publication date now appears correctly. Filed under: date
• In certain scenarios, the Recent Activity widget listed extraneous “current” content types (such as Current Brand and Current Country). The Recent Activity now lists only the relevant content types. Filed under: dashboard
• In certain scenarios, selection fields opened empty, and editors needed to re-open the selection field to populate it. Selection fields now open correctly, and contain options should they be available. Filed under: content form
• In certain scenarios, the caption language did not appear correctly in the AWS Elemental manifest. The caption language now appears correctly. Filed under: Amazon Elemental
• Publishing by email failed when submitting an item containing an image from an iPhone. This defect has been addressed. Filed under: email to CMS
• If an item contained a link to another item in draft status, translation for the first item failed. This defect has been addressed. Filed under: translation
• The template placeholder combination {{#with}}-{{else}} rendered differently in the Styleguide and production environments. The combination now renders consistently. Filed under: Styleguide
• Previewing an item that included certain types of rich-text elements caused the browser to become unresponsive. This defect has been addressed. Filed under: rich-text editor

• Keyboard shortcuts for the rich-text editor:

  • The keyboard shortcut ⌘-⇧-Q for inserting a pull quote conflicted with the macOS shortcut to quit all applications and log out. The shortcut is no longer available in the rich-text editor.
  • They keyboard shortcut ⌘-F for finding text was overridden by the identical browser shortcut to find text anywhere in a web page. The rich-text editor’s shortcut now takes precedence. Filed under: rich-text editor
• In some scenarios, the Scheduled Events widget caused high CPU usage. This defect has been addressed. Filed under: dashboard, schedule
• Search spotlights on terms incorrectly included partial matches. Search spotlights on terms now include only exact matches. Partial matches can still be specified as variants of the term. Filed under: search
• When a Brightspot deployment included the InDesign plugin, a styling error prevented display of the login page’s Forgot Password link. This defect has been addressed. Filed under: InDesign
• In some scenarios, images added to a gallery through bulk upload did not render on published sites. Images bulk uploaded to a gallery now render as expected. Filed under: bulk upload
• In some scenarios, promoting an item from another item did not populate the corresponding placeholder text. For example, promoting a video from an article in the article’s Overrides tab did not populate the promo’s title, description, and image with text from the video. The placeholder text is now populated as expected. Filed under: promo
• In some scenarios, workflow notifications were not working as expected. The condition causing this error was corrected. Filed under: notification, workflow

Breaking changes

• Due to an update to the LinkedIn API, the following signatures in AbstractLinkedInAuthenticationProvider have changed:

  • #authenticate:

    • Old: OAuth10aService oAuthService, OAuth1AccessToken accessToken
    • New: OAuth20Service oAuthService, OAuth2AccessToken accessToken

  • #createCallbackUrl:

    • Old: HttpServletRequest request, HttpServletResponse response, LinkedInToken requestToken
    • New: Site site, HttpServletRequest request
• This release disables the legacy SAML login filters by default via SamlAuth#useLegacySamlFilters. The filters can be enabled again by adding dari/useLegacySamlFilters = true in the context.xml settings.

• The disabled filters are as follows:

  • saml/src/main/java/com/psddev/saml/CmsLogin.java
  • saml/src/main/java/com/psddev/saml/CmsLogout.java
  • saml/src/main/java/com/psddev/saml/LoginFilter.java
• This release also changes the location to which SAML Identity Providers will need to POST their responses if that SAML Identity Provider will be used along with SamlToolAuthenticator. Instead of /cms/logIn.jsp, SAML Identity Providers will need to POST to /saml/login. This change is only required if using the new SamlToolAuthenticator.