v4.7.23 release

v4.7.23 had one new feature, five improvements, and 46 bug fixes.

Significant new feature

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

Significant improvements

• Improved display of filter labels for integer type fields, improving clarity.
• Improved filter clearing functionality in CMS search so that it works as intended.
• Added support for different basic authentication credentials for different developer functions.
• 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 was resulting in a 404 error.

Significant defects addressed

• Fixed an issue where cms.ui.cluster had stopped working when creating sets of front-end fields.
• Fixed an issue where PrePublishAction.shouldDisplay did not take editorial information into account.
• Fixed an issue when adding images to a gallery set to grid view causing the the page focus to become stuck and cut off part of the page.
• Fixed an issue when creating a nested table that caused table icons to overlap.
• Fixed an issue preventing changes to data that was relocated from one module type to another from persisting after the first save action.
• Fixed RCIG Actions menu (swap module, copy module) accessibility labels.
• Added functionality to the checkmark box that appears in combo inputs sections so that it works as expected.
• Corrected an issue when viewing a previous revision that prevented the Name Revision and Compare to Live links from being aligned properly.
• Resolved an issue where the Scheduled Events Widget pop-up for a single day showed more items than expected.
• Addressed stack overflow issue that occurred when saving content templates.
• Fixed an issue preventing the Watcher query restriction from working properly on the Associated Content widget.
• Resolved an issue by increasing the Lingotek connector locale limit from 300 to 1000.
• Fixed an issue when translating a content type that caused the information and error messages to be displayed on top of one another.
• Resolved an issue that at times prevented Preview to Edit from working.
• Corrected an issue where a WIP message was being 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.
• Improved accessibility by ensuring that screen readers read out full dates instead of abbreviating the days of the week or leaving off exact dates.
• Upgraded certain dependencies to a new version of Zookeeper to eliminate an earlier version's vulnerability.
• 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.
• Resolved an issue where interactive controls were missing a programmatic role.
• Fixed an issue of status messages not being announced by screen readers.
• Fixed an issue where controls had accessible labels that were inaccurate or incomplete.
• Fixed an issue in which disclosures were not following the expected pattern when a user navigates to a page.
• Fixed an issue where the form field errors were not properly defined.
• Fixed an issue causing interactive controls to require a mouse to operate.
• Fixed an issue where some controls had inaccurate programmatic roles.
• Corrected an issue where some controls had names that were unnecessarily verbose.
• Corrected an issue where list boxes were missing a programmatic name.
• Fixed an issue where paging was broken on Adobe Stock images search results.
• Corrected an issue that allowed a tag to select itself as a parent tag.
• Fixed an issue in which the images that are dragged from the Shelf were appearing in the wrong order.
• Resolved performance issues on content edit pages that had large amounts of embedded records.
• Fixed an issue caused by ViewModel#getModel previously being introduced as a getter method. This fix introduced a breaking change. See "Breaking changes" below.
• Resolved an issue where new revisions and revisions being edited were using different logic.
• Fixed an issue preventing links from working as intended if surrounded by underline tags.
• Fixed an issue where invalid endpoints were leading to watcher API errors.
• Fixed an issue where assets that were removed from a collection via the toggle were not actually being removed until the user refreshed the page.
• Fixed an issue preventing Brightcove from supporting multi-word search text.
• Fixed an issue where preview would at times experience slowness after an upgrade.
• Fixed an issue at times preventing the rich text editor toolbar from sticking to the top of the page when scrolling.
• Fixed an issue causing the caption field, when included in a CMS search, was returned multiple times instead of once.
• Resolved an issue preventing editorial content types from being 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.
• Improved exception handling so that the behavior is different depending on implementation (i.e., whether an exception is logged or thrown), with an emphasis on having exceptions thrown in GraphQL and other headless implementations.
  

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.