Brightspot Releases

4.7 releases

Back to 4.7 releases

v4.7.11 release

Release date: January 31, 2024

Note

v4.7.11 is an official, cumulative release of all of its previous release candidates. See below for a breakdown of what each release candidate included. When upgrading to this version, your implementation of Brightspot receives all bug fixes, improvements, and new features detailed in this topic.

v4.7.11 has 12 bug fixes, six new features, and 13 improvements.

Significant improvements

Dari now supports the classes in java.time.
Drag-and-drop is now available in the search panel's board view for indexed fields such as section and tag.
Added sort order options to the search panel, such as newer/older for update date, A-Z/Z-A for label.
Added improvements to the AI Chat user interface.
Improved usability of the collections menu (available in the search panel under more_horiz.)
Added the Content Templates dashboard widget to integration testing.
Added bulk editing to integration testing.
Added non-publishable assets (such as dashboards) to integration testing.
Refactored code pertaining to the search panel in integration testing.
Added a permission that restricts editors to view assets only in their own collections or in appropriately shared collections.
Quick View (accessible by clicking info) is now available in the search panel's taxonomy view.
Refactored code for sticky search to avoid developer intervention when a new filter is added to the search panel.
In the search panel's Collections filter, editors can select more than one collection. This improvement allows editors to search for assets in more than one collection.

Significant new features

Bulk editing is now available for content templates. For example, an editor can change the headline field on multiple content templates.
Content reports are now available.
- Editors and admins can generate content reports for assets satisfying a broad range of criteria, such as content type, status, watcher, and package. The report output is fully configurable, and can include almost any field appearing in a selected content type.
- Role permissions now include access to content reports.
- A new Reports widget is available for inclusion in dashboards.
- Admins and editors can configure content report notifications.
- Editors can create content reports from the search panel.

Significant defects addressed

Corrected an issue causing the All Scheduled Items cluster to be incorrectly displayed.
Corrected an issue preventing a new collection from appearing as an available collection in the search panel.
Corrected an issue preventing a search widget in a custom dashboard from honoring the collections filter.
Corrected an issue causing icon misalignment in a basic list of asset previews (such as a basic list of images).
Corrected an issue throwing ClassCastException in the search panel.
Corrected an issue preventing proper filtering by tag when the search panel is in board view.
Corrected an issue preventing theme bundles from including folders starting with a dot (such as .well-known).
Corrected an issue displaying an unnecessary warning about altering header rows (as expected when importing a Google Sheets file) when importing a Google Docs file.
Corrected an issue preventing display of the Copy and Convert options in a module's more (more_horiz) menu.
Corrected an issue causing incorrect display of labels in the References widget.
Corrected an issue causing extraneous display of the Quick View icon (info) when dragging an asset inside a list.
Corrected an issue preventing field selection in a content report when the status filter is set to Any Status.

The following release candidates are also part of this release.

v4.7.11-rc.2023.12.21

v4.7.11-rc.2023.12.21 has seven bug fixes, three improvements, and two new features.

Significant new features

A Content Templates widget is now available for the dashboard. The widget lists content templates by underlying content type along with a quick view.
The Create New control in a reference field allows creating an asset from multiple content types, not just the content type in the current context. For example, when creating a new article, the Create New control in the Author field allows creating a new author or a new user.

Significant improvements

Quick View is available for selected assets in reference fields. For example, when creating a new article, clicking info for a selected author in the Author field displays the Quick View widget for the author.
An informational message appears when no changes are recorded after re-importing a Google Sheets containing tags or sections. Specifically, when the header row is deleted from a previously imported sheet, and changes are made to the data rows within the sheet, a message is displayed indicating those changes are not imported into Brightspot.
The method DataSupplier#get no longer requires the ToolPageContext page parameter. All calls to the method were similarly updated.

Significant defects addressed

Corrected an issue causing poor layout of adjacent and more_horiz icons.
Corrected an issue preventing correct reset of a referenced image. For example, an editor uploads an image (State A) and then modifies it (State B). Next, the editor selects the shared image as an article's lead, and modifies it again in that context (State C). When clicking Reset in the image editor from the article, the image reverted to State A instead of State B.
Corrected duplicate text in the explanatory note for configuring a new Google service.
Corrected an issue preventing retention of some search settings.
Corrected an issue throwing an IllegalStateException in the Recent Activity widget. The exception occurred when an asset's underlying content type was deleted.
Corrected an issue causing some integration tests to erroneously fail.
Accessibility:
- Added announcement to the New Workstream widget's Name field.

v4.7.11-rc.2023.12.13

v4.7.11-rc.2023.12.13 has 22 bug fixes, 14 improvements, and two new features.

Significant new features

Editors can now generate PDFs from an asset's content edit form.
The preview pane now has a toggle for tuning on or off Preview to Edit.

Significant improvements

Improved the search panel's taxonomy view to better accommodate long tag names.
Prior to this release, there were only two groupings of content types—Main Content Types and Misc Content Types—that appeared in various lists such as in the Create list. Administrators can now configure their own groupings of content types.
Administrators can assign colors to workflow statuses.
From an asset's content edit form, editors can add an asset to a collection, and can also view the collections in which the asset is included.
An asset's quick view now includes links to the asset's content edit form as well as a shared preview.
Editors can now filter for collections in the search panel.
Removed the Delete Permanently link in the following types of production guides: content type, page, and widget.
Changed field labels for configuring Quick View to improve consistency.
GitHub actions now include creation of containers for high-availability testing on Antithesis.
Code coverage reports are now included with integration testing.
Reworded option labels for sticky search.
Simplified APIs for the notification subsystem.
The class AbstractCmsPageTest was moved to a different package, and is now available to project developers.
Integration tests now include errors recorded in the browser console.

Significant defects addressed

Corrected an issue causing confusing display of a list while dragging an asset onto the list from The Shelf. In particular, when the list already included one asset, dragging the new asset from The Shelf did not provide a good indication of the new asset's position in the list.
Corrected an issue preventing application of a selected value in the search panel's Watchers filter.
Corrected an issue preventing deletion of a field's text in a production guide.
Corrected an issue preventing correct reset of the search panel's filters. When an editor has search filters configured for sticky or slightly sticky, clicking Reset in the search panel now reverts the content type to Any Content Type and retains the values of the other filters.
Corrected an issue preventing publication of assets in a bulk schedule. When the scheduled time arrived, the assets were not published.
Corrected an issue causing radio buttons in the Post Publish Actions widget to appear solid even when not explicitly selected.
Corrected an issue preventing Quick View from working when the search panel is in board view and the results are grouped by section.
Corrected an issue preventing removal of an image's preview in the Lead field. Specifically, an editor selects a shared image in the Lead field, and Brightspot displays the image's preview. The editor then selects a module in the Lead field. The preview for the previously selected image was not removed.
Corrected an issue preventing display of some material icons in the content edit form.
Corrected an issue causing incorrect display of the more icon more_horiz in the rich-text editor's table module.
Corrected an issue preventing an asset's Quick View from appearing in The Shelf after dragging the asset onto the content edit form.
Corrected an issue causing search filters from the content picker to be those set in the search panel. For example, an editor opened the search panel and filtered for any asset published in the last seven days. Subsequently, the editor opened a reference field for authors. The associated content picker retained the filter for assets published in the last seven days.
Corrected an issue causing the Save Search control to disappear from the search results menu after opening a collection.
Corrected an issue preventing import options from appearing when attempting to import a file from Google Drive or Microsoft Drive.
Corrected an issue causing a list's explanatory text from appearing under the expand all control unfold_more.
Corrected an issue preventing proper grouping of a list's or set's items.
Corrected an issue causing production guides to fail during integration testing.
Corrected an issue preventing population of alt text for SVG, PDF, and video previews.
Corrected an issue throwing a NullPointerException when opening search filters.
Corrected an issue preventing correct sorting of assets in the content picker.
Corrected an issue causing the number of assets surfaced in the search panel to be different from the number of assets reported in the actions menu.
Corrected an issue preventing bulk uploaded images from appearing in the search panel. Specifically, immediately after bulk uploading images, the search panel opens, but those images were missing.

v4.7.11-rc.2023.10.31

v4.7.11-rc.2023.10.31 has 13 bug fixes and 15 improvements.

Significant improvements

The Java Server Page record.jsp and associated pages were migrated to the FormInput class and associated subclasses.
The Java Server Page hotSpot.jsp and associated pages were migrated to the FileFormInput class.
Deprecated the initialBody element in the @RichTextElement.Tag annotation.
Updated the class ValueGenerator to allow for grouping of values in reference fields.
Deprecated the class ReferentialText and associated infrastructure. See "Breaking changes," below.
Converted the following files in /cms/tool-ui/src/main/webapp/v4/util/ to TypeScript:
- debounce.js
- getComponentKey.js
- noise.js
- repaint.js
- storage.js
- throttle.js
Editors can now filter for collections in The Shelf, and place individual assets within those collections on the content edit form.
Content templates now consistently reflect the hierarchy (from highest priority to lowest) user, role-site, role, site, global.
Admins are prompted with a message when attempting to have more than one default content template for a site.
- Admins receive a warning message when attempting to add a default content template to a site that already has a default content template for that content type.
- Admins receive an error message when attempting to use the same content template as both the default and an extra template for the same site.
Editors with access to the Publish Override transition, but with no access to any other transition, now see those transitions as read-only buttons in the Workflow widget. For example, a workflow has the transitions Send To Review, Send to Proofread, Publish, and Publish Override, and an editor has access to Publish Override. When opening the Workflow widget, the editor sees the next transition in the workflow as read-only. This improvement informs the editor that there may be other workflow steps necessary prior to publishing the asset.
Collections no longer are associated with a site; a collection can contain assets from multiple sites.
The Content Templates widget now has a filter field so editors can more quickly find their required content template.
Clicking a schedule in the Available Schedules widget now opens the Edit Schedule widget; previously clicking a schedule opened one of the assets contained in that schedule.
A new Enable Bulk Scheduling field is available in Edit Site. This field shows/hides the Bulk Scheduled Items field in the Edit Schedule widget.
Continued deployment of displaying workflow statuses with the same name only once in corresponding filter fields.

Significant defects addressed

Corrected an issue causing incorrect display of an editor's avatar in the search panel's board view.
Corrected an issue causing incorrect spacing between field labels and field values in the search panel's board view.
Corrected an issue causing incorrect display and functioning of the quick-view icon info in the search panel's board view.
Corrected an issue preventing successful drag-and-drop upload from a laptop into a gallery's content edit form.
Corrected an issue preventing display of an asset's lead image in the search panel's quick view.
Corrected an issue causing display of an extraneous image in the content edit form when adding a shared image as an article's lead.
Corrected an issue causing an integration test to fail on the class ContentEditDrawerTest.
Corrected an issue preventing filtering of items in a list based on characters typed in the field. For example, a list contains three values Apple, Orange, and Banana. When an editor typed App, the values in the list did not reduce to only Apple.
Corrected an issue preventing correct operation of the Replace, Insert, and Copy buttons in the ChatGPT integration.
Corrected an issue preventing correct focus when a gallery is in list view and the editor clicks on an image.
Corrected an issue preventing drag-and-drop from one column to another in the search panel's board view.
Corrected an issue preventing correct operation of two-factor authentication.
Corrected an issue causing incorrect positioning of The Shelf's close icon close.

Breaking changes

The JSP classes powering ReferentialText have been removed. Projects should use the Rich Text system instead. For details, see Rich text.

v4.7.11-rc.2023.9.28

v4.7.11-rc.2023.9.28 has seven bug fixes, 12 improvements, and one new feature.

Significant new feature

Added integration with OpenAI Chat.

Significant improvements

The initialBody element in the @RichTextElement.Tag annotation is now deprecated. Projects should use the toBody method in the RichTextElement class.
The file jquery.editableplaceholder.js was rewritten in TypeScript.
The status drop-down list in the search panel now displays workflow statuses with the same name only once. For example, the content type Article has two workflows, and both of them have a status named Review. Starting with this release, the status Review appears only once in the status drop-down list.
The Java Server Page searchResult.jsp was migrated to the SearchResultPage class.
The Java Server Page workflowActions.jsp was migrated to the Workflow class.
Ensured that object instantiation is package private for the following classes: RepeatingTask, SearchExtension, AutoPlugin, LocaleProvider, SiteMapType, and SiteMapConfig.
Replaced usage of the annotation @FieldDisplayType with @FormInputClass.
When adding a user as an asset's watcher, it is no longer necessary to click Add. Selecting the user in the View Watchers widget immediately adds the user.
Changed the threshold for displaying a + indicator to the notification count from 100 to 1000. When an editor accumulates 1000 or more notifications, the notification count is a static +.
The file v4/TextInput.js was rewritten in TypeScript, and is now delivered as a Lit web component. See "Breaking Changes," below.
Users can no longer create multiple Shelf Type Settings with the same content type.
When Sticky Search is enabled, Brightspot now retains the last setting for the search panel's Show field for the current content type. For example, an editor sets the Show field to 20 when filtering on images. The next time the editor opens the search panel and filters on images, the Show field is set to 20.

Significant defects addressed

Corrected an issue causing different production guides to appear for <domain>/cms/ and <domain>/cms/index.jsp.
Corrected an issue preventing successful login to Brightspot even after providing the correct username and password.
Corrected an issue preventing modification of strings in text fields.
Corrected an issue causing The Shelf to appear over the image editor's Done button.
Corrected an issue preventing the image editor from opening when attempting to edit an image associated with an asset's lead module.
Corrected an issue preventing display of the dashboard after successful login through Google single sign-on.
Corrected an issue causing build failures.

Breaking changes

Migration of v4/TextInput.js to TypeScript requires the following:
- Code using CSS selectors to select inputs such as > input need to be changed to > btu-input input. The platform code has been updated accordingly, but any custom code outside platform will need this change.
- Inputs of type checkbox (<input type="checkbox">) and visually hidden inputs are unaffected.

4.7.11-rc.2023.9.18

4.7.11-rc.2023.9.18 has four bug fixes and four improvements.

Significant improvements

The Java Server Page searchResult.jsp was migrated to the SearchCollectionForm class.
The Java Server Page workflowActions.jsp was migrated to the Workflow class.
Users can no longer create multiple Shelf Type Settings with the same content type.
When Sticky Search is enabled, Brightspot now retains the last setting for the search panel's Show field for the current content type. For example, an editor sets the Show field to 20 when filtering on images. The next time the editor opens the search panel and filters on images, the Show field is set to 20.

Significant defects addressed

Corrected an issue throwing a message null value in entry: username=null when displaying a profile or user page.
Corrected an issue causing The Shelf to appear over the image editor's Done button.
Corrected an issue throwing a TypeError when attempting to edit an image from within a page's lead promo.
Corrected an issue preventing the image editor from opening when attempting to edit an image associated with an asset's lead module.
Corrected an issue preventing display of the dashboard after successful login through Google single sign-on.
Corrected an issue causing build failures.

4.7.11-rc.202308

4.7.11-rc.202308 has 11 bug fixes, 19 improvements, and three new features.

Significant new features

Collections:
- Editors can add assets to existing collections directly from the search panel's more menu (more_horiz > Add To Collection).
- Editors can view available collections by selecting menu > Collections. In that widget, editors can modify and delete collections.
Developers can view a JSON representation of an asset under the Tools widget.
Editors can now add and remove assets from a bulk schedule in the Edit Schedule widget.

Filters for users now include a Current User preset. For example, the filters for Publish User and Update User include a preset Current User.
Deployed an integration test framework that supports the following: Playwright, Antithesis, animations, screenshots, and video recording.
Removed the Java Server Page enhancementResult.jsp.
The Java Server Page settings.jsp was migrated to the UserSettings class.
The Java Server Page index.jsp was migrated to the IndexPage class.
The Java Server Page enhancement.jsp was migrated to the EnhancementPage class.
The Java Server Page header.jsp was migrated to the ToolPageContext#writeHeader method.
The Java Server Page objectPost.jsp was migrated to the FormRequest#processObject method. See "Breaking Changes," below.
The file v4/TextInput.js was rewritten in TypeScript, and is now delivered as a Lit web component. See "Breaking Changes," below.
The settings Auto Watch User On Publish and Auto Watch User On Update are now enabled by default.
An editor's Quick View settings override those set at the site level only for the selected content types. For example, an editor defined quick-view settings for articles. Prior to this release, that setting implied the editor wanted quick views only for articles, and quick views for any other content types at the site level were blocked. Starting with this release, the editor's configuration for an article's quick view overrides the site-level settings for articles, but quick views for other content types flow from the site to the editor.
Enhanced the native GraphiQL explorer so that the cursor does not unexpectedly jump from the current editing position in the middle pane.
Quick View is now available in the search panel's Board View.
Integrated search is now available with the Brightcove integration.
Improved the note appearing in the New Facebook Service widget.
Improved the notes appearing in the new service widget for the following services: Google, Instagram, LinkedIn, and Twitter.
Updated the GraphiQL npm package to version 3.
Updated the file cms/tool-ui/src/README.md to reflect changes in TypeScript functions.
Added README documentation to the OneLogin authentication module.

Significant defects addressed

Corrected an issue throwing a message null value in entry: username=null when displaying a profile or user page.
Corrected an issue that, after deleting a standard content type, deleted associated editorial content types and also displayed a validation exception message. Starting with this release, deleting a standard content type archives (instead of deletes) any associated editorial content types.
Corrected an issue that prevented display of the controls Add Tags and Add Sections in the Suggestions widget when the editor has an assigned role.
Corrected an issue causing The Shelf's close button close from appearing in the wrong place.
Corrected an issue generating an excessively large clickable area around the add_circle_outline Add Object Type in the New Site Search page.
Corrected the following issues in the GraphiQL explorer:
- Fields named deprecated appeared as deprecated.
- Nested deprecated fields did not appear as deprecated.
Corrected an issue that prevented new users from resetting their passwords on first login.
Corrected an issue that threw a message Invalid advanced query when a new user opened the search panel.
Corrected an issue preventing the search field from working correctly in the module picker.
Deprecated ToolPageContext#writeQueryRestrictionForm (which created two web forms) in favor of ToolPageContext#writeQueryRestriction.
Corrected an issue that was causing the error message Unable to process file type [UNKNOWN TYPE] for Remote Theme Bundle. File must be gzip or zip file! to display incorrectly when creating a theme from a remote bundle (New Theme > Main > New File > New URL).

Breaking changes

The new method FormRequest#update provides the same functionality as objectPost.jsp. That method requires three parameters:
- object—The object to be updated, cannot be null.
- includeFields—A collection of strings representing the names of the object's internal fields that will be updated. Can be empty or null.
- excludeFields—A collection of strings representing the names of the object's internal fields that will not be updated. Can be empty or null.
includeFields and excludeFields should never be used together in the same method call.
Migration of v4/TextInput.js to TypeScript requires the following:
- Code using CSS selectors to select inputs such as > input need to be changed to > btu-input input. The platform code has been updated accordingly, but any custom code outside platform will need this change.
- Inputs of type checkbox (<input type="checkbox">) and visually hidden inputs are unaffected.