Brightspot Releases

v4.2.19 release

Release date: May 3, 2021

v.4.2.19 had 125 bug fixes, 6 new features, and 28 improvements.

Significant improvements

  • Reorganized fields in Site and Profile widgets—Starting with this release, fields in the Edit Site widget are neatly organized into five tabs: Main, Front-End, Integrations, CMS, and Plugins. Regarding the Profile widget, features such as Notifications and Subscriptions moved to the Main tab, and Content Templates and Dashboard options moved to a new CMS tab.
  • One-off themes—Editors can create one-off themes when creating new sites.
  • Creating new content types from existing ones—Editors can build new content types by modifying existing ones (instead of building them from scratch). For example, editors start with the Article content type, and add, remove, and reposition fields, and save as a new content type. This feature helps publishers customize Brightspot to fit their workflow.
  • Various improvements to track changes and commenting. In particular, in full-screen mode—

    • Comments now wrap to the next line.
    • When viewing comments and changes, the rich-text editor is centered between the left side of the editing area and the right rail.
    • When viewing only comments, there was a gap between the right rail and the rich-text toolbar. That gap was removed.
  • Login image—Prior to this release, the random image on the login page was provided by a third party. To maintain a consistent editing experience, the login page is now a static image that can be customized.
  • Drag-and-drop URLs—Editors can drag and drop URLs in the URLs widget.
  • Tealium integration—Publishers can integrate Tealium’s customer data platform to improve audience segmentation and to create actionable and comprehensive customer profiles.
  • Marketo integration—Marketing departments can integrate their Marketo forms directly into Brightspot.
  • GraphQL—

    • Developers can now determine if a record was updated by the CMA, and can also retrieve relevant metadata for tracing or debugging.
    • Developers can now specify predicate variables in the CMA.
    • Persisted Query Java APIs and implementations have been improved and made more flexible.
    • Editorial content types are now included when the Record object type is included in CMA.
    • Scrubbed GraphQL widgets for inclusive terminology.

Significant defects addressed

  • In some scenarios, clicking on a revision in the search panel displayed an unrelated content edit form. For those scenarios, clicking on a revision in the search panel now displays the correct content edit form.
  • Rich-text editor—

    • With tracked changes on, editors could not add enhancements in the rich-text editor.
    • With tracked changes on, editors could not create or delete tables.
    • Consecutive grave accents (backtick, `) appeared only once.
    • Consecutive bulleted lists with no intervening text appeared as a single bulleted list.

    These defects have been addressed.

  • The widget for listing and editing social networking accounts (navigation menu > Social > Accounts) did not appear correctly after selecting an account to edit. The widget now appears correctly.
  • In some scenarios, clicking Back in a content edit form to return to a content picker generated an error. For example, clicking New in a content picker to create a new item displays a content edit form with a Back button; clicking on Back generated an error. For those scenarios, clicking Back returns to the content picker without error.
  • In some scenarios, the Edit Global or Edit Site widget did not display an archived object. For example, if the Edit Site widget specified a particular search page, and the search page was later archived, that search page did not appear in the Edit Site widget. For those scenarios, archived values now appear in the Edit Global or Edit Site widget.
  • Prior to this release, the widget for selecting fields appeared under the widget from which it was opened (and editors could not use the widget). For example, in the search panel, clicking settings displayed a Select Fields widget under the search panel. Starting with this release, the Select Fields widget appears over the widget from which it was opened.
  • Filters in the search panel did not always limit results to the filter. For example, if searching for users by a particular role, the search panel displayed all users—not just those matching the selected role. This defect has been addressed.
  • In some scenarios, the selection fields in the bulk edit widget did not display the available values. For example, in a bulk edit widget containing multiple articles, the selection field for Authors did not list any existing authors. For those scenarios, selection fields in the Bulk Edit widget now display available values.
  • Federated search—

    • Prior to this release, imports from a Getty federated search incorrectly retrieved a small image resolution (size), even if a larger resolution was available. Starting with this release, imports from Getty federated search retrieve the largest available resolution.
    • In the search panel, selecting items retrieved from a federated search and then moving to the next page cleared the selection. For example, an editor performs a federated search having 10 pages of results. The editor selects three items on the first page and then proceeds to the next page. The first three items became deselected. This defect has been addressed.
  • In some scenarios, editors could not cleanly save new items. After the save, the title disappeared and the Generate Permalink checkbox was cleared. This scenario often occurred when an editor was assigned to a role, and the item was made from a content template. For those scenarios, new items save correctly.
  • Prior to this release, changing the value of a checkbox in the content edit form did not always trigger a work-in-process save. Starting with this release, such changes trigger a work-in-process save.
  • When publishing a content variation for an audience, the notification area did not appear, and after clicking Publish the work-in-process status was not cleared. This defect has been addressed.
  • An editor creates a content variation for an audience, publishes it, and then creates a new revision for that item. In some scenarios, attempting to view any of the item’s previous revisions in the preview pane generated an error. This defect has been addressed.
  • Prior to this release, editors could not remove the last item from the Quick Start widget. (Removing the last content type from the Quick Start widget was always possible.) Starting with this release, editors can remove the last item.
  • In some scenarios, a nested template did not display the containing content. For example, a parent template includes a child template rendering a media player. The child template did not always appear. This defect has been addressed.
  • Prior to this release, CSV exports from the search panel did not always create a clean file. In particular, values may take up more than one column, causing subsequent values to appear under an incorrect heading. Starting with this release, values in CSV exports are aligned under the correct heading.
  • Prior to this release, when an editor placed an image overlay on a video, various controls (such as position, opacity, duration, fade in/out) were missing. Starting with this release, the overlay controls are available.
  • In some scenarios, editors submitted items to Brightspot over email, and the content was not correctly ingested into Brightspot. For example, the ingested “from” and “to” addresses contained invalid values. This defect has been addressed.
  • Prior to this release, after completing a workstream, the Continue button was still available; clicking Continue generated an error. Starting with this release, the Continue button is not visible after completing a workstream.
  • In some scenarios, the content edit form’s Community tab had an inconsistent appearance or even generated an error instead of displaying an event log. This defect has been addressed.
  • Prior to this release, Brightspot displayed a raw server error (500) when an archived editor attempted to log in. Starting with this release, Brightspot displays a graceful error message inside the login widget.
  • In some scenarios, editors could not skip an item in a workstream when that item was scheduled for later publication. This defect has been addressed.
  • In some scenarios, a work-in-process condition occurred after updates to non-editorial, read-only fields in the content edit form. For example, if the content edit form contained a read-only field displaying the current time, and the current time changed, the item entered a work-in-process state (and Brightspot tracked that change as one to be saved or discarded). For those scenarios, changes in non-editorial, read-only fields no longer generate a work-in-process condition.

Breaking changes

  • All comparisons (=, !=, <, >, <=, >=) against _any field will throw an UnsupportedOperationException. Use matches instead.
  • As a result of improving persisted GraphQL query Java APIs and implementations, a number of deprecations were made.

    • Previously, the AutomaticPersistedQueryProtocol and StaticPersistedQueryProtocol classes were concrete classes extending the abstract class GraphQLPersistedQueryProtocol. These classes contained all logic specific to their respective protocols. Now, AutomaticPersistedQueryProtocol and StaticPersistedQueryProtocol classes are abstract classes extending the abstract class GraphQLPersistedQueryProtocol. The abstract classes now contain all protocol-specific logic. CustomStaticPersistedQueryProtocol and CustomAutomaticPersistedQueryProtocol replace their concrete predecessors, and are intended for use cases where configurable CMS fields are necessary.
    • Therefore, the original usage of AutomaticPersistedQueryProtocol and StaticPersistedQueryProtocol objects should be replaced with those implementations if the contained fields are still necessary. If fields aren't necessary, extend one of the abstract classes, or implement the interface to supply the intended implementation.
    • For editorial cases, persisted query protocol data from the prebuilt APIs will automatically be migrated with the relocation logic in the CustomContentDeliveryApiEndpoint#getPersistedQueryProtocol and CustomContentManagementApiEndpoint#getPersistedQueryProtocol methods, but other custom-built APIs should implement a similar fix in order to migrate the original persisted queries' data as well.
Previous Topic
v4.2.20.1 release
Next Topic
v4.2.19.8 release
Was this topic helpful?
Thanks for your feedback.
Our robust, flexible Design System provides hundreds of pre-built components you can use to build the presentation layer of your dreams.

Asset types
Module types
Page types
Brightspot is packaged with content types that get you up and running in a matter of days, including assets, modules and landing pages.

Content types
Landing pages
Everything you need to know when creating, managing, and administering content within Brightspot CMS.

Admin configurations
A guide for installing, supporting, extending, modifying and administering code on the Brightspot platform.

Field types
Content modeling
Rich-text elements
A guide to configuring Brightspot's library of integrations, including pre-built options and developer-configured extensions.

Google Analytics
Apple News