4.5 versions

Read below for more information on each version in the 4.5 release.

v4.5.34

v4.5.34 had three improvements, and 18 bug fixes.

Improvements

• Enhanced the SiteMapEntry lastmod field to support full timestamp formatting with both date and time.
• Added support for Java 16+.
• Added onFind, setupMenuForAria, and toggleMenu functions to window.BRIGHTSPOT.js for experimentation from newer Brightspot versions to 4.5.

Bug fixes

• Fixed an issue where links inside pop-up frames would reload the entire page, navigating you away from the underlying page you were editing.
• Resolved an issue where changes to a name made via a content form with a Global scope persisted, even after editing the form’s scope or deleting the form.
• Fixed an issue where the Create New option of ComboInput was not keyboard accessible.
• Resolved an issue where users could create new revisions from revision pages even when draft creation was disabled.
• Resolved an issue where the Archive button was visible and occasionally functional for users that did not have archive permissions in admin areas.
• Addressed an issue where the Report widget would display an empty table with no message when no results were returned. An info message is now shown when there is no data to display.
• Resolved an issue where workflow options were missing when editing content revisions in draft or other non-published states.
• Fixed an issue where dragging and dropping multiple articles from The Shelf into the rich-text editor would result in only the last article link appearing.
• Fixed CMS image preview functionality to properly handle a URLStorageItem using a URL that contained spaces encoded as + instead of %20.
• Fixed calendar date/time picker issue that was resetting the selected time to the present time when viewing it after setting it.
• Fixed an issue where attempting to publish a revision without a publish override would incorrectly reset the workflow, rather than publishing the revision as intended.
• Fixed an issue where the banner on revision items would incorrectly show Published instead of Updated during workflow states.
• Fixed JavaScript error that occurred when using the rich text editor's full screen mode in places other than on a content edit page.
• Fixed an issue where the contents of the Dari HTML <style> element were incorrectly escaped.
• Resolved an issue where updated editorial information was not being displayed by PrePublishAction.shouldDisplay upon publishing.
• Removed an obsolete static database environment reference from TypePermission, replacing it with up-to-date usage of DatabaseEnvironment.getCurrent().
• Resolved an issue where enabling the debug profiler would display unintended sequence numbers at the top of HTML pages.
• Resolved issues with unnecessary spacing and padding in top-level widget messages and class notes.

v4.5.33

v4.5.33 had eight bug fixes.

Bug fixes

• Fixed an issue where the URL in the URLs widget would sometimes run off the page.
• Fixed an issue related to accessibility of the Bulk Workflow button.
• Fixed an issue related to accessibility of the Reset Filters button.
• Resolved an issue where unscheduling the revision set for a future date did not clear the publish date.
• Saved search links are now shortened in versions 4.5.x and 4.7.x.
• Fixed an issue where FieldAccessFilter added comments inside HTML tags that do not support them.
• Resolved an issue where the notifications were not being rendered when site specific role was set.
• Resolved an issue where an exception thrown in a method of the ViewModel would prevent the entire ViewModel from displaying.

v4.5.32

v4.5.32 had five bug fixes.

Bug fixes

• Fixed an issue where mirror preview attempted to display a preview for rich-text elements, for which there is no ability to do so.
• Resolved an issue where the replication cache reported a healthy status despite having stopped receiving updates.
• Fixed an issue causing read-only fields to be sortable.
• Fixed an issue where revision validation occurred before a content state was set to be updated by widgets. Since validation occurred before additional changes were made, the additional changes would sometimes survive validation when they should not have.
• Resolved an issue where revisions would at times run validation without first calling beforeSave().

v4.5.31

v4.5.31 had two bug fixes.

Bug fixes

• Resolved an issue causing slow preview load times.
• Updated how some errors during data retrieval are handled in environments that use GraphQL. Instead of erroneous fields returning null (which are indistinguishable from actual null values), these fields now have their errors appropriately included in the GraphQL response.

v4.5.30

v4.5.30 had one new feature, one improvement, and 11 bug fixes.

New features

• A user with a role that has the Publish permission, but does not have the Workflow permission, now sees the Publish button on the content edit page of an asset.

Improvements

• If content has not been published in more than two days, Brightspot will now generate an empty sitemap instead of no sitemap at all, which resulted in a 404 error.

Bug fixes

• Fixed an issue when creating a table inside of a table that caused table icons to overlap.
• Fixed an issue preventing changes to data that was relocated from one module type to another to persist after the first save action. Now, changes persist after the first save action after data is relocated from one module type to another.
• Fixed an issue that caused a page to get stuck in an infinite loop when saving a content template.
• Resolved an issue by increasing the Lingotek connector locale limit from 300 to 1000.
• Corrected an issue that saw a WIP message displayed on the content edit page after moving a revision between workflow states or after saving a revision while it was in a workflow state.
• Resolved an issue causing an error when loading a content edit page after a populated field in a data model changed from a single embedded record field to a list of the same record type.
• Fixed an issue in which the images that are dragged from The Shelf were appearing in the wrong order.
• Fixed an issue that was confusing the view system reflection APIs when searching for the list of properties of a view model. This fix introduced a breaking change. See "Breaking changes" below for more information.
• Fixed an issue where pasting links surrounded by <u> tags into a rich-text editor field was removing the link.
• Fixed an issue causing editorial content types to not be properly represented in the GraphQL schema upon schema generation.
• Resolved an issue where large GraphQL endpoints, due to the length of time it took for them to load, were making other endpoints temporarily unavailable.

Breaking changes

• As a result of fixing an issue caused by a getModel method on ViewModel, the viewModel#getModel instance method has been removed, and there is now a new static ViewModel#getModel(Object) method.

v4.5.29

v4.5.29 had two improvements and nine bug fixes.

Improvements

• Backported translation functionality to better indicate which pieces of content are translations of one another.
• Made changes to keep Brightspot compatible with Lingotek as a result of a recent authentication mechanism change.

Bug fixes

• Fixed an issue preventing modules added in between tab modules from being clickable.
• Fixed an issue causing content forms to override cluster names in Pre-publish actions.
• Fixed an issue allowing revisions that did not have values in required fields to be saved and to be passed through a workflow. This resulted in a breaking change. See the "Breaking changes" section below.
• Fixed an issue preventing the proper preview of an image that was swapped in for another, then deleted, then restored.
• Fixed an issue causing saved search URLs to contain parameters for integrations and functionality even if a user's project did not include them.
• Fixed a Zookeeper vulnerability.
• Fixed an issue causing the improper exposure of links from the standard revision history view that was resulting in unexpected behaviors.
• Fixed an issue preventing the double-clicking of certain rich-text enhancements to open them.
• Fixed an issue causing multiple images that are selected and then dragged from The Shelf into a rich-text field to be pasted in a different order than they appeared when originally selected.

Breaking changes

• As a result of an issue that did not force validation of revisions when passed through a workflow, revisions will now undergo validation when passing through a workflow to ensure that no required fields are blank.

v4.5.28

v4.5.28 had one bug fix.

Bug fixes

• Corrected an issue throwing a Null Pointer Exception when using @DynamicFieldMethod with a DATE_STRING_TYPE field type, like LocalDate.

v4.5.27

v4.5.27 had one improvement and 21 bug fixes.

Improvements

• Made an improvement to increase security around generating cookie signatures.

Bug fixes

• Corrected an issue preventing UrlBuilder from failing to decode a valid query parameter.
• Corrected an issue causing some Spanish translations to be garbled.
• Updated Facebook oEmbed API to latest version.
• Corrected an issue causing dynamic notes to replace existing notes if the content was the same.
• Corrected an issue preventing the proper display of images when querying and trying to import from external AP Images libraries.
• Fixed a regression issue causing Editorial Content Type fields named id to throw an error.
• Two usages of JspUtils#getAbsoluteUrl were changed to use UrlBuilder.
• Fixed a UI padding issue related to the Audiences widget at the top of the content edit form.
• Corrected an issue causing a Null Pointer Exception in Board View when the user attempted to view abstract types in a Draft state.
• Improved security related to a jsoup library. This fix introduced a breaking change on the third-party's end. See "Breaking Changes" for more information.
• Corrected an issue preventing UrlBuilder from properly handling URL fragments.
• Fixed a UI issue causing module tab menus to be partially covered by an opened preview pane.
• Corrected the size and alignment of the Restore to Draft and Restore to Live buttons for archived assets.
• Corrected an issue throwing a Null Pointer Exception when attempting to swap the style of a module.
• Fixed an issue causing screen readers to describe toggle fields as checkboxes; now, they are described as switches.
• Fixed an issue causing Preview to Edit to not work properly in some cases.
• Fixed an issue causing abstract classes and interfaces marked with @Hidden(false) to not appear as a content type filter in search.
• Fixed a regression issue preventing some users from accessing Sites & Settings.
• Fixed an issue preventing a CMS UI popup initiated from the submission of a form from being reopened upon a resubmission.
• Fixed an issue showing duplicates of standard image sizes in the resized image popup.

Breaking changes

• Changes were made to remain current with jsoup; however, in doing so, library updates to whitespace handling may change textual content, like stripping spaces that were not previously stripped, vice versa, and other changes. Projects running versions that implement these changes (4.5.15.23, 4.5.27, 4.7.20, and 4.8.0) must address any potential issues surrounding this. The update is from 1.14.3 -> 1.17.3. See jsoup News and release notes for more information on how to resolve issues. Additional references can be found in jsoup’s Parser documentation and on their Issues repository.

v4.5.26

v4.5.26 had 10 improvements and 25 bug fixes.

Improvements

• Ping methods have been updated to reduce associated system loads. See "Breaking changes," below.
• URLs used for applying watermarks now use the AES/GCM/NoPadding mode of operation instead of the less secure AES/ECB.
• Improved view model and other front-end processing to enable developers to build custom modules using editorial content types.
• Upgraded Github runner for Antithesis, addressing the run-time error System.IO.IOException: No space left on device.
• Disabled external entity resolution in the SAML XML parser, thereby helping to prevent XML eXternal Entity (XXE) attacks.
• Replaced the class org.apache.commons.lang3.RandomStringUtils with org.apache.commons.text.RandomStringGenerator to more securely generate API keys.
• Replaced the class org.apache.commons.lang3.RandomStringUtils with org.apache.commons.text.RandomStringGenerator in the GraphQL explorer to more securely generate nonces.
• Replaced the function HMAC SHA-1 with HMAC SHA-256 to more securely generate a Tool User Time Based One Time Password.
• Improved performance of database initialization when instances of legacy types contain references to other objects.
• The HTTP response status code is now 500 for GraphQL schema load failures.

Bug fixes

• Corrected an issue that prevented publishing an asset's variation created using the Overlay All Fields option.

• Corrected an issue throwing a NullPointerException when attempting to delete an asset whose content type no longer exists.

• Corrected an issue preventing appearance of the focus indicator on images for sites configured without a theme.

• Corrected an issue allowing editors to move deleted elements within a list. For example, an article had a list of two authors. The editor deleted one of those authors by clicking . The editor was able to drag the deleted author to a different position in the list.

• Corrected an issue preventing proper rendering of the remove icon .

• Corrected an issue causing incorrect rendering of an asset in the preview pane, but correct rendering on the live front end.

• Corrected an issue causing the method JspUtils#getAbsoluteUrl to return an http URL when an https URL is available.

• Corrected an issue preventing proper rendering of an RSS feed when the corresponding section has a URL ending with a forward slash (such as /firstsection/).

• Corrected an issue preventing proper population of lists of objects. For example, when creating a role, the list of content types included entries other than content types.

• Corrected an issue preventing proper rendering of a post's history in an asset's Conversation widget.

• Corrected an issue preventing persistent disabling of the Crosslinker.

• Corrected an issue causing the content edit form to scroll to the bottom when creating a subsidiary asset, such as creating an assignment from a pitch.

• Corrected an issue preventing correct operation of the spell checker when track changes is toggled on.

• Corrected an issue preventing proper listing of assets in The Shelf when filtering by a role.

• Corrected an issue preventing proper interaction with the New Workstream widget. Specifically, if an editor opened New Workstream and clicked Save, the widget became blank instead of displaying a message to enter a required name.

• Corrected an issue preventing Brightspot from populating all <iframe> elements in the preview pane.

• Corrected an issue preventing population of The Shelf's source list when the asset in the content edit form did not include a typeId in its URL.

• Corrected an issue preventing synchronous updates of dynamic placeholder text on integer fields.

• Corrected an issue causing a parent asset's preview control to disappear and a NullPointerException message to be thrown when a child asset's content type is not available.

• Corrected an issue causing a certain combination of workflow and permissions to incorrectly give a user the publish permission.

• Corrected an issue throwing a NullPointerException when attempting to drag an asset from The Shelf onto the content edit form.

• Accessibility—

  • Added announcement for the name of date fields, such as Embargo Date.
  • Added announcements for the Expand All control as well as for successfully removing an item from a list.
  • Improved announcement of the more menu in the editorial toolbar.
  • Improved announcement of the word and character count in the rich-text editor.

Breaking changes

• The ping methods in dari.db.Database have changed to throw Exception instead of Throwable. Implementations should be updated to reflect this change.

v4.5.25

v4.5.25 had one improvement and 10 bug fixes.

Improvements

• The Shelf has been recoded to allow for more customizations.

Bug fixes

• Corrected an issue preventing proper operation of Brightspot when clicking Publish and then quickly opening another form such as Edit Global.
• Corrected an issue causing bookmarks in Microsoft Word documents to be imported as links instead of as plain text.
• Corrected an issue preventing proper pasting of rich text from Microsoft Word into the rich-text editor.
• Corrected an issue preventing proper rendering of assets in the preview pane when selecting a small device size.
• Corrected an issue causing the more icon to disappear after converting a module between shared and inline in the content edit form.
• Corrected an issue throwing a JavaScript error when clicking > Source Data in an image.
• Corrected an issue throwing a ClassCastException when attempting to copy a hotspot.
• Corrected an issue preventing a GraphQL CMA's detection of a content type when adding a StorageItem asset by URL.
• Corrected an issue causing a signature error when making calls to Amazon Translate.
• Accessibility—improved keyboard navigation and screen reader announcements pertaining to the rich-text editor's toolbar.

v4.5.24

v4.5.24 had one new feature, three improvements, and 17 bug fixes.

New features

• Expanded the ability to apply character-level formatting.

Improvements

• Brightspot no longer defaults to sending fields annotated with @ToolUi.Secret to translation services. Administrators must explicitly configure such fields for translation.
• Deployed a security update required by AP Images. For details, see Important API Security Updates.
• Added state information to logs for better diagnosis of replication cache failures.

Bug fixes

• Corrected an issue preventing expected rendering of the field option cms.ui.cluster.
• Corrected an issue preventing the display of a revision in the preview pane. Specifically, when an asset was rendered in the preview pane, and the editor clicked on the link to display a revision, the entire content edit form loaded with the revision except for the preview pane.
• Corrected an issue causing an extraneous character count to appear when selecting a user in the Conversation widget.
• Corrected an issue preventing the correct alignment of the , , , and icons that appear for child assets in the content edit form.
• Corrected an issue causing unexpected results after accepting deletions in text with tracked changes. For example, spaces in some positions were not deleted.
• Corrected an issue preventing the standard process when creating a new item while creating a shared list module. For example, an editor created a new shared list of people. As part of that process, the editor created a new person. After creating the new person, the editor clicked Back, and the editor did not return to the people list being created.
• Corrected an issue preventing the swapping of module types within a page. For example, an editor created a page and added three modules in the Contents field. Clicking to swap one of the modules for a different module threw a NullPointerException.
• Corrected an issue preventing proper display of the Title and Description fields in the content edit form's SEO tab.
• Corrected an issue preventing proper post-publish placement of an asset inside a parent asset's lists. For example, an editor created a homepage whose contents are a module. The editor then added a list List 1 to the module. The editor then copied List 1 to List 2. Next, the editor created an article, and in post-publish actions added the article to List 1. The article was also added to List 2.
• Corrected an issue causing text to scroll in the RTE when clicking on a button in the RTE toolbar.
• Corrected an issue allowing editors to close a nested module's rich-text editor without seeing a warning to save unsaved changes. Specifically, the warning was missing after pressing Escape.
• Corrected an issue preventing proper layout of the preview pane in Firefox.
• Corrected an issue preventing proper behavior of selection fields when one of the options is Is Missing.
• Corrected an issue generating different robots.txt rules for visitors to a URL with a www subdomain compared to a URL without a www subdomain.
• Corrected an issue preventing a favorite content type from behaving as expected in the content picker's Create field. For example, an editor selected User as a favorite content type. Next, the editor created an article, and in the Authors field selected Create New. In the content picker, in the Create field, User was not indicated as a favorite, and Author was.
• Corrected an issue preventing the disabled setting for Automatic Analytics JavaScript Injection at the Global level from cascading to the site level.
• Corrected an issue preventing proper rendering of a referenced asset in the preview pane. Specifically, when an asset is in the preview pane, and referenced assets are available from the View Reference list, the referenced asset did not appear correctly.

v4.5.23

v4.5.23 had four bug fixes.

Bug fixes

• Corrected an issue allowing an admin to restore a site without permission to do so.
• Corrected an issue throwing a Paths must be unique error even after deleting the duplicate path from an asset.
• Corrected an issue preventing setting permissions on content types for a copied role. For example, Adam added permissions for the Image content type to the role Reporters. He then copied the role Reporters to a new role Proofreaders. Next, he changed the Proofreaders permissions for the Image content type to Video and saved the role. The permissions for Video were not saved.
• Corrected an issue preventing the removal of images from a gallery.

v4.5.22

v4.5.22 had one improvement and seven bug fixes.

Improvements

• When Solr search data is not cached, Brightspot now searches only the default original database instead of traversing the entire database stack.

Bug fixes

• Corrected an issue causing a hyperlink in the rich-text editor to be applied to all selected characters except the last one.
• Corrected an issue preventing usage of editorial content types during CloudSQL maintenance.
• Corrected an issue causing the rich-text editor to accept changes beyond any text actually selected.
• Corrected an issue in which the StateWalker class was calling the deprecated RichTextElement.fromElement(Database db, Element element) method. The class now calls RichTextElement.fromElement(Recordable parent, Element element).
• Corrected an issue in which an impersonated editor became the active editor. For example, Adam impersonated Olivia. When Adam clicked Stop Impersonating, Olivia became the active editor instead of Adam.
• Corrected an issue preventing proper closure of the Bulk Workflow widget in the search panel.
• Corrected an issue preventing the method ToolUi#setHidden() from actually showing or hiding fields and clusters.

v4.5.21

v4.5.21 had three improvements and 27 bug fixes.

Improvements

• Added support for MySQL 8. See "Breaking changes," below.
• Improved keyboard navigation inside a reference field's list of assets. Specifically, after pressing the right arrow key to focus on the favorite icon , pressing the up/down, escape, and tab keys now have expected behaviors.
• Added the query parameter _callers to URLs to display levels in a stack trace. For example, with _callers=10, the profiler provides 10 levels of stack trace.

Bug fixes

• Corrected an issue preventing a border from appearing around the Recent Searches widget when tabbing through the search panel.

• Corrected an issue causing loss of context in the search panel after clicking . For example, clicking in the Users widget opens the search panel with filters applicable for users. Clicking removed those user-specific filters.

• Corrected an issue preventing expected operation of the annotation @Ignored(false).

• Corrected an issue causing incorrect layout of the preview pane.

• Corrected an issue preventing the typing of an HTML hex code in the color picker.

• Corrected an issue preventing editing text in the rich-text editor when entering full-screen mode with the preview pane open.

• Corrected an issue causing incorrect layout of the warning messages appearing under search fields in the left rail. For example, when selecting > Content Templates, if there are no content templates, the warning message No matching items was not laid out correctly.

• Corrected an issue throwing an error in The Shelf. Specifically, after saving a search for an external type (such as YouTube Video), opening The Shelf and selecting Recent Activity > Saved searches threw a NullPointerException.

• Corrected an issue disabling the Format menu when an X (formerly Twitter) post is embedded in the rich-text editor.

• Corrected an issue preventing population of the Suggestions widget when both annotations @ToolUi.Suggestions and @Where are present on a Set<E> field. See "Breaking changes," below.

• Corrected an issue throwing JavaScript errors when clicking to open the Edit Post widget in an asset's Conversation cluster.

• Corrected an issue causing cluster labels to display on two lines when a validation error occurs inside that cluster.

• Corrected an issue throwing a NullPointerException in The Shelf when one of The Shelf's labels are null.

• Corrected an issue causing user sessions to unexpectedly end.

• Corrected an issue preventing an asset's state to update if a Set field has dynamic placeholder text.

• Corrected an issue incorrectly assembling a URL after clicking to open a field's developer text.

• Corrected an issue in which an impersonated editor becomes the active editor. For example, Adam impersonates Olivia. When Adam clicks Stop Impersonating, Olivia is now the active editor instead of Adam.

• Accessibility

  • Ensured focus is applied to fields associated with the control. For example, when adding tags to an article, clicking ensures the focus moves to the newly opened field.
  • Ensured focus is applied to fields associated with the and Back controls. For example, in an article, clicking to edit a tag opens an Edit Tag form and applies focus to the Display Name field; clicking Back applies focus to the originating tag field.
  • Ensured focus is applied to a subsequent control after clicking . For example, in the search panel, clicking applies focus to the first item in the subsequent popup menu.
  • Ensured the order of screen reader announcements matches the visual layout of the content edit form.

• Corrected an issue causing the preview pane's width to equal the content edit form's width on initial load.

• Corrected an issue preventing preview-to-edit containers from rendering fields correctly when those fields do not have a valid preview.

• Corrected an issue causing a phrase in the search field that was surrounded in quotation marks to ignore all filters and return all assets. For example, searching for "cms workflow" returned all assets, not just those identifiable by the phrase cms workflow.

• Corrected an issue preventing updates to scheduled revisions from being saved. For example, an editor created a new revision of a homepage, and added a module to the contents. The editor then scheduled this revision. Subsequently, the editor removed a module from the scheduled homepage's contents, and scheduled this new revision. The removed module still appeared. See "Breaking changes," below.

• Corrected an issue that caused the method SegmentationDatabase#personalize to trigger a large number of extraneous reference resolves.

• Corrected an issue that did not account for the Zip Slip vulnerability. A security check now exists to detect and avoid this vulnerability.

• Corrected an issue preventing rCDA schema generation when a field's internal name has a prefix containing a dash. For example, a prefix declared as String PREFIX = "brightspot.custom-components." prevented schema generation.

Breaking changes

• The behavior for ToolUi#isEffectivelySuggestions has changed since it no longer automatically returns false if there is a field predicate present.

• Connections to MySQL 8 may not function with an existing dataset due to the following reasons:

  • Upgrading from MySQL 5.6 to 8 is not supported.
  • The UIDs between two images differ.
  • Passwords need to be updated to conform to MySQL 8's caching_sha2_password authentication plugin. See Caching SHA-2 Pluggable Authentication.

• In the class com.psddev.cms.db.Draft:

  • The method void update(Map, Object, Map, boolean) has been removed.
  • The method void update(Map, Object) is still available.

v4.5.20

v4.5.20 had 10 improvements, one new feature, and 28 bug fixes.

New features

• Hovering over an image in the preview pane now displays the image's crop name and size.

Improvements

• Embedded forms now have the same background shading in the header when the form is collapsed. Previously, when an embedded form was collapsed, the header lost the background shading.
• Improved accessibility and usability of the rich-text editor's find/replace toolbar.
• The internal precision of an asset's scheduled publication date has been reduced to minutes, reflecting what is visible in the date picker. (Previously the precision was stored at the selected date:hour:minute, and additional seconds and milliseconds were included based on the time the editor clicked Set in the date picker.)
• A setting is now available to ensure the Name field in the Name Revision widget is required.
• Updated Gradle to v8.6.
• Reduced build times in GitHub Actions.
• Refactored code to avoid false positives in Sonar checks.
• Upgraded Playwright to 1.41.2.
• In the Revisions widget, a clearer presentation is now available for revisions by audience.
• Improved performance of the References tab in the Content Type widget by implementing DataCache, thereby avoiding unnecessary Query and recursive reference lookups. See "Breaking changes," below.

Bug fixes

• Corrected an issue preventing display of a material icon in the Icon field of the New Content Type widget.

• Corrected an issue preventing proper update of default placeholder text. For example, a Byline field's default placeholder text is an asset's author. Deleting the author from the asset did not remove the author from the Byline field.

• Corrected an issue preventing display of workflow statuses in various selection fields (other than the standard statuses Draft, Published, Archived, and Revision).

• Corrected an issue causing incorrect sequencing as specified in the @ToolUi.FieldDisplayOrder annotations when that annotation is used in class T and also used in class Alternation<T>.

• Corrected an issue causing incorrect text display as specified in the @Recordable.DisplayName annotations when that annotation is used in class T and also used in class Alternation<T>.

• Corrected an issue causing incorrect application of recordable annotations to modified and target classes. For example, applying the @Recordable.Embedded annotation to Modification<T> embedded both class Modification<T> and class T in a parent class.

• Corrected an issue causing copied dashboards to display the original dashboard's headings. For example, Sue creates Dashboard A has a widget named Sue's Reports. Sue copied the dashboard to Dashboard B, and renamed the widget to Sam's reports. When using Dashboard B, the widget Sue's Reports remained.

• Corrected an issue preventing recently used modules from appearing in the module picker's Recently Used list.

• Corrected an issue preventing correct sorting of users in the Search Tool Users widget.

• Corrected an issue causing delays in rendering large tables in the rich-text editor.

• Corrected an issue preventing the closing of widgets when pressing Escape. This behavior occurred when a selection field (such as Any Content Type in the search panel) had focus.

• Corrected an issue allowing possibly excessive scopes in the Google Drive integration.

• Corrected an issue causing multiple selections to be cleared. For example, an editor selects two options in a selection field, and then types in the field to locate additional options. After typing in the field, the previous two selections are lost.

• Corrected an issue preventing bulk-uploaded images inside a parent asset from being published when the parent asset is published. For example, in a new article, an editor inserts a gallery in the rich-text editor, and bulk uploads several images into the gallery. Publishing the article did not simultaneously publish the uploaded images.

• Corrected an issue causing case-sensitive sorting of workflow statuses in the Workflow widget. For example, an editor creates an asset, and then opens the Workflow widget. The available statuses were sorted A–Z and then a–z.

• Corrected an issue causing the rich-text editor to mark correctly spelled words as incorrect, and incorrectly spelled words as correct.

• Corrected an issue causing clusters with only hidden fields to appear as expandable ( control) or collapsible ( control).

• Corrected an issue returning a Service Unavailable status when multiple editors are searching for assets through the search panel.

• Corrected an issue causing the React Developer Tools extension in Chrome to throw extraneous errors to the browser's console.

• Corrected an issue throwing a NullPointerException when selecting several assets in search results and then clicking to open the search actions menu.

• Accessibility

  • Added labels, descriptive text, and announcements to fields as required.
  • Corrected inconsistent field labels and screen announcements.
  • Improved keyboard accessibility and announcements for the image editor.
  • Added keyboard accessibility to the pagination controls and in the date picker.
  • Recast duplicate <h1> headings in various widgets and forms.

• Corrected an issue preventing an option from being marked as a favorite in drop-down lists.

• Corrected an issue causing delays of up to five minutes in cache replication.

• Corrected an issue preventing the method RtcEventUpdateNotifier#onChange from generating NullPointerException errors.

v4.5.19.1

v4.5.19.1 had one improvement and two bug fixes.

Improvements

• Improved performance of the References tab in the Content Type widget by implementing DataCache, thereby avoiding unnecessary Query and recursive reference lookups. See "Breaking changes," below.

Bug fixes

• Corrected an issue causing the method ByIdIterator#next to indefinitely return the same object.
• Corrected an issue causing delays of up to five minutes in cache replication.

Breaking changes

Subclasses of com.psddev.cms.type.Item need to implement ItemContainer to pick up any possible ReferenceField usages in the References tab.

v4.5.19

Note

v4.5.19 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.5.19 had two improvements and 19 bug fixes.

Improvements

• Editors now have two choices to manage the inheritance between a default variant and an audience variant.

  • For fields not changed in the audience variant, content from the default variant flows to the audience variant.
  • All fields in the audience variant are considered as changed, so no content flows from the default to the audience variant.

• Improved the visibility of links (outside of mouse hover) by replacing the dotted underline with a solid underline.

Bug fixes

• Corrected an issue preventing display of the Styles tab in an editorial content type's content edit form.

• Corrected an issue causing an extraneous underline to appear under tab names.

• Corrected an issue preventing proper display of list modules in the preview pane.

• Corrected an issue in which mergeNonSamlUser was not included in the SAML configuration.

• Corrected an issue in which selections in lists were not reset after applying a filter. (The current selection remained even if it did not satisfy a filter.)

• Corrected an issue causing improper alignment of an image's quick view icon in the search panel.

• Corrected an issue preventing preservation of an original Solr query's options to a MySQL database.

• Corrected an issue causing undefined to appear in a tool tip when hovering over bulk schedule items.

• Corrected an issue preventing proper layout of modules in the preview pane.

• Corrected an issue preventing expected manual numbering of paragraphs in a numbered list in the rich-text editor.

• Corrected an issue causing the method TranslationUtils#entryToTranslationValue to throw a NullPointerException.

• Corrected an issue preventing a translation job from terminating when the job itself does not complete.

• Corrected an issue preventing nested enhancements inside rich-text enhancements.

• Corrected an issue preventing activation of the controls (preview size, reference) in the preview pane when previewing a live blog post.

• Corrected an issue preventing values in a color picker from being saved with an image search. For example, when searching for an image, an editor specifies the color #f70000. When saving that search search, the color #f70000 was not preserved.

• Corrected an issue preventing application of themes to topics in books.

• Corrected an issue preventing correct selection of a content form when that content form is associated with a user itself associated with a site-specific role. For example, the content edit form Recipe is derived from Article and associated with the role Editor. Adam Braun is an Editor. In this scenario, when Adam Braun started a new asset based on Article, the default Article content edit form appeared instead of Recipe.

• Corrected an issue throwing a NullPointerException when attempting to configure post-publish actions for an asset. For example, Section A has an empty list for both lead and content, Article B is assigned to Section A, and post-publish actions are enabled. Clicking Publish threw a NullPointerException.

• Accessibility:

  • In various grouped lists, the group headings are no longer announced as one of the available selections. For example in the Create list, the headings Main Content Types and Misc Content Types are no longer announced as selectable.

The following release candidates are also part of this release.

v4.5.19-rc.2023.12.21

v4.5.19-rc.2023.12.21 had five bug fixes.

Bug fixes

• Corrected an issue preventing the preview pane from entirely loading an asset.

• Corrected an issue preventing update of the slider in the Columns field of the Dashboard widget. After deleting a column in the Dashboard widget, the slider did not immediately update. This defect has been resolved.

• Corrected an issue causing images added to a gallery from The Shelf to have an incorrect preview size.

• Corrected an issue causing incomplete conversion of double quotes to smart quotes in text containing characters outside of Basic Latin (such as ó).

• Accessibility:

  • Added announcements to various menus, such as search results menu and saved searches.

v4.5.19-rc.2023.12.13

v4.5.19-rc.2023.12.13 had 27 bug fixes and 10 improvements.

Improvements

• Improved readability of error message when access to Google Drive was revoked.
• A new References tab indicates where an editorial content type (ECT) is referenced in a parent ECT. In addition, a warning message is displayed when attempting to delete an ECT referred by a parent ECT.
• Added ability to swap between shared and inline modules within the rich-text editor.
• Improved granularity of revision comparison for embedded content. Within a side-by-side comparison, clicking on a module's information icon lists the changes within the module between the two revisions.
• Added an id element to CDA image map elements to enable default caching and streamlined testing.
• Improved the search panel's taxonomy view to better accommodate long tag names.
• Added a field Map metaData to the class ImageTransformBuilder to more easily pass image metadata between objects.
• Added accessibility guidelines to the Brightspot repository's README.
• Enhanced documentation for integrating Brightspot with Microsoft Teams.
• Changed the class name of a <div> element to better control tab order.

Bug fixes

• Corrected an issue causing new assets to be saved in MySQL but not in Solr.

• Corrected an issue causing delays of up to five minutes in cache replication.

• Corrected an issue preventing updates to a field type from appearing in the associated production guide. For example, for the content type Article, an administrator changes a field Body from rich text to list. The type change was not reflected in the production guide for Article.

• Corrected an issue allowing editors to inadvertently add multiple tables in the rich-text editor.

• Corrected an issue causing focus to move to the Sort field in the search panel when typing in the search field.

• Corrected an issue causing the production guide to obscure the rich-text editor in full-screen mode.

• Corrected an issue preventing the preview pane from entirely loading an asset.

• Corrected an issue causing an extraneous underline to appear under tab names.

• Corrected an issue causing an extraneous underline to appear in the Conversation widget's reply icon .

• Corrected an issue preventing a scheduled asset from appearing in the Revisions widget after the scheduled date passed and the asset was published.

• Corrected an issue preventing changes to text fields from appearing in compare-to-live. Specifically, if an update to a text field started with a new paragraph, the change did not appear in the comparison.

• Corrected an issue preventing proper selection of a workflow when multiple workflows are available for a content type.

• Corrected an issue causing improper alignment of The Shelf's quick view icon .

• Corrected an issue causing incorrect display of a basic list after dragging an asset onto the list from The Shelf.

• Corrected an issue preventing tabbing between fields after clicking in the Saved Searches widget.

• 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 focal point assigned to an image group. For example, a focal point (x, y) was assigned to the Square image group, but Brightspot did not apply that focal point to individual images within that group.

• Accessibility

  • Added indication to screen readers that the Content Types field in the New Workflow widget allows multiple selections.
  • Fixed incorrect announcements of icons and controls.
  • Focus now moves to the navigation menu when it is opened; modified the position of the menu within the underlying HTML to improve sequence of announcements and tabbing.
  • Suppressed announcements for the analytics chart's axis when there is no suitable context to include with the announcement.
  • Improved accessibility of field-level error messages.
  • In the content edit form, reading order is from top-to-bottom, left-to-right and matches the page layout.
  • In the search panel, reading order is from top-to-bottom, left-to-right and matches the page layout.
  • In the Users and Roles page, reading order is from top-to-bottom, left-to-right and matches the page layout.
  • The Name field in the New Workstream widget has a static Required label and has a required attribute detectable by screen readers.
  • Corrected ARIA attributes in the CMS header.

v4.5.19-rc.2023.10.31

v4.5.19-rc.2023.10.31 had 21 bug fixes and two improvements.

Improvements

• A new toggle in the New/Edit Workflow widget can make comments mandatory when transitioning an asset from one status to another.
• The placeholder text in the workflow widget was changed from Optional Workflow Comment to Add Comment.

Bug fixes

• Corrected an issue causing selection of the Is Missing filter value via the keyboard to forget values in sticky search.

• Corrected an issue throwing a NullPointerException in the Users & Roles widget.

• Corrected an issue causing incorrect back-end rendering of a promo's lead image when that image is in .svg format.

• Corrected an issue preventing display of the Styles tab in an editorial content type's content edit form.

• Corrected an issue preventing cancellation of an asset's scheduled status after the corresponding schedule is deleted.

• Corrected an issue preventing addition of a Favorites section in the search panel's content types list. For example, an editor opens the search panel, expands the content types list, and clicks on for the Video content type. The next time the editor opens the content types list, there is no Favorites section containing the Video content type. This is now fixed.

• Corrected an issue causing the dynamic placeholder text in a required embedded content type to appear in one of its child fields.

• Corrected an issue causing improper placement of a field's current character count.

• Corrected an issue preventing display of the headings Hidden Fields and Selected Fields in the Show/Hide Fields widget.

• Corrected an issue causing the method Query.groupBy("l10n.locale") to return incorrect results.

• Corrected an issue preventing the publication of an asset in draft status that was scheduled; when the scheduled date arrived, the asset was not published.

• Accessibility:

  • Mitigated use of repeated <h1> elements in various widgets.
  • Mitigated use of repeated <h1> elements in Workflow widget.
  • Mitigated use of repeated <h1> elements in Users & Roles widget.
  • Mitigated use of repeated <h1> elements in the following widgets: Select Fields, Save Search, Bulk Archive confirmation, Conversation, Edit Post, Notifications, and Name Revision.
  • Corrected overlap of the settings and reset icons in the search panel.
  • Improved focus contrast in the Unpublished Draft widget's column headings.
  • Added Role and Accessible label to the Advanced Query and New Workstream widgets.
  • Suppressed announcements by screen readers of decorative UI icons.
  • Modified markup so background elements in several widgets are no longer announced by screen readers.
  • For text fields with maximal character counts, screen readers now announce the current character count and the maximal allowed.

v4.5.19-rc.2023.10.13

v4.5.19-rc.2023.10.13 had 10 bug fixes.

Bug fixes

• Corrected an issue causing the dynamic placeholder text in a required embedded content type to appear in one of its child fields.

• Corrected an issue that prevented the correct initialization of values in the content edit form, such as when changing a list from advanced to dynamic.

• Corrected an issue preventing display of the headings Hidden Fields and Selected Fields in the Show/Hide Fields widget.

• Corrected an issue causing the method Query.groupBy("l10n.locale") to return incorrect results.

• Corrected an issue preventing the publication of an asset in draft status that was scheduled; when the scheduled date arrived, the asset was not published.

• Corrected an issue causing the ingestion of Google Analytics 4 to fail.

• Corrected an issue throwing a NullPointerException error when attempting to log in.

• Accessibility:

  • Modified markup so background elements in several widgets are no longer announced by screen readers.
  • For text fields with maximal character counts, screen readers now announce the current character count and the maximal allowed.
  • Suppressed announcements by screen readers of decorative UI icons.

v4.5.19-rc.2023.9.28

v4.5.19-rc.2023.9.28 had 12 bug fixes and one improvement.

Improvements

• Customers can now secure webhook endpoints using HMAC-SHA256 encryption.

Bug fixes

• Restored the For Developers tab in an asset's Tools widget for users with the default Full Access role. See "Breaking changes," below.

• Corrected an issue causing the count of references displayed in the References widget to be different from the number of references in the corresponding search panel. For example, the link in the References widget was View All 102 References. Clicking on the link displayed, by default, a search panel with only 100 references.

• Corrected an issue throwing a MalformedURLException error when attempting to access a GraphQL endpoint.

• Corrected an issue displaying the Quick Start widget as Create New Widget in production guides.

• Corrected an issue throwing an Unable to format date! message when importing assets from Getty Images.

• Accessibility:

  • Pressing the tab key now displays a Skip To Content control that, upon click, advances focus to the primary section of the current page. For example, clicking Skip to Content in the content edit form advances focus to the widgets in the right rail.
  • Visual headings in the search panel's board view are now correctly marked up as headings.
  • Visual lists in the search panel's board view are now correctly marked up as lists.
  • Visual heading in an asset's workflow widget is now correctly marked up as a heading; visual heading in an asset's Compare to Live widget is now correctly marked up as a heading.
  • Corrected improper nested-heading markup for the search panel's Clear control.
  • Changed login page's <title> tag from Dashboard | CMS | Brightspot to Login | CMS | Brightspot.
  • Modified markup so background elements in several widgets are no longer announced by screen readers.

Breaking changes

• Projects may not not want to expose the Developer tab in an asset's Tools widget for the default role. In such cases, update missingRolePermissions to include -developer/info (or -developer/ to exclude all developer features from the default role).

v4.5.19-rc.2023.9.18

v4.5.19-rc.2023.9.18 had 21 bug fixes and one improvement.

Improvements

• Developers can now limit and customize the selection criteria for assets appearing in The Shelf.

Bug fixes

• Corrected an issue causing poor performance in the preview pane when the asset has a large number of modules.

• Corrected an issue preventing population of the Schedule Date column in the search panel.

• Corrected an issue causing an image enhancement's tool bar from obscuring an enhancement inside a table.

• Corrected an issue throwing an error TypeError: Cannot read properties of undefined when creating a new section by clicking Create New in a Section reference field.

• Corrected an issue throwing an error NullPointerException after clicking a schedule in the Available Schedules widget.

• Corrected an issue exposing an XSS vulnerability for text fields.

• Corrected an issue preventing successful upload of a new image when Brightspot is running on an AWS server.

• Accessibility:

  • Added focus indicator to several controls, such as the Generate Permalink checkbox.
  • Improved programmatic announcement for the more control in the content edit form's header.
  • Added programmatic announcement to the checkboxes in the search panel; added announcement to the slider in the search panel.
  • Added programmatic announcement to the drag indicators in the Show/Hide fields widget.
  • Added programmatic announcement to the New Workflow control in the Workflows widget.
  • Ensured focus indicator remains in the search panel after clicking Clear.
  • Added announcement after transitioning an asset from one status to another in a workflow.
  • Added programmatic announcement to reference fields in the Advanced Query Builder and New Workstream widgets.
  • Improved visual link indicator on the Brightspot graphic in the login page.
  • Ensured focus indicator remains after clicking or a field name in Selected Fields column in the Show/Hide fields widget.
  • Removed the unresponsive help control in the login page.
  • Prevented focus from leaving the field after selecting a content type in the search panel's global filters.
  • Ensured focus indicator remains after making a selection in the search panel's Sort and Show filters.
  • Improved contrast between the production guide icon and its background during mouse hover.

v4.5.19-rc.202308

v4.5.19-rc.202308 had 28 bug fixes, five improvements, and one new feature.

New features

• Production guides are now available for all widgets on the content edit page.

Improvements

• The Revisions widget now displays the history for revisions. For example, if an article's revision is in a workflow, the Revisions widget now lists all of the revision's transitions—and all transitions for all other revisions.
• The core graphql module no longer depends on the analytics module.
• Editors can now select multiple levels of referenced assets to send for translation. For example, an asset is sent for translation, and that asset is referenced by a child section, which in turn is referenced by a parent section. Editors can send both the child section and parent section for translation.
• Added README documentation to the OneLogin authentication module.
• Added a front-end accessibility function announce that developers can call to announce run-time changes in the UI, such as changes in search results.

Bug fixes

• Corrected an issue that prevented the annotation @ToolUi.Unlabeled from working on embedded types outside of the rich-text editor. For example, if the field NestedBody was annotated with @ToolUi.Unlabeled, and another field had an @Embedded list of List<NestedBody>, the label appeared in the content edit form.

• Deprecated ToolPageContext#writeQueryRestrictionForm (which created two web forms) in favor of ToolPageContext#writeQueryRestriction.

• Corrected an issue that unnecessarily generated asset previews even when the preview pane was never opened.

• Corrected vulnerabilities detected by the OWASP dependency checker.

• Corrected an issue that prevented display of the close icon in The Shelf.

• Corrected an issue that prevented @Visibility(index) from working in AbstractSearchPageServlet classes with multiple content types.

• Corrected an issue preventing the correct display of the Conversation widget in custom forms.

• Corrected an issue causing the preview pane to overlap a rich-text editor enhancement's edit widget. For example, when editing a hyperlink in the rich-text editor, the Edit Link widget was layered under the preview pane.

• Corrected an issue preventing the text of a pinned reply in the Conversation widget from appearing in the list of pinned replies. For example, an editor replies to a conversation I agree, and then pins that reply. The text I agree did not appear in the list of pinned replies.

• Corrected an issue that prevented the first field in a new content edit from from receiving focus.

• Corrected an issue causing incorrect spacing of results in the search panel.

• Corrected an issue preventing display of the headings Hidden Fields and Selected Fields in the Show/Hide Fields widget.

• Accessibility:

  • Added descriptive text to uninitialized fields in the content edit page.

  • Added announcement for the New Workflow control in the Workflows widget.

  • Added keyboard accessibility to the drag-and-drop controls.

  • Added keyboard accessibility to content type-specific filters in the search panel and to controls in the Saved Searches widget.

  • Added informative announcement to the Brightspot link in the login page.

  • Added programmatic context to the preview pane.

  • Added accessibility attributes for links in search results pagination.

  • Added dynamic announcement for the New button in the Create widget.

  • Added announcements for the Hidden Fields and Selected Fields in the Show/Hide Fields widget.

  • Added announcement to the search panel for the following events:

    • Search results changed
    • No search results found

  • Improved visual indication that sliders are in focus (such as the slider in the search panel that increases/decreases thumbnail sizes).

  • Disambiguated the link text associated with the and controls in the Edit Workstream widget.

• Corrected an issue in which methods in the class HandlebarsTemplateRenderer created repeated objects that caused heap exhaustion.

• Corrected an issue causing the incorrect or confusing display of a comparison between revisions.

• Corrected an issue causing preview-to-edit field frames to overlap.

• Corrected an issue causing performance degradation due to creation of unnecessary timers for SAML X.509 sessions.

v4.5.18.1

v4.5.18.1 had one bug fix and one improvement.

Improvements

• The Revisions widget now displays the history for revisions. For example, if an article's revision is in a workflow, the Revisions widget now lists all of the revision's transitions (and all transitions for all other revisions).

Bug fixes

• Corrected an issue causing the incorrect or confusing display of a comparison between revisions.

v4.5.18

v4.5.18 had 33 bug fixes, two improvements, and one new feature.

New features

• The Authorship widget pulls its data from Google Analytics 4.

Improvements

• The search panel's board view now has an Is Missing column. When grouping found assets by a field (such as Section), those assets without an assigned section appear in their own column. Editors can set the missing section by dragging the assets to the appropriate column.
• Added a screen-reader-only class for styling elements that are visually hidden but spoken by assistive technologies.

Bug fixes

• Accessibility:

  • Improved presentation of chart axes to screen readers, and added an outline to any element with focus.
  • Added keyboard accessibility to workflow creation.
  • Added announcements for various toggles.
  • Removed announcements for elements that are hidden from the visible screen.
  • When selecting > Workflows, focus no longer jumps to the New Workflow > Name field.
  • Added keyboard accessibility to workflow controls (Workflow , Publish Override, more icon in Revisions widget).
  • Added keyboard accessibility to the controls in a workflow's Actions widget (such as Add Status and Add Transition).
  • Added focus to fields after clicking the controls Publish Override, Back to Workflow, Compare to Live, and Back (when comparing revisions).
  • Added focus to fields after clicking the controls Post, Save, and Delete Permanently in the Conversation and Edit Post widgets. Modified Conversation widget so that it updates after editing or deleting a post/reply.
  • Added alt text to images and icons in the Revisions and Conversation widgets.
  • Added indication to screen readers that the Content Types field in the New Workflow widget allows multiple selections.
  • Added keyboard accessibility to controls in the search panel.

• Corrected an issue that caused the settings icon to appear over the close icon in the Edit Post widget.

• Corrected an issue that caused the expand all icon to appear over the reset weights icon in the Edit Dashboard widget.

• Corrected an issue that threw a NullPointerException error when adding the Lead field to search results, and when that field has a one-off image.

• Corrected an issue displaying an extraneous before error messages.

• Corrected an issue indicating changes between an asset's revisions when no such changes were made.

• Corrected an issue in which CMA mutations did not validate the passed ID against the type being modified or deleted in the request. For example, a CMA request wants to delete an article, but the passed ID refers to a page.

• Corrected an issue that caused ValidObjectFieldTypesTest to fail when attempting to save objects of type SearchResultView.

• Corrected an issue throwing an error Invalid advanced query: Can't query [null] using [status]! in the search panel when filtering by assignment and any status in board view.

• Corrected an issue causing one of the close icons in the Edit Post widget to appear in a shade of white.

• Corrected an issue causing incorrect comparison markup when creating a scheduled replacement revision. For example, an editor opens an existing article and creates a new revision. The new revision is scheduled to replace the existing one. The editor then creates a new revision from the scheduled one. The comparison between the two revisions was incorrect.

• Corrected an issue preventing updates to fields across revisions. For example, an editor opens an existing article and creates a new revision. The editor then creates a new revision from the existing one. Changes to the live version were not carried into the second revision.

• Corrected an issue causing the move icon to appear outside the associated list.

• Corrected an issue causing extraneous spaces in the HTML representation of a rich-text object. For example, a tag appeared as <ul class="something"> (two spaces after the ul).

• Corrected an issue causing names in the Watchers widget to appear in a separate list.

• Corrected an issue preventing Brightspot icons from appearing correctly in Safari.

• Corrected an issue preventing display of AWS Comprehend suggestions.

• Corrected an issue causing degraded performance during cache replication.

• Corrected an issue allowing a user to see a dashboard without appropriate permissions. Specifically, User A is assigned to a role that excludes the dashboard. When User B impersonates User A, User B sees the dashboard.

• Corrected an issue preventing editors from clicking and editing nested rich-text fields inside preview-to-edit.

• Corrected an issue causing an error when replacing a scheduled draft with a subsequent scheduled draft.

• Corrected an issue causing the browser tab to slow or freeze when attempting to edit a field.

v4.5.17.2

v4.5.17.2 had two bug fixes.

Bug fixes

• Corrected an issue causing the browser tab to become slow or freeze when attempting to edit a field.
• Corrected an issue causing preview-to-edit field frames to overlap.

v4.5.17.1

v4.5.17.1 had one improvement.

Improvements

• Saved searches now preserve the Group selection for board view and the zoom setting for grid view.

v4.5.17

v4.5.17 had 30 bug fixes and 12 improvements.

Improvements

• Preview-to-edit of an asset now allows editing of embedded or shared children assets.
• Deployed more intuitive field labels for the schedule builder.
• Expanded processing of <ol> and <ul> tags in the rich-text editor to accommodate export to XML format.
• Because editors write their production guides in the Guide widget, the For Editors tab no longer appears in field-level help. The question mark indicating field-level help is available appears only when the current user has developer-level permissions.
• Saved searches now preserve the Group selection for board view and the zoom setting for grid view.
• Moved the Embedded field from the Developer tab to the Main tab in the Content Type widget.
• Preview-to-edit is now streamlined for many levels of nested assets. Fields in the preview pane have multiple distinctive borders corresponding to levels of nesting. Modifying nested assets involves fewer mouse clicks.
• Editors can now drag assets from The Shelf into single-value fields such as Lead and Section.
• Added a cron expression builder to the Google Analytics 4 integration.
• Plyr and Crosslinker now retrieve associated resources directly from the configured content delivery network (CDN) instead of via Brightspot.
• After a transient and recoverable database error, Brightspot now attempts to re-connect and read API calls.
• Improved the performance of the method ViewMap#getViewClasses. This improvement will reduce the time to render assets on the front end.

Bug fixes

• Corrected an issue that caused text in the Unpublished Drafts widget to overflow cell borders on Safari.

• Corrected an issue that caused incorrect placement of the icon for resetting dashboard column widths.

• Corrected an issue that caused some fields in the content edit form to appear in more than one place in preview-to-edit.

• Corrected an issue that caused lost text when merging table cells.

• Corrected an issue that prevented strikethrough formatting from appearing in a content edit form's list items. For example, when adding a tag to an asset, and then deleting the tag, the strikethrough did not appear in the deleted tag's label.

• Corrected an issue throwing a ValidationException error when viewing a new image in The Shelf.

• Corrected an issue that prevented appropriate initialization of values in the content edit form, such as when changing a list from advanced to dynamic.

• Corrected an issue that prevented update of an asset's path over GraphQL CMA when the asset was created through an editorial content type.

• Corrected an issue causing deletion of a scheduled revision when the option is to replace (instead of merge with) the live version.

• Corrected an issue causing inconsistent formatting of editable fields in preview-to-edit. For example, when loading the preview pane, all the editable fields had a border, but clicking inside one of those fields caused borders around the other fields to disappear.

• Corrected an issue that prevented unscheduling an asset's variation that was scheduled for a specific audience.

• Corrected an issue that displayed Update Existing Schedule for an asset even after the asset was unscheduled.

• Accessibility:

  • Corrected an issue preventing some controls from conveying to screen readers required information, such as role, state, or name.
  • Corrected an issue preventing screen readers from detecting messages or status updates, such as error messages associated with fields.
  • Corrected an issue causing screen readers to incorrectly announce icons or controls.
  • Corrected an issue rendering a content edit form's tabs without semantic or programmatic structure.
  • Corrected an issue preventing the navigation menu from receiving focus when opened; improved keyboard accessibility with the navigation menu.
  • Corrected an issue in which some controls had hover-only accessibility and no keyboard accessibility.
  • Corrected an issue preventing a focus indicator from appearing on various controls in the content edit page.
  • Corrected an issue in which a content edit form's clusters were rendered without semantic or programmatic structure.
  • Corrected an issue preventing an announcement when the content edit form's more icon changes to a close icon .
  • Corrected an issue preventing an announcement when an editor creates a new workstream.
  • Corrected an issue preventing an announcement when an editor adds a post to a conversation and that post mentions another editor.

• Corrected an issue preventing a scheduled asset's variations from being published. For example, if an asset had a variation for a particular audience, the audience's variation was not published on the scheduled date.

• Corrected an issue in which an asset's unpublished revision did not retain changes previously initiated by an editor.

• Corrected an issue that threw a java.lang.NullPointerException error when uploading images through the Upload widget.

• Corrected an issue causing NullPointerException errors when ingesting rich text from an external source, such as a Google Doc.

• Corrected an issue preventing the update of a preview when placing an image in The Shelf onto the content edit form.

• Corrected an issue causing an audience selector to appear in the editorial toolbar when an asset is in a workflow and before the asset is published.

• Corrected an issue causing the workflow status to appear as a UUID instead of its actual name.

v4.5.16.1

v4.5.16.1 had three bug fixes.

Bug fixes

• Corrected an issue preventing some controls from conveying to screen readers some required information, such as role, state, or name.
• Corrected an issue in which some controls had hover-only accessibility and no keyboard accessibility.

v4.5.16

v4.5.16 had 11 bug fixes, one new feature, and 8 improvements.

New features

• Deployed a MarkedText TypeScript library. Developers can use this library to pass and parse marks in text sent between Brightspot and GraphQL.

Improvements

• The module picker now has a search field for quickly finding a specific module or style.
• Improved the Compare To Live feature, presenting a cleaner, more rich-text-focused comparison between revisions.
• For editorial content types, introduced permissions on widget tabs and fields intended for developers.
• Improved accessibility in the CMS.
• Implemented Google Analytics 4 for reporting at the site, search, and asset levels.
• Improved visual comparison of two revisions by suppressing HTML tags.
• Enhancements now appear in the comparison of two revisions. For example, if Revision A has an image, and Revision B modified that image, the different images appear in the comparison.

Bug fixes

• Fixed scrolling in the Add widget for adding a module.
• Corrected an issue in which, if a workstream has some assets that are published and others that are skipped, clicking Skip continued past the last asset, displayed a blank content edit form, and displayed an incorrect sequence number.
• Corrected an issue that prevented the preview pane's height from being set correctly.
• Corrected an issue causing incorrect display of editorial content types. For example, an editorial content type ECT1 had a cluster, row, or tab, and any one of them had an embedded Boolean field. Subsequently, an editorial content type ECT2 had a cluster, row, or tab, and any one of them had an embedded text field. Opening the content edit form for ECT1 showed an embedded text field instead of an embedded Boolean field.
• Corrected an issue that disabled scrolling in the preview pane after updating text in the associated content edit form.
• Corrected an issue that allowed editors to circumvent permissions on the Module content type.
• Corrected an issue that caused The Shelf to display native-size images instead of their thumbnails.
• Corrected an issue that prevented new fields from being included in custom content forms. In particular, the Hidden Items widget in Edit Content Form did not include the new field, so admins could not add it to existing content forms. For example, a developer added a new field Eyebrow to the standard content type Article. Admins had no way of adding Eyebrow to custom content forms based on Article.
• Corrected an issue that caused the preview pane to scroll to the top after making a change in the associated content edit form.
• Corrected an issue that caused long delays in rendering The Shelf for a given asset.
• Corrected an issue that caused unit tests involving WebRequest objects to fail.

v4.5.15.24

v4.5.15.24 had one improvement and four bug fixes.

Improvements

• Made changes to keep Brightspot compatible with Lingotek as a result of a recent authentication mechanism change.

Bug fixes

• Fixed an issue causing cms.ui.cluster to not work properly when creating sets of front-end fields.
• Fixed an issue preventing changes to data that was relocated from one module type to another to persist after the first save action. Now, changes persist after the first save action after data is relocated from one module type to another.
• Fixed an issue where saved search URLs contain irrelevant parameters.
• Upgraded certain dependencies to a new version of Zookeeper to eliminate an earlier version's vulnerability.

v4.5.15.23

v4.5.15.23 had nine improvements and 16 bug fixes.

Improvements

• Improved the security of image watermarking URL.
• Replaced *:* queries with ping&df=data. As a result, this change updates the query in dari/db/DefaultDatabasePing to a ping&df=data query. This correction introduced a breaking change described below.
• Made an adjustment to the SAML XML parser to prevent XML eXternal Entity (XXE) attacks.
• Made an improvement to increase security around generating API keys.
• Made an improvement to increase security around API requests.
• Made an improvement to increase security around creating new tool users and their passwords.
• Made an improvement to increase security around generating cookie signatures.
• Improved the speed of the database environment initialization process when stored legacy types contain references.
• Ensured that responses for GraphQL endpoints with a failed schema return the proper 500 error code.

Bug fixes

• Corrected an issue preventing UrlBuilder from failing to decode a valid query parameter.
• Corrected an issue preventing the use of a header that returned an http site URL instead of a https site URL.
• Changed two usages of JspUtils#getAbsoluteUrl so that they use UrlBuilder.
• Corrected an issue causing an NPE in Board View when the user attempted to view abstract types in a Draft state.
• Improved security related to a jsoup library. This change introduced a breaking change on the third-party's end. See "Breaking Changes" for more information.
• Corrected an issue causing an RSS feed filter to not resolve feed sources if ending in a trailing slash.
• Corrected an issue preventing UrlBuilder from properly handling URL fragments.
• Corrected an issue causing some Spanish translations to be garbled.
• Updated Facebook oEmbed API to latest version.
• Corrected an issue enabling a user without permissions to Publish or Publish Override to be able to do so.
• Corrected an issue causing the Publish Override option to be available instead of the Publish option.
• Fixed a regression issue preventing some users from accessing Sites & Settings.
• Corrected an issue causing dynamic notes to replace existing notes if the content was the same.
• Corrected an issue preventing the proper display of images when querying and trying to import from external AP Images libraries.
• Fixed a regression issue causing Editorial Content Type fields named id to throw an error.

Breaking changes

• ping APIs have changed to throw Exception instead of Throwable. Implementations should be changed to reflect this.
• Changes were made to remain current with jsoup; however, in doing so, library updates to whitespace handling may change textual content, like stripping spaces that were not previously stripped, vice versa, and other changes. Projects running versions that implement these changes (4.5.15.23, 4.5.27, 4.7.20, and 4.8.0) must address any potential issues surrounding this. The update is from 1.14.3 -> 1.17.3. See jsoup News and release notes for more information on how to resolve issues. Additional references can be found in jsoup’s Parser documentation and on their Issues repository.

v4.5.15.22

v4.5.15.22 had five bug fixes.

Bug fixes

• Corrected an issue preventing proper interaction with the New Workstream widget. Specifically, if an editor opened New Workstream and clicked Save, the widget became blank instead of displaying a message to enter a required name.
• Corrected an issue preventing proper rendering of assets in the preview pane when selecting a small device size.
• Corrected an issue causing the content edit form to scroll to the bottom when creating a subsidiary asset, such as creating an assignment from a pitch.
• Corrected an issue preventing a GraphQL CMA's detection of a content type when adding a StorageItem asset by URL.
• Corrected an issue causing a signature error when making calls to Amazon Translate.

v4.5.15.21

v4.5.15.21 had three improvements and 18 bug fixes.

Improvements

• Added state information to logs for better diagnosis of cache replication failures.
• When Solr search data is not cached, Brightspot now searches only the default original database instead of traversing the entire database stack.
• Deployed a security update required by AP Images. For details, see Important API Security Updates.

Bug fixes

• Corrected an issue causing unexpected results after accepting deletions in text with tracked changes. For example, spaces in some positions were not deleted.
• Corrected an issue preventing the standard process when creating a new item while creating a shared list module. For example, an editor created a new shared list of people. As part of that process, the editor created a new person. After creating the new person, the editor clicked Back, and the editor did not return to the people list being created.
• Corrected an issue preventing the swapping of module types within a page. For example, an editor created a page and added three modules in the Contents field. Clicking to swap one of the modules for a different module threw a NullPointerException.
• Corrected an issue preventing proper display of the Title and Description fields in the content edit form's SEO tab.
• Corrected an issue causing text to scroll in the RTE when clicking on a button in the RTE toolbar.
• Corrected an issue preventing proper layout of the preview pane in Firefox.
• Corrected an issue preventing proper behavior of selection fields when one of the options is Is Missing.
• Corrected an issue preventing a favorite content type from behaving as expected in the content picker's Create field. For example, an editor selected User as a favorite content type. Next, the editor created an article, and in the Authors field selected Create New. In the content picker, in the Create field, User was not indicated as a favorite, and Author was.
• Corrected an issue preventing the disabled setting for Automatic Analytics JavaScript Injection at the Global level from cascading to the site level.
• Corrected an issue preventing proper rendering of a referenced asset in the preview pane. Specifically, when an asset is in the preview pane, and referenced assets are available from the View Reference list, the referenced asset did not appear correctly.
• Corrected an issue allowing editors to close a nested module's rich-text editor without seeing a warning to save unsaved changes. Specifically, the warning was missing after pressing Escape.
• Corrected an issue causing a hyperlink in the rich-text editor to be applied to all selected characters except the last one.
• Corrected an issue generating different robots.txt rules for visitors to a URL with a www subdomain compared to a URL without a www subdomain.
• Corrected an issue allowing an admin to restore a site without permission to do so.
• Corrected an issue throwing a Paths must be unique error even after deleting the duplicate path from an asset.
• Corrected an issue causing the rich-text editor to accept changes beyond any text actually selected.
• Corrected an issue in which the StateWalker class was calling the deprecated RichTextElement.fromElement(Database db, Element element) method. The class now calls RichTextElement.fromElement(Recordable parent, Element element).
• Corrected an issue in which an impersonated editor became the active editor. For example, Adam impersonated Olivia. When Adam clicked Stop Impersonating, Olivia became the active editor instead of Adam.

v4.5.15.20

v4.5.15.20 had two improvements and 14 bug fixes.

Improvements

• 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.
• Added the query parameter _callers to URLs to display levels in a stack trace. For example, with _callers=10, the profiler provides 10 levels of stack trace.

Bug fixes

• Corrected an issue causing a phrase in the search field that was surrounded in quotation marks to ignore all filters and return all assets. For example, searching for "cms workflow" returned all assets, not just those identifiable by the phrase cms workflow.
• Corrected an issue preventing expected operation of the annotation @Ignored(false).
• Corrected an issue causing incorrect layout of the preview pane.
• Corrected an issue causing incorrect layout of the warning messages appearing under search fields in the left rail. For example, when selecting > Content Templates, if there are no content templates, the warning message No matching items was not laid out correctly.
• Corrected an issue throwing an error in The Shelf. Specifically, after saving a search for an external type (such as YouTube Video), opening The Shelf and selecting Recent Activity > Saved searches threw a NullPointerException.
• Corrected an issue disabling the Format menu when an X (formerly Twitter) post is embedded in the rich-text editor.
• Corrected an issue preventing updates to scheduled revisions from being saved. For example, an editor created a new revision of a homepage, and added a module to the contents. The editor then scheduled this revision. Subsequently, the editor removed a module from the scheduled homepage's contents, and scheduled this new revision. The removed module still appeared. Correcting this issue introduced a breaking change described below.
• Corrected an issue causing the preview pane's width to equal the content edit form's width on initial load.
• Corrected an issue that caused the method SegmentationDatabase#personalize to trigger a large number of extraneous reference resolves.
• Corrected an issue that did not account for the Zip Slip vulnerability. A security check now exists to detect and avoid this vulnerability.
• Corrected an issue preventing rCDA schema generation when a field's internal name has a prefix containing a dash. For example, a prefix declared as String PREFIX = "brightspot.custom-components." prevented schema generation.
• Corrected an issue causing user sessions to unexpectedly end.
• Corrected an issue preventing an asset's state to update if a Set field has dynamic placeholder text.
• Corrected an issue preventing preview-to-edit containers from rendering fields correctly when those fields do not have a valid preview.

Breaking changes

• In the class com.psddev.cms.db.Draft:

  • The method void update(Map, Object, Map, boolean) has been removed.
  • The method void update(Map, Object) is still available.

v4.5.15.19

v4.5.15.19 had six bug fixes.

Bug fixes

• Corrected an issue preventing proper update of default placeholder text. For example, a Byline field's default placeholder text is an asset's author. Deleting the author from the asset did not remove the author from the Byline field.
• Corrected an issue causing delays in rendering large tables in the rich-text editor.
• Corrected an issue causing multiple selections to be cleared. For example, an editor selects two options in a selection field, and then types in the field to locate additional options. After typing in the field, the previous two selections are lost.
• Corrected an issue causing the rich-text editor to mark correctly spelled words as incorrect, and incorrectly spelled words as correct.
• Corrected an issue returning a Service Unavailable status when multiple editors are searching for assets through the search panel.
• Corrected an issue throwing a NullPointerException when selecting several assets in search results and then clicking to open the search actions menu.

v4.5.15.18

v4.5.15.18 had nine bug fixes and one improvement.

Improvements

• 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.

Bug fixes

• Corrected an issue preventing an option from being marked as a favorite in drop-down lists.
• Corrected an issue preventing the method RtcEventUpdateNotifier#onChange from generating NullPointerException errors.
• Corrected an issue causing repeated /contentState calls when opening an asset in the browser, and when that asset has a dynamically hidden embedded record.
• Corrected an issue causing an error when replacing a scheduled draft with a subsequent scheduled draft.
• Corrected an issue in which spell checking caused a reduction in performance.
• Corrected an issue preventing spell checking on Macs with the Apple Silicon chip.
• Corrected an issue causing delays of up to five minutes in cache replication.
• Corrected an issue causing extraneous resolution of references when the referred object is invisible.
• Corrected an issue causing the method ByIdIterator#next to indefinitely return the same object.

v4.5.15.17

v4.5.15.17 had one bug fix.

Bug fixes

• Corrected an issue preventing images from exiting the draft state after uploading those images into a gallery enhancement in the rich-text editor and then publishing the parent asset. For example, an editor starts a new article and adds a gallery enhancement in the rich-text editor. The editor then bulk uploads images into the gallery and publishes the asset. The bulk-uploaded images never appeared as published.

v4.5.15.16

v4.5.15.16 had three bug fixes.

Bug fixes

• Corrected an issue preventing correct selection of a content form when that content form is associated with a user itself associated with a site-specific role. For example, the content edit form Recipe is derived from Article and associated with the role Editor. Adam Braun is an Editor. In this scenario, when Adam Braun started a new asset based on Article, the default Article content edit form appeared instead of Recipe.
• Restored the For Developers tab in an asset's Tools widget for users with the default Full Access role. See "Breaking changes," below.
• Corrected vulnerabilities detected by the OWASP dependency checker.

Breaking changes

• Projects may not not want to expose the Developer tab in an asset's Tools widget for the default role. In such cases, update missingRolePermissions to include -developer/info (or -developer/ to exclude all developer features from the default role).

v4.5.15.15

v4.5.15.15 has two bug fixes.

Bug fixes

• Corrected an issue preventing successful upload of a new image when Brightspot is running on an AWS server.
• Corrected an issue preventing application of a focal point assigned to an image group. For example, a focal point (x, y) was assigned to the Square image group, but Brightspot did not apply that focal point to individual images within that group.

v4.5.15.14

v4.5.15.14 has four bug fixes.

Bug fixes

• Corrected an issue causing inconsistent formatting of editable fields in preview-to-edit. For example, when loading the preview pane, all the editable fields had a border, but clicking inside one of those fields caused borders around the other fields to disappear.
• Corrected an issue causing the browser tab to slow or freeze when attempting to edit a field.
• Corrected an issue causing preview-to-edit field frames to overlap.
• Corrected an issue preventing the preview pane from entirely loading an asset.

v4.5.15.13

v4.5.15.13 has one bug fix.

Bug fixes

• Corrected an issue causing delays of up to five minutes in cache replication.

v4.5.15.12

v4.5.15.12 has one improvements and five bug fixes.

Improvements

• Preview-to-edit is now streamlined for many levels of nested assets. Fields in the preview pane have multiple distinctive borders corresponding to levels of nesting. Modifying nested assets involves fewer mouse clicks.

Bug fixes

• Corrected an issue for which inserting an @-mention of an editor in the Conversation widget incorrectly added the widget's placeholder text.
• Corrected an issue causing a copied value to be assigned a default value instead of retaining an assigned null. For example, an instance of Article has a subheadline intentionally set to null, and the class Article specifies the subheadline field has a default value of Short read. When copying the instance, the new object's subheadline was set to Short read instead of null.
• Corrected an issue that caused the preview pane to scroll to the top after making a change in the associated content edit form.
• Corrected an issue that prevented @Visibility(index) from working in AbstractSearchPageServlet classes with multiple content types.
• Corrected an issue throwing an Unable to format date! message when importing assets from Getty Images.

v4.5.15.11

v4.5.15.11 has two improvements and three bug fixes.

Improvements

• There is no longer a For Editors tab in field level notes. (Depending on permissions, clicking in a field now displays information for developers only.) Editors now see field-level explanations in production guides.
• Continued deployment of displaying workflow statuses with the same name only once in corresponding filter fields.

Bug fixes

• Corrected an issue preventing the correct display of the Conversation widget in custom forms.
• Corrected an issue causing new assets to be saved in MySQL but not in Solr.
• Corrected an issue preventing operational restriction of the Solr facet limit.

v4.5.15.10

v4.5.15.10 has five bug fixes.

Bug fixes

• Corrected an issue causing improper placement of a field's current character count.
• Corrected an issue in which repeatable labels were not displaying for methods returning embedded records or read-only fields containing embedded records.
• Corrected an issue that prevented the preview pane's height from being set correctly.
• Corrected an issue that caused the preview pane to scroll to the top after making a change in the associated content edit form.
• Corrected an issue causing poor performance in the preview pane when the asset has a large number of modules.

v4.5.15.9

v4.5.15.9 has two bug fixes and one improvement.

Improvements

• 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.

Bug fixes

• Corrected an issue causing assignment of unitialized objects instead of null values to copied assets.
• Corrected an issue causing deletion of a scheduled revision when the option is to replace (instead of merge with) the live version.

v4.5.15.8

v4.5.15.8 has one bug fix and one improvement.

Improvements

• The method DefaultDatabasePing#ping now calls Database.Static#getDefaultOriginal to ensure it retrieves the original default database (instead of a possibly overridden default database).

Bug fixes

• Corrected an issue preventing the correct display of the Conversation widget in custom forms.

v4.5.15.7

v4.5.15.7 has one improvement.

Improvements

• Removed arguments as allowed by the upgrade to GraphQL version 19.

v4.5.15.6

v4.5.15.6 had one bug fix.

Bug fixes

• Corrected an issue that threw a java.lang.NullPointerException error when uploading images through the Upload widget.

v4.5.15.5

v4.5.15.5 had two bug fixes and one improvement.

Improvements

• Improved the performance of the method ViewMap#getViewClasses. This improvement will reduce the time to render assets on the front end.

Bug fixes

• Corrected an issue causing NullPointerException errors when ingesting rich text from an external source, such as a Google Doc.
• Corrected an issue preventing the update of a preview when placing an image in The Shelf onto the content edit form.

v4.5.15.4

v4.5.15.4 had three improvements.

Improvements

• Editors can now drag assets from The Shelf into single-value fields such as Lead and Section.
• Plyr and Crosslinker now retrieve associated resources directly from the configured content delivery network (CDN) instead of via Brightspot.
• After a transient and recoverable database error, Brightspot now attempts to re-connect and read API calls.

v4.5.15.3

v4.5.15.3 had two bug fixes and one improvement.

Improvements

• Editors can now drag assets from The Shelf into single-value fields such as Lead and Section.

Bug fixes

• Corrected an issue throwing a ValidationException error when viewing a new image in The Shelf.
• Corrected an issue that prevented correct initialization of values in the content edit form, such as when changing a list from advanced to dynamic.

v4.5.15.2

v4.5.15.2 had three bug fixes.

Bug fixes

• Corrected an issue that prevented a selection's form from being initialized correctly. For example, if you selected an internal call to action, and then selected an external call to action, the external call to action's URL field was not initialized.
• Corrected an issue that caused The Shelf to display native-size images instead of their thumbnails.
• Corrected an issue that caused long delays in rendering The Shelf for a given asset.

v4.5.15.1

v4.5.15.1 had two bug fixes and one improvement.

Improvements

• The module picker now has a search field for quickly finding a specific module or style.

Bug fixes

• Fixed scrolling in the Add widget for adding a module.
• Corrected an issue that prevented new fields from being included in custom content forms. In particular, the Hidden Items widget in Edit Content Form did not include the new field, so admins could not add it to existing content forms. For example, a developer added a new field Eyebrow to the standard content type Article. Admins had no way of adding Eyebrow to custom content forms based on Article.

v4.5.15

v4.5.15 had three bug fixes.

Bug fixes

• Corrected an issue in which reporting widgets with custom grouping displayed special characters incorrectly.

• Corrected two issues with the rich-text editor in full-screen mode:

  • The move icon did not appear with enhancements.
  • Quote modules were read-only.

• Corrected an issue in which copying a copied asset (editor copies an article, then copies the copy) threw an error message Can't render /cms/copy-record!.

v4.5.14

v4.5.14 had 26 bug fixes and five improvements.

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.

Bug fixes

• 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.

v4.5.13.3

v4.5.13.3 had two improvements.

Improvements

• In the Revisions widget, a clearer presentation is now available for revisions by audience.

• Editors now have two choices to manage the inheritance between a default variant and an audience variant.

  • For fields not changed in the audience variant, content from the default variant flows to the audience variant.
  • All fields in the audience variant are considered as changed, so no content flows from the default to the audience variant.

v4.5.13.2

v4.5.13.2 had two bug fixes.

Bug fixes

• Corrected the following issues pertaining to preview-to-edit:

  • Corrected an error in which editors clicking on a particular field in preview-to-edit were directed to a different field in the content edit form.
  • 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.

v4.5.13.1

v4.5.13.1 had two bug fixes.

Bug fixes

• Corrected an issue that caused error messages to appear in place of code blocks when the containing topic included anchors.
• Corrected an issue causing text in the rich-text editor to be saved as encoded HTML. For example, the text This is some text with spaces was saved as This%20is%20some%20text%20with%20spaces.

v4.5.13

v4.5.13 had 24 bug fixes and four improvements.

Improvements

• Replaced the error message Invalid Java field name! appearing in editorial content types with wording that provides better context and recommendations to resolve.
• When designing a theme or template in Styleguide, the presets now default to Custom if no presets have been defined for that theme or template.
• The Suggestions widget now displays field-specific suggestions in the same order as the corresponding content edit form. For example, a content edit form has a field for Sections followed by a field for Tags. The Suggestions widget displays a cluster for suggested sections followed by a cluster for suggested tags.
• The content type Raw HTML was renamed to HTML Page.

Bug fixes

• Corrected an issue in which queries working in Solr 4.6.1 no longer work in Solr 8.11.1.

• Corrected an issue in which fields annotated with @Hidden were unavailable in custom content edit forms.

• Corrected an issue that threw StringIndexOutOfBoundsException when getting DIMS image URLs.

• Corrected an issue in which editing a rich-text field in the preview pane caused browser crashes or slowness.

• Corrected an issue in which the Recent Activity and Unpublished Drafts widgets displayed error messages after saving an editorial content type.

• Corrected an issue in which the search panel's export feature did not actually export assets in a non-visible state (such as in a workflow).

• Corrected an issue preventing the conversion of a promo module from one-off to shared. For example, an editor created a one-off module to be used as a layout override. The module referred to an archived asset. In this scenario, the editor could no convert the one-off module to a shared module.

• Corrected an issue in which the sites filter in the Content Types widget did not correctly display sites to which an editor had permissions.

• Corrected an issue that caused a performance hit when using a self-service SAML authenticator.

• Corrected an issue in which archived vanity and site redirects always threw error 404. For example, an admin archived the redirect from /index to /welcome. With this fix, requests to /index display the actual asset at /index.

• Corrected the following issues pertaining to preview-to-edit:

  • Clicking on a particular field redirected editors to a different field in the content edit form.
  • Scrolling in the preview pane did not extend to the bottom of the pane.

• Corrected an issue causing numbered lists with a customized start value to be removed from the rich-text editor. For example, an editor started a numbered list with 4. After saving or publishing the containing asset, the numbered list was removed.

• Corrected an issue in which CMA resource file uploads failed when the uploaded file included nested diffs in variables.

• Corrected an issue in which the rich-text editor in full-screen mode did not occupy the entire screen on a tablet.

Breaking changes

• The fix for Solr 8.11.1 described above requires a SQL-to-Solr copy.

v4.5.12.4

v4.5.12.4 had one bug fix.

Bug fixes

• Corrected an issue preventing previews from appearing in the module picker.

v4.5.12.3

v4.5.12.3 had four bug fixes and one improvement.

Improvements

• When designing a theme or template in Styleguide, the presets now default to Custom if no presets have been defined for that theme or template.

Bug fixes

• Corrected an issue that caused the message Restored Work In Progress to appear after publishing, closing, and then re-opening an asset.
• Corrected an issue that caused error messages to appear in place of code blocks when the containing topic included anchors.
• Corrected an issue that caused the Types field in the New Content Type form to be empty.
• Corrected an issue in which the sites filter in the Content Types widget did not correctly display sites to which an editor had permissions.

v4.5.12.2

v4.5.12.2 had one bug fix and two improvements.

Improvements

• Standardized the workflow for deleting editorial content types; admins must now first archive the editorial content type, and then delete it permanently.
• Improved the usability of the displayed error message when using an invalid field name in an editorial content type.

Bug fixes

• Corrected an issue in which the Recent Activity and Unpublished Drafts widgets displayed error messages after saving an editorial content type.

v4.5.12.1

v4.5.12.1 had one bug fix.

Bug fixes

• Corrected an issue in which saving an editorial content type resulted in a server error.

v4.5.12

v4.5.12 had six bug fixes and seven improvements.

Improvements

• Saved searches now remember the editor's selected tab and exposed fields. For example, an editor saves a search MySearch while in board view and showing only the label field. The next time the editor runs MySearch, the results will be in board view and showing only the label field.
• List fields now have an expand all and collapse all control that shows and hides all items in a list.
• Further deployed tool-tip text for icons.
• The Recent Searches and Saved Searches widgets retain their open/close setting after closing the search panel. For example, an editor closes the search panel with the Recent Searches widget open; the next time the editor opens the search panel, the Recent Searches widget opens automatically.
• The Tools widget displays the For Developers tab only if the editor has developer permissions.
• Improved usability of error messages pertaining to workflow design.

Bug fixes

• Corrected an issue in which editorial content types with duplicate field names caused unexpected behavior.
• Corrected an issue that prevented the add control from appearing in list fields.
• Corrected an issue in which editors clicking on a particular field in preview-to-edit were directed to a different field in the content edit form.

v4.5.11.5

v4.5.11.5 had one bug fix.

Bug fixes

• Corrected an issue preventing a scheduled asset's variations from being published. For example, if an asset had a variation for a particular audience, the audience's variation was not published on the scheduled date.

v4.5.11.4

v4.5.11.4 had one bug fix.

Bug fixes

• Corrected an issue in which Integer fields in embedded objects did not validate correctly after first publish. For example, an integer field in an embedded object is constrained with annotations @Minimum(1) and @Maximum(12). After clicking Publish for the first time, editors could enter values beyond the annotated range, and even enter non-integer values.

v4.5.11.3

v4.5.11.3 had one improvement.

Improvements

• There is no longer a For Editors tab in field level notes. (Depending on permissions, clicking in a field now displays information for developers only.) Editors now see field-level explanations in production guides.

v4.5.11.2

v4.5.11.2 had one bug fix.

Bug fixes

• Corrected an issue preventing a module's Template field from displaying all available templates. For example, when selecting a list module for a page's content, the module picker previews five available templates. After selecting one of the templates and returning to the content edit form, the Template tab listed only one of those five templates (instead of all five).

v4.5.11

v4.5.11 included the following:

• 14 bug fixes
• 3 new features
• 1 improvement

Improvements

• For Getty integrated search results, a date created field is now associated with each retrieved asset. Getty's "sort by newest" feature sorts by the date the asset was submitted, not the date it was created. With the date created field in Brightspot, editors can sort by newest date created or newest date submitted.

Bug fixes

• Preview-to-edit:

  • Corrected an error that prevented editing of embedded or shared objects using preview-to-edit.
  • Corrected labeling of the rich-text editor field in preview-to-edit.

• Corrected view model overlays causing degraded front-end performance.

• Corrected an error that prevented removing fields from a production guide.

v4.5.10.13

v4.5.10.13 had two bug fixes and one improvement.

Improvements

• The Recent Searches and Saved Searches widgets retain their open/close setting after closing the search panel. For example, an editor closes the search panel with the Recent Searches widget open; the next time the editor opens the search panel, the Recent Searches widget opens automatically.

Bug fixes

• Improved accessibility in the CMS.
• Corrected an issue preventing the production guide's scrolling to a date field when clicking on the field's help icon .

v4.5.10.12

v4.5.10.12 had one improvement.

Improvements

• Corrected an issue that, in the context of a workflow, caused the Revisions widget to mark an asset's state as Published when the transition was actually back to the New state.

v4.5.10.11

v4.5.10.11 had one improvement.

Improvements

• Improved accessibility in the CMS.

v4.5.10.10

v4.5.10.10 had one bug fix.

Bug fixes

• Corrected an issue causing numbered lists with a customized start value to be removed from the rich-text editor. For example, you started a numbered list with 4. After saving or publishing the containing asset, the numbered list was removed.

v4.5.10.9

v4.5.10.9 had one bug fix.

Bug fixes

• Corrected an issue in which queries working in Solr 4.6.1 no longer work in Solr 8.11.1.

Breaking changes

• The fix described above requires a SQL to Solr copy.

v4.5.10.8

v4.5.10.8 had one bug fix and one improvement.

Improvements

• A new Query.option is available to opt out of Solr query joins.

Bug fixes

• Corrected an issue that caused poor performance when using Solr joins.

v4.5.10.7

v4.5.10.7 had one bug fix.

Bug fixes

• Corrected an issue in which, when adding a module in the rich-text editor, the Enhancement Style fields were not appearing.

v4.5.10.6

v4.5.10.6 had 1 improvement.

Improvements

The work-in-progress feature now preserves content in new assets. Previously, WIP saved work for assets that were in draft, revision, scheduled or other states other than new.

v4.5.10.2

v4.5.10.2 had 1 bug fix.

Bug fixes

• The Query Usages debug tool repeatedly launched a background task, thereby affecting performance. That tool is no longer supported and was removed from the Dari standard tools.

v4.5.10.1

v4.5.10.1 had 2 bug fixes.

Bug fixes

• Corrected a regression error that displayed empty production guides that cannot be closed.
• Corrected an issue preventing the copying of modules in a list used as an enhancement in the rich-text editor.

v4.5.10

v4.5.10 had 24 bug fixes, one new feature, and four improvements.

New features

• The Styleguide build command has a new option that allows for a continuous integration pipeline. The option is -p puppeteer-custom-config.json. The contents of puppeteer-custom-config.json override the standard Styleguide build configuration. A typical command is as follows:

  yarn node node_modules/@brightspot/styleguide/build/bundle -b build/styleguide -o build/theme.zip -p puppeteer-launch-config.json

Improvements

• Enhanced accessibility in various Brightspot forms and widgets.

  • Search filters now have the aria-labelledby attribute to describe the inputs.
  • Keyboard shortcuts are available for editing images and videos.
  • The focus order of the items in the navigation area are now sequential.
  • In the image and video editing UI, the crop feature now has a proper name, role, and value.
  • Individual projects can customize the purpose of each input field.
  • Tabs remain tabs in smaller resolutions instead of turning into a menu.
  • Increased contrast between separators and items in a list.
  • Buttons in the header now have visible focus.
  • Clear identification of multiple languages, such as mixed English and Spanish, in the rich-text editor.

• Ensured that Styleguide builds invalidate the browser cache so that after five minutes the server delivers the latest assets.

• In board view, editors can now abort a drag-and-drop action by returning the dragged card to its initial column.

• Improved the MarkedText schema in GraphQL.

Bug fixes

• Corrected a regression error that caused batch upload failures into objects of type GoogleStorageItem.
• Corrected an issue in which invalid Dynamic Placeholder values can block editors from creating new content.
• Corrected issues that prevented saving and processing of editorial content types.
• Corrected an issue that prevented correct operation of the show/hide comments toggle.
• Corrected an issue that prevented proper deployment of a new bundle to an existing theme.
• Corrected an issue that caused overlays to disappear when adding a slide to a homepage carousel.
• Corrected an issue that caused comments to appear in promo descriptions.
• Corrected an issue that displayed the Edit Theme widget behind a full-screen rich-text editor.
• Corrected a regression error that displayed empty production guides that cannot be closed.

Breaking changes

The schema for the CDA and rCDA have changed, and the following elements have been removed:

• interface Mark—removed
• type HtmlMark—removed
• type MarkedText—removed
• type RichTextMark—removed

For the rCDA, there is an option for backwards compatibility in the form of a Use Marked Text Schema V1 toggle field in the Advanced tab of Recordable API schema settings.

For the regular view CDA, this is a breaking change with no backwards compatibility.

v4.5.9.33

v4.5.9.33 had one bug fix and one improvement.

Improvements

• Added the query parameter _callers to URLs to display levels in a stack trace. For example, with _callers=10, the profiler provides 10 levels of stack trace.

Bug fixes

• Corrected an issue that caused the method SegmentationDatabase#personalize to trigger a large number of extraneous reference resolves.

v4.5.9.32

v4.5.9.32 had one bug fix.

Bug fixes

• Corrected an issue that threw a java.lang.ClassCastException when attempting to retrieve an ExternalContentRichTextElement (such as TweetUrl or RawHtml).

v4.5.9.31

v4.5.9.31 had one bug fix.

Bug fixes

• Corrected an issue causing incomplete conversion of double quotes to smart quotes in text containing characters outside of Basic Latin (such as ó).

v4.5.9.30

v4.5.9.30 had one bug fix.

Bug fixes

• Corrected an issue preventing save of WIP for new assets.

v4.5.9.29

v4.5.9.29 had one bug fix.

Bug fixes

• Corrected an issue causing text in the rich-text editor to be saved as encoded HTML. For example, the text This is some text with spaces was saved as This%20is%20some%20text%20with%20spaces.

v4.5.9.28

v4.5.9.28 had one bug fix.

Bug fixes

• Corrected an issue preventing the correct display of code examples in topics with internal anchors.

v4.5.9.27

v4.5.9.27 had three bug fixes.

Bug fixes

• Corrected an issue preventing display of the icon in the URLs widget.
• Corrected an issue that prevented editors from assigning content forms having a site-specific scope to a role.
• Corrected an issue in which methods in the class HandlebarsTemplateRenderer created repeated objects that caused heap exhaustion.

v4.5.9.25

v4.5.9.25 had two bug fixes.

Bug fixes

• Corrected an issue in which links and other enhancements embedded into a custom priority tag (in the rich-text editor) were causing the priority tag to be split into multiple instances instead of a single tag that encompassed all text and enhancements added to it.
• Corrected an issue causing an error when replacing a scheduled draft with a subsequent scheduled draft.

v4.5.9.24

v4.5.9.24 had one bug fix.

Bug fixes

• Corrected an issue causing the browser tab to slow or freeze when attempting to edit a field.

v4.5.9.23

v4.5.9.23 had one bug fix.

Bug fixes

• Corrected an issue preventing editors from clicking and editing nested rich-text fields inside preview-to-edit.

v4.5.9.22

v4.5.9.22 had one improvement.

Improvements

• Added the SQL predicate HAVING to query hash code.

v4.5.9.21

v4.5.9.21 had two bug fixes.

Bug fixes

• Corrected an issue causing deletion of a scheduled revision when the option is to replace (instead of merge with) the live version.
• Corrected an issue causing inconsistent formatting of editable fields in preview-to-edit. For example, when loading the preview pane, all the editable fields had a border, but clicking inside one of those fields caused borders around the other fields to disappear.

v4.5.9.20

v4.5.9.20 had one improvement.

Improvements

• Preview-to-edit is now streamlined for many levels of nested assets. Fields in the preview pane have multiple distinctive borders corresponding to levels of nesting. Modifying nested assets involves fewer mouse clicks.

v4.5.9.19

v4.5.9.19 had three bug fixes.

Bug fixes

• Corrected an issue with 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) that caused preview-to-edit to not function.
• Corrected an issue in which an editor's local time zone America/Mexico_City was not accounted for when the Brightspot server's time zone was America/New_York. For example, publishing an asset at 13:00 in Mexico City appeared as published at 15:00.
• Corrected an issue that caused the preview pane to scroll to the top after making a change in the associated content edit form.

v4.5.9.17

v4.5.9.17 had three bug fixes.

Bug fixes

• Corrected an issue that prevented scrolling to the bottom of the preview pane.
• Corrected an issue that prevented the preview pane's height from being set correctly.
• Corrected an issue that disabled scrolling in the preview pane after updating text in the associated content edit form.

v4.5.9.15

v4.5.9.15 had four bug fixes.

Bug fixes

• Corrected an issue in which, when adding a module in the rich-text editor, the Enhancement Style fields were not appearing.

• Corrected an issue in which a question mark ? in a search term incorrectly returned zero results.

• Corrected the following issues pertaining to preview-to-edit:

  • Corrected an error in which editors clicking on a particular field in preview-to-edit were directed to a different field in the content edit form.
  • Clicking a shared embedded child asset in the parent asset's preview pane opened a different, incorrect child asset in the content edit form.

v4.5.9.13

v4.5.9.13 had one bug fix.

Bug fixes

• Corrected an issue causing the theme editor's paintbrush icon to appear over the production guide's help icon .

v4.5.9.12

v4.5.9.12 had one improvement.

Improvements

• Because editors write their production guides in the Guide widget, the For Editors tab no longer appears in field-level help. The question mark indicating field-level help is available appears only when the current user has developer-level permissions.

v4.5.9.11

v4.5.9.11 had three bug fixes.

Bug fixes

• 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.

v4.5.9.10

v4.5.9.10 had two bug fixes.

Bug fixes

• Corrected an issue that caused the message Restored Work In Progress to appear after publishing, closing, and then re-opening an asset.
• Corrected an issue causing multi-select dropdown lists to lose selections when using type-ahead. For example, you are customizing a Search dashboard widget. In Display Fields, you type Date and then select Update Date. You next type User and then select Update User. The second selection removed the first selection Update Date.

v4.5.9.9

v4.5.9.9 had three bug fixes.

Bug fixes

Corrected the following issues pertaining to preview-to-edit:

• Editing a rich-text field in the preview pane caused browser crashes or slowness.
• Clicking on a particular field in preview-to-edit redirected editors to a different field in the content edit form.
• Scrolling in the preview pane did not extend to the bottom of the pane.

v4.5.9.8

v4.5.9.8 had 1 bug fix.

Bug fixes

Corrected an issue that resulted in the unnecessary creation of timers within SAML configurations.

v4.5.9.7

v4.5.9.7 had 1 bug fix.

Bug fixes

Corrected an error in which editors clicking on a particular field in preview-to-edit were directed to a different field in the content edit form.

v4.5.9.6

v4.5.9.6 had 1 bug fix.

Bug fixes

• Corrected an issue in which repeatable labels were not displaying for methods returning embedded records or read-only fields containing embedded records.

v4.5.9.5

v4.5.9.5 had 2 bug fixes.

Bug fixes

• Preview-to-edit:

  • Corrected an error that prevented editing of embedded or shared objects using preview-to-edit.
  • Corrected highlighting of the rich-text editor field in preview-to-edit.

v4.5.9.4

v4.5.9.4 had 1 bug fix.

Bug fixes

• Corrected a regression error that displayed empty production guides that cannot be closed.

v4.5.9.3

v4.5.9.3 had 1 bug fix.

Bug fixes

• Corrected an issue that prevented style preset custom settings from being saved in a module when the module was embedded inside of the rich-text editor.

v4.5.9.2

v4.5.9.2 had 3 bug fixes.

Bug fixes

• Corrected an issue that caused a JavaScript error when no broadcast component is present.
• Corrected an issue that caused a compilation error when calling ToolPageContext#createObjectLabelHtml.
• Corrected an issue that caused overlays to disappear when adding a slide to a homepage carousel.

v4.5.9

Brightspot 4.5.9 has 20 bug fixes and 2 improvements.

Caution

An issue was discovered affecting v.4.5.9 that prevents users from setting style presets from the rich-text editor, such as setting alignment on modules. A workaround is available by adding the following custom CSS.

.CIG-row.StyleguidePreset-row .CIG-small:has(select[data-selected-id=""]) + .CIG-large { 2 display: block !important; 3}

The custom CSS above is compatible with Apple Safari and Google Chrome. A setting must be updated in Mozilla Firefox for the custom CSS to be compatible. See Mozilla's browser compatibility section.

Improvements

• Improved the display of Image Recognition tags and moved them to a more intuitive location, under the Advanced menu of the image itself.
• Improved the default image recognition confidence levels—now defaulting to 50%.
• Improved revision comparisons UI to exclude excessive HTML markup.

Bug fixes

• Corrected an issue in 4.5.8 affecting two-factor authentication.
• Corrected an issue causing cascading fields in Pre-publish actions to display duplicate call to actions.
• Corrected an issue related to an error produced by adding colors to the color palette via swatches.
• Corrected an issue that caused an error when removing an editorial content type that was referenced in a different editorial content type.
• Corrected an issue related to a non-breaking space in the rich-text editor causing a runtime error in GraphQL.
• Corrected an issue preventing front-end color picker fields and some other fields from saving at times.
• Corrected an issue occasionally preventing Preview to edit from recognizing content from references.
• Corrected an issue related to the rich-text editor not rendering properly if certain fields were present.

v4.5.8.1

v4.5.8.1 had 1 improvement.

Improvements

• Table rows can now be isolated for processing on the front end.

v4.5.8

Brightspot 4.5.8 has 23 bug fixes, 8 improvements, and 1 new feature.

Caution

A significant issue was discovered in v.4.5.8 that affects two-factor authentication. This issue was fixed in v.4.5.9. When evaluating an upgrade, Brightspot advises that customers upgrade to v.4.5.9 or later.

Improvements

• Improved the display of Image Recognition tags and moved them to a more intuitive location, under the Advanced menu of the image itself.
• Improved the default image recognition confidence levels—now defaulting to 50%.
• Improved revision comparisons UI to exclude excessive HTML markup.

Bug fixes

• Corrected an issue causing PaginatedResult.hasNext()returning true when there were zero elements.
• Corrected occasional erratic cluster behavior with dynamic fields.
• Corrected an issue causing v.4.5.7 styles to render too large.
• Corrected an issue preventing Social Service edit pages from appearing in v.4.5.6.
• Corrected an issue that at times prevented the New Site Category link from working.
• Corrected an issue causing images to appear in different sizes in Search Grid View.
• Corrected an issue causing TypeAhead to reset on string fields when using ValueGeneratorannotation.

v4.5.7.9

v4.5.7.9 had one improvement.

Improvements

• Added the SQL predicate HAVING to query hash code.

v4.5.7.8

v4.5.7.8 had one bug fix.

Bug fixes

• Corrected an issue that prevented removing an asset from a reference field.

v4.5.7.7

v4.5.7.7 had 2 bug fixes.

Bug fixes

• Corrected an issue preventing front-end color picker fields and some other fields from saving at times.
• Corrected an issue that caused overlays to disappear when adding a slide to a homepage carousel.

v4.5.7.6

v4.5.7.6 had 1 bug fix.

Bug fixes

• Corrected an issue that caused an error when removing an editorial content type that was referenced in a different editorial content type.

v4.5.7.5

v4.5.7.5 had 1 improvement and 2 bug fixes.

Improvements

• Improved the display of highlighted rich-text enhancements when text that uses them is highlighted in the editor, to include the icon representing the drop-down menu where some of these enhancements may live.

Bug fixes

• Corrected an issue causing PaginatedResult.hasNext() to return as true when there were zero elements.
• Corrected an issue preventing template fields from appearing when adding style templates.

v4.5.7.4

v4.5.7.4 had 1 bug fix.

Bug fixes

• Corrected an issue at times preventing editors from viewing import pages of integrated search providers if the site being used was not Global.

v4.5.7.3

v4.5.7.3 had 1 improvement and 12 bug fixes.

Improvements

• Made revisions of articles that include one-off modules easier to read when comparing them to one another.

Bug fixes

• Corrected an issue preventing the yellow bar that denotes that a change has been made to a field from appearing on the Styles tab of a content type.
• Corrected an issue preventing editors from scrolling properly in the preview pane when preview-to-edit was enabled.
• Corrected an issue at times preventing social icons, account names, and edit icons from appearing on social accounts.
• Corrected an issue causing images sorted by collage order to show different sizes in Brightspot search grid view.
• Corrected an issue triggering an error when a shared module was added as a rich-text enhancement.
• Corrected an issue preventing an editor from adding a new site category from Sites & Settings, instead producing the content edit form for a new site.
• Corrected an issue preventing text fields in embedded records in @DisplayGrid from wrapping after publishing.
• Corrected an issue preventing social service edit pages from appearing as intended.
• Corrected an issue causing certain styles to render too large in the Styles tab of a module.
• Corrected an issue throwing a JavaScript error when selecting multiple cells in a table in the rich-text editor.
• Corrected an issue causing comments in the rich-text editor to display as raw HTML.
• Corrected an issue related to an unhelpful error that appeared after adding an existing URL to the Local URLs field in the vanity URL redirect content edit form.

v4.5.7.1

v4.5.7.1 had 1 bug fix.

Bug fixes

• An issue was preventing editors from scrolling properly in the preview pane when preview-to-edit was enabled.

v4.5.7

Brightspot 4.5.7 has 19 bug fixes, 17 improvements, and 2 new features.

Improvements

• Improved Production Guides so that field descriptions are now shared across content types, saving users the time and keystrokes it would take to duplicate that information in each instance.

• Added Instagram Reel support to Brightspot's rich-text editor.

• GraphQL improvements:

  • Allowed programmatic creation of API clients/keys, even when no WebRequest is present.
  • Improved UX of API and GraphQL explorer pages
  • Added indication that options are set without opening popup
  • Added ability to override entire endpoint path
  • Now includes link to GraphQL explorer from API configuration

Bug fixes

• Corrected an issue preventing Preview to edit from functioning as intended after publishing a specific kind of menu.
• Corrected an issue occasionally causing missing social icons, account names, and edit icons.
• Corrected an issue that at times prevented @DisplayGrid from working on embedded records.
• Corrected a UI issue causing the Schedule button from sometimes covering a part of the Back to Workflow button.
• Corrected an issue preventing the content edit widget from displaying data.
• Corrected an issue causing a freeze when a Call to Action was used as a Lead containing a self-referential link.
• Corrected a styling issue when uploading files in a List field.

v4.5.6.8

v4.5.6.8 had 4 bug fixes.

Bug fixes

• Corrected an issue preventing an editorial content type from appearing outside of the editorial content types page if it was saved with a duplicated field name.
• Corrected an issue in which invalid Dynamic Placeholder values can block editors from creating new content.
• Corrected an issue that prevented an editorial content type's internal name from being automatically updated after its name value was changed due to a validation error.
• Corrected an issue when saving an editorial content type with a nameless field that caused an error instead of a validation message.

v4.5.6.7

v4.5.6.7 had 1 bug fix.

Bug fixes

• Corrected an issue that occurred when a non-breaking space in the rich-text editor was at times causing a runtime error in the GraphQL Explorer.

v4.5.6.6

v4.5.6.6 had 1 bug fix.

Bug fixes

• Corrected an issue that caused an error when removing an editorial content type that was referenced in a different editorial content type.

v4.5.6.5

v4.5.6.5 had 1 bug fix.

Bug fixes

• Corrected an issue that caused an error when removing an editorial content type that was referenced in a different editorial content type.

v4.5.6.4

v4.5.6.4 had 2 bug fixes.

Bug fixes

• Corrected an issue that caused an error when removing an editorial content type that was referenced in a different editorial content type.
• Corrected an issue preventing an editorial content type from appearing outside of the editorial content types page if it was saved with a duplicated field name.

v4.5.6.3

v4.5.6.3 had 1 bug fix.

Bug fixes

• Corrected an issue that caused an error when removing an editorial content type that was referenced in a different editorial content type.

v4.5.6.2

v4.5.6.2 had 1 new feature.

New features

• Added the ability for the rCDA to return raw HTML for rich-text fields on content.

v4.5.6

Brightspot 4.5.6 has 10 bug fixes, 16 improvements, and 1 new feature.

Improvements

• Added ability for editors to specify whether changes made to an existing bulk schedule are automatically merged into the schedule or not. If selecting "Do not merge updates," any changes will be live exactly upon publish instead of being held in the schedule for a future publish.
• Improved Post-publish actions UI.
• Added additional handlebars rendering support for Editorial content types. Now, Editorial content types that are configured to extend another Java class or implement an interface will include fields and methods from the superclass, from modifications on the superclass, from modifications on interfaces selected in the JavaScript Class UI, and additionally now display an error message if any methods from an abstract superclass or interface are unimplemented.

Bug fixes

• Corrected an issue related to refresh times that was at times causing 503 errors.
• Corrected an issue in which the criteria for creating a workstream were not saved with the workstream itself.
• Corrected an issue that caused re-connection to the replicator server to deliver an asset's old revision (the replicator server's cache was not invalidated after re-connection to Brightspot).

Breaking changes

• As a result of improving support for extending superclasses (related to Editorial Content Types and Javascript support), a number of changes were made. Please reference the ticket named BSP-13333 when seeking guidance.

v4.5.5.5

v4.5.5.5 had 1 improvement.

Improvements

• Improved the way preview-to-edit handles light mode and dark mode to ensure a smoother editing experience.

v4.5.5.4

v4.5.5.4 had 1 bug fix.

Bug fixes

• Corrected an issue when using Getty Images integrated search that prevented newest results from displaying first when sorting by newest.

v4.5.5.3

v4.5.5.3 had 1 bug fix.

Bug fixes

• Corrected an issue in which text pasted inside an existing comment was pasted as plain text. For example, an editor copied a URL from a browser. The editor placed the cursor inside a comment in the rich-text editor and pastes. The pasted URL appeared as plain text, not as part of the comment.

v4.5.5.2

v4.5.5.2 had 1 bug fix.

Bug fixes

• Corrected an issue that was preventing the replication cache from staying in sync or updating.

v4.5.5

Brightspot 4.5.6 has 10 bug fixes, 16 improvements, and 1 new feature.

Improvements

• Added ability for editors to specify whether changes made to an existing bulk schedule are automatically merged into the schedule or not. If selecting "Do not merge updates," any changes will be live exactly upon publish instead of being held in the schedule for a future publish.
• Improved Post-publish actions UI.
• Added additional handlebars rendering support for Editorial content types. Now, Editorial content types that are configured to extend another Java class or implement an interface will include fields and methods from the superclass, from modifications on the superclass, from modifications on interfaces selected in the JavaScript Class UI, and additionally now display an error message if any methods from an abstract superclass or interface are unimplemented.

Bug fixes

• Corrected an issue related to refresh times that was at times causing 503 errors.

Breaking changes

• As a result of improving support for extending superclasses (related to Editorial Content Types and Javascript support), a number of changes were made. Please reference the ticket named BSP-13333 when seeking guidance.

v4.5.4.4

v4.5.4.4 had 1 bug fix.

Bug fixes

• Addressed an XSS security vulnerability.

v4.5.4.3

v4.5.4.3 had 1 improvement and 1 bug fix.

Improvements

• Table rows can now be isolated for processing on the front end.

Bug fixes

• Corrected an issue causing tables to be rendered incorrectly on the front end.

v4.5.4.2

v4.5.4.2 had 1 bug fix.

Bug fixes

• Corrected an issue causing a freeze when a Call to Action was used as a Lead containing a self-referential link.

v4.5.4.1

v4.5.4.1 had 1 bug fix.

Bug fixes

• Corrected an issue was forcing an error code to be repeatedly printed when a theme build failed to unzip.

v4.5.4

Brightspot 4.5.4 has 13 bug fixes, 14 improvements, and 9 new features.

Improvements

• Modules can now be swapped between one-off and shared from within the content type where they are used. This saves editors time and mouse clicks since they no longer must navigate away from the content edit page.
• Added Pre-publish actions functionality, which provide users with reminders, suggestions, and actions before content is published.
• Added integration with Veeva Vault, allowing users to map Veeva’s Content Modules to Brightspot content.
• Editors may now make editorial content types specific to a given site, making navigating through editorial content types easier.
• Google Analytics now includes more metrics that are sortable and accessible in search-, site-, and asset-level reporting, like page views, unique page views, sessions, and bounce rate.
• Brightspot’s Getty Images federated search integration will now display a number of additional filters, including age, number of people, hex value, and more.
• Admins may now decide whether or not Production Guides are available on a site in the CMS. This setting respects hierarchy, and can be overridden at a lower level of the hierarchy if desired.
• Filters and pagination have been added to the Sites and Content Type widgets to make it easier for users to locate the site or content type they need.
• Assignment Desk's Board View now includes the ability to group data by workflow status and default status.
• Administrators can now create site-specific roles for users. The Roles field in Users & Roles has been replaced with a Permissions dropdown field, where administrators can designate roles accordingly.
• To improve CMS accessibility, icons now display tooltips upon hover, showing what action they perform.
• The Share Image popup now includes a copy URL button.
• A workflow permission can be configured to allow a role to only transition an asset to the Publish state.

Bug fixes

• Corrected an issue caused by the Handlebars helper #or being inconsistent with the #if operator.

Breaking changes

• > Admin > Content Types > CSS Class has been renamed to Row and now has added support in clusters and tabs. As a result, the class CssGroup.java that was introduced in v.4.5.3 has been renamed to Row.java.

v4.5.3.2

v4.5.3.2 had 1 bug fix.

Bug fixes

• Corrected an issue was at times preventing embedded fields from returning in query results in the GraphQL Explorer.

v4.5.3.1

v4.5.3.1 had 2 bug fixes.

Bug fixes

• Corrected an issue causing dynamic placeholders to not work correctly when used on an empty value.
• Corrected an issue was occasionally adding unintended line breaks to items in a list.

v4.5.3

Brightspot 4.5.3 has 9 bug fixes, 18 improvements, and 6 new features.

Improvements

• Added new Post-publish actions feature, allowing editors an easy way to take additional, important actions after publishing a piece of content.

• Added an Authorship Volume & Engagement widget. The volume and engagement metrics that this widget exposes will help publishers and editors visually keep track of the volume of content being created as well as the engagement with this content.

• Facilitated management of UI settings, which now live in the CMS tab and the UI cluster automatically. These settings respect hierarchy.

• Improved translations, specifically by allowing a translated asset to automatically be assigned to the correct site based on the available locales, and by allowing editors to pick a shared or one-off site group.

• The Translation plugin now provides an additional setting to configure which locales a site can support. This helps prevent the Translation tab from getting crowded with available locale options if an admin wants to enforce that an editor only use one.

• Improved "favoriting" UI.

• Site category search now includes any subcategories of parent categories returned when filtering results (not just those subcategories that were directly linked).

• Improved UI for The Shelf.

• When adding search result fields, editable placeholder text is now displayed alongside the editable placeholder, resulting in less clicks for the editor and a better general sense of which field is being added.

• Improved Search Board View:

  • Boolean values in the Search Board View or in the Field Preview Popup are now localized, facilitating the Brightspot user experience for non-English speakers.
  • Dragging cards from column to column is now much faster. Additionally, the place where an editor drags a card now persists after the drop.
  • Improved UI.

• “Bring Your Own Key” functionality has been enabled for AWS Rekognition, AWS Translate, AWS Transcribe, and AWS Comprehend integrations.

• Editors now have the ability to group fields in a CSS Group in order to influence the layout of an editorial content type.

• Editors now have the ability to choose a material icon to display along with their editorial content types in the CMS (like in the Quick Start widget).

• Time-related fields in Google Analytics (like Time on Page) are now configured to be reported in HH:MM:SS format.

Bug fixes

• Corrected an issue causing the Image Recognition task to attempt to run twice.

v4.5.2

Brightspot 4.5.2 has 25 bug fixes, 24 improvements, and 1 new feature.

Improvements

• Brightspot now provides a data model and API for securely storing secrets and providing integrations with common secret managers.
• Previews are now able to be requested using a preview ID. This ID is accessible via {rest-api-prefix}/preview/{preview-id} and returns in the same format as /contents API.
• Editorial content types now support List <string> fields.
• In content selectors, recently updated results now sort by update date.
• Site categories now have subcategories, allowing for better categorization of sites.
• The Quick Start widget will now display a message if no content types are available to display.
• Editors may now define an expiration date on shared preview links.
• Improvements to the GraphQL explorer.
• Previous filter selections are now retained for users using The Shelf.
• The Styleguide UI has been improved.
• Added ability to disable CMS proxy servlet, allowing images to be served directly to a user's browser if desired.

Bug fixes

• Corrected an issue related to Page load occasionally producing an error that blocked preview from loading.
• Corrected an issue causing multiple Slack and email notifications for a single triggering event.

Breaking changes

• There was a refactor of the singular Intranet User Modification into smaller, more specific modification classes. Because of this, the hidden/indexed employeeTypeType field has changed; therefore, the script (please reference the ticket named BSP-12381 when seeking guidance) will need to be run to loop over the User records into the production Brightspot Intranet site, and they will need to be re-saved.

v4.5.1

Brightspot 4.5.1 has 16 bug fixes, 18 improvements, and 2 new features.

Improvements

• Editors can now define Custom Locales that can be used globally across Brightspot without any operational or development work.

• Nested lists are now allowed in CMA models and CDA view models.

• A number of improvements to The Shelf, including:

  • Quality of life improvements
  • Improved positioning of the drawer close button
  • New multi-select drag and drop functionality
  • A new information icon and content summary for cards included in the Shelf

• GraphQL nested lists, similar to Java's private List<List<List<String>>> getNested(), are now supported in CMA models and CDA view models.

Bug fixes

• Corrected an issue preventing the GraphQL CMS endpoint from not displaying all fields for a content type.
• Corrected an issue preventing keywords from being added to article revisions when using the SEMrush integration.
• Corrected UI issues related to refactored preview system.

Breaking changes

• Raw HTML name is no longer unique, which may cause issues if project code depends on it.
• Enhancement view interfaces were changed so that it is possible to add front-end fields only to block level elements. As a result, this changes how rich text elements are rendered. Each rich-text element is now separated out into its own enhancement. If any group of elements should get a front-end field, they should be targeted specifically.

v4.5.0.1

v4.5.0.1 had 1 improvement.

Improvements

• Due to Marketo deprecating the endpoint Brightspot uses to submit forms from the CMS to Marketo, Brightspot has updated the existing MarketoExternalSubmitAction model to use the new endpoint.

Breaking changes

Method signature change:

• brightspot.form.action.Action#tryAction(FormSubmission formSubmission) to #tryAction(FormSubmission formSubmission, Form form). The new Form parameter is the Form containing the Action having #tryAction called.

Model change:

• MarketoExternalSubmitAction no longer needs any instance variables. The actionLink and submitMethod fields have been removed, along with their respective getter and setter methods.

Marketo API Permission change:

• The SubmitForm endpoint requires the Read-Write Lead be added to the role associated with the REST endpoint created in Marketo.

v4.5.0

v4.5.0 had 28 bug fixes, 28 improvements, and 19 new features.

Improvements

• Added a new integration with Microsoft Teams, helping to prevent context switching and facilitate efficiency when working in Brightspot.
• Added a new integration with Google Vision to return metadata on images.
• Added site- and page-level event metrics for Google Analytics.
• Administrators now have a more straight-forward way to set the import settings of Google Analytics data ingestion. Administrators can now define the import frequency by hour and by day, and now have the ability to set a custom import frequency using Cron Expressions.
• Search now has a Board View that allows editors to display results by additional field values. Additionally, the order of assets in Board View has been made more predictable: if the columns are powered by an enum, they will use that order; otherwise, they will be ordered alphabetically.
• In an effort to make type selection easier, faster, and more intuitive, editors now have the ability to “favorite” the things they most often select from dropdown menus and filters. This feature exists on a per-user basis and will bubble up those types/selections to the top of their respective lists. As a result, the “Recently Used” function/section will no longer be used.
• Editors may now also "favorite" content types in the Quick Start widget.
• Editors can now access a “Shared Preview Links” list item in the Profile dropdown, which will show a list of all active preview links, which can then be removed as the sharer sees fit.
• Editors are now able to set permalink rule overrides at the site level versus only at the global level. This is helpful if an editor has, for example, a site that needs its images to have URLs for preview purposes, but also has another site that doesn’t need images to have URLs.
• Editors now have the ability to print search results in CMS search.
• Editors can now quickly search for sites via site categories after accessing Sites & Settings in the CMS, much like they are already able to do with the site switcher.
• Addition of The Shelf, which allows users to drag and drop content directly from a centralized location onto a Page and to see, at a glance, what those draggable items are. The Shelf is available on all landing page content types (Article, Page, Homepage, Section, Tag, etc.) and the Entity Page content types (Corporate, Broadcast, Podcast). It also allows users to drag and drop content into articles to create enhancements.
• Editors now have the ability to add and subsequently set a query field to editorial content types. This query field lives in the UI after accessing the editorial content type to which an editor wants to add it.
• Addition of the Associated Content widget, which can be extended to create new replacements for three existing widgets: the Assignment Content widget, the Pitch Assignments widget, and the Pitch Content widget.
• Editors now have the ability to drag and drop content between columns when using Assignment Desk’s board view. Dragging updates fields with new values when necessary, and changes are captured in revisions.
• Developers may now make back-end customizations to editorial content types in Brightspot using JavaScript rather than only in Java.
• Improved error messaging related to Notifications.
• New content delivery API module with helpers for returning MarkedText from View Models.
• Added rCDA type-specific sort options for inverse indexes.
• Added a new schema version diff feature.
• Added more distinct type names.
• Added ability to sort interface implementations in the GraphiQL explorer.
• Improved editorial content management API and content delivery API ObjectType selection.

Bug fixes

• With sticky search enabled, each keystroke in the Advanced Search field closed and then re-opened the Edit Dynamic Query widget. This defect has been addressed.
• When opening the Edit Query widget from an edit icon, criteria in the Advanced Query field did not affect search results. Improvements

Breaking changes

• As a result of allowing permission system to be consulted from a background task, a number of items were changes and/or removed. Please refer to the ticket named BSP-12398 when seeking more information.
• To allow users the ability to generate a password reset token and send a welcome email from the CMS, the AuthenticationEntityWidgetWriter interface signature has changed to add a new (non-default) method: update(ToolPageContextpage, Object content).
• In abstracting image recognition capabilities in Brightspot, a number of changes were made. Please refer to the ticket named BSP-9242 when seeking more information.
• In improving Google Analytics import settings, on GoogleAnalyticsTaskGlobalSettingsModification, the analyticsImportTaskSchedule field has been deprecated in favor of the new importSchedule field. The data in analyticsImportTaskSchedule is being @Relocate-ed to importSchedule, and any usages of #getAnalyticsImportTaskSchedule() will need to be updated to #getImportSchedule().