v4.2.43 release

v4.2.43 had 15 bug fixes and one improvement.

Significant improvement

• Introduced a code change that dramatically reduced the time required for localizing text in the UI.

Significant defects addressed

• Corrected an issue in which fields annotated with @Where were disabled in the Bulk Edit widget.
• Corrected an issue in which copying Location objects to a Solr database generated a RemoteSolrException.
• Corrected an issue in which importing data from Google Analytics generated duplicate entry and queue full errors.
• Corrected an issue that prevented field notes marked up with <ul><li> to appear as a bulleted list.
• Corrected an issue that prevented correct paging of form submissions.
• Corrected an issue that caused a border to appear in the content edit form when adding tags or authors.
• 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.
• Corrected an issue that caused a blank error message to appear in an editorial content type's rich-text field.
• Corrected an issue that caused a Location field to extend outside its allocated space in the content edit form when the browser's window is narrowed.
• Corrected an issue that prevented deletion of custom content forms when the underlying editorial content type was deleted.
• 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 previewed 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).
• Corrected an issue causing a Query generated by Grouping#createItemsQuery to throw an SQLException when the original Query contained a Query#having predicate.
• Corrected an issue that caused a long error message starting with Multiple entries with same key to appear when creating multiple content forms with the same name for the same underlying content type. (For example, creating a content form named Article1 based on the Article content type, and creating another content form with the same name Article1 for the Article content type.) Starting with this release, such duplicate content forms are flagged with the standard error message Must be unique but duplicate at.
• Corrected an issue that prevented a null-value field annotated with class implementing DynamicField from correctly updating. For example, a field endDate is annotated with @DynamicFieldClass(EndDateDynamicField.class). If endDate is null, its value was never updated even though the method EndDateDynamicField#update required it to do so.