v4.5.30 release

v4.5.30 had one new feature, one improvement, and 11 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.

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

Significant defects addressed

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