Changelogs

Last Updated: Sep 8, 2023
documentation for the dotCMS Content Management System

LTS dotCMS releases

dotCMS will periodically specify specific product releases as Long-Term Supported (LTS) releases, which will be maintained for a longer period than other dotCMS releases, and which will provide a number of advantages for customers that choose to install them.

dotCMS is committed to the security and stability of our latest LTS versions. In our ongoing efforts to protect users, we have established specific timelines for resolving detected vulnerabilities. Note that the responsibility outlined here concerns vulnerabilities that are relevant to live, supported versions. Users on current LTS versions will benefit from security updates in accordance with our established schedules.

Please see the Long Term Supported Releases page for more information and Current Releases for downloads.

Major Version Current Patch Last Updated End of Life Date
23.10.24 LTS 23.10.24v8 Apr 15, 2024 May 19, 2025
23.01 LTS 23.01.15 Apr 15, 2024 Sep 22, 2024
22.03 LTS 22.03.15 Apr 15, 2024 Feb 11, 2024
21.06 LTS 21.06.14 Feb 23, 2023 Apr 30, 2023
5.3.8 LTS 5.3.8.14 Sep 30, 2022 Sep 30, 2022
5.2.8 LTS 5.2.8.4 Feb 16, 2021 ⚠️ Jun 2, 2022
⌛ Notice: This major version is past its End of Life date and no longer receives updates.

dotCMS 5.2.8.4 LTS

Available: Feb 16, 2021 Demo starter image: 20200219

dotCMS 5.2.8.4 is a minor release which includes several minor improvements, and fixes for several issues in previous releases.

Changes and Improvements in dotCMS 5.2.8.4

  • Improved logging messages for JSON Tool. (#19927 )
  • Improved how the database handles content from deleted users. (#19555)
  • Improved logging messages. (#19566 )(#19621)
  • Streamlined database calls especially related to reindexing. (#18605)
  • Changed `JSOntool.generate` to return velocity by default instead of JSON. The default can be changed to JSON in file `dotmarketing-config.properties` see documentation for more information. (#18505)

Fixes

The 5.2.8.4 release includes fixes for the following reported issue. For a list of issues addressed in dotCMS 5.2.8.4, please visit the dotCMS Github Repository.

  • Fixed an issue that caused an error to appear when content is created in a language that is not the default. (#19854)
  • Fixed an issue that sometimes caused unexpected behavior due to legacy content identifiers. (#19832)
  • Improved error message for files created in site root attempting to use a name already in use. (#19831)
  • Fixed an issue that prevented output when trying to access the descendents of self related content specifically using depth attach to the url. (#19796)
  • Fixed an issue that prevented a thumbnail from showing up for a PDF. (#19753)
  • Fixed an issue that sometimes caused an error when GraphQL was queried via a relationship with another Content Type and the query included a Category field on a File Content Type. (#19728)
  • Fixed an issue that sometimes caused an error when a page was edited in a foreign language but the page only existed in the default language. (#19686)
  • Fixed an issue that sometimes caused permissions to be removed on certain content until the cache is flushed. ( #19608)
  • Fixed an issue that sometimes caused extreme login delays if multipe people are trying to login to the same account at the same time. (#19486)
  • Fixed an issue that sometimes caused existing URL maps on newly upgraded systems to throw an error. (#19452)
  • Fixed an issue which prevented content from appearing when using the advance search option, select, on the Content Search screen.(#19337)
  • Fixed an issue causing the JSONTool to return a single content item instead of a list. (#18505)
  • Fixed an issue that caused push publishing to fail if the VTL file that is being pushed has no content. (#18051)
  • Fixed an issue that sometimes prevented a custom layout included in a push publish from being showing on the reciever.(#19890)
  • Fixed an issue that sometimes caused Google Translate Sub-action to send an error when a valid translation key was used. (#19910)
  • Fixed an issue which could cause an error when upgrading to newer versions of Java 8 (#18927)

To view more information on these and other issues, please visit the dotCMS Github repository.


dotCMS 5.2.8.3 LTS

Available: Jul 23, 2020 Demo starter image: 20200219

dotCMS 5.2.8.3 is a maintenance release which fixes a number of issues in earlier versions of the 5.2.x release series. It does not contain any new features, and does not include changes to any underlying structures from the 5.2.8.0, 5.2.8.1, or 5.2.8.2 releases, so customers upgrading from earlier versions of 5.2.8 can upgrade to this release with no change to dotCMS operation or content.

Fixes

The 5.2.8.3 release includes fixes for a number of reported issues. For a list of issues addressed in dotCMS 5.2.8.3, please visit the dotCMS Github Repository.

  • Fixed an issue which could cause vanity URL's to stop working after intense traffic. (#18364)
  • Fixed an issue where dotCMS created an unusable file asset name by replacing spaces in file asset name with the wrong character. (#18214)
  • Fixed an issue which caused key/value fields in a content type to be put in a random order. (#18479)
  • Fixed an issue that could prevent an indexed binary field in a file asset to be edited. (#18369)
  • Fixed an issue that prevented concurrent acess to the Felix Bundle Cache in clustered enviroments. (#18319)
  • Fixed issues that prevented the Content API from working when retrieving the related parents of a given contentlet based on its corresponding relationship. (#18525)
  • Fixed an issue the could prevent a user from sucessfully initiate a bundle from OSGI. (#18501)
  • Fixed an issue which could cause push pulishing issues with files that were batch uploaded via WebDAV. (#18626)
  • Fixed an issue that could cause push publishing to fail with the incorrect error message. (#18621)
  • Fixed an issue that caused a relationship to have a new id when it was converted from an old relationship to a new field based relationship. (#18616)
  • Fixed an issue which could cause logging error when reindexing an instance.(#18072)
  • Fixed an issue which could cause the reindexing process to fail due to data inconsistencies. (#18673)
  • Fixed an issue that could cause content types with more than 2 relationship fields to produce an error in the console.(#18764)
  • Fixed an issue that prevented the endpoint '/v1/folder/sitename/(siteName)/uri/(uri : .+)' to work when passing a URI parameter. (#18848)
  • Fixed an issue that caused a permission error when submitting a form. (#18292)
  • Fixed an issue that could cause aliases to not be recognized and therefore default to the default site. (#18187)
  • Fixed an issue that could cause push publishing errors when a piece of content is manually archived in the recieving endpoint. (#18920)
  • Fixed an issue that could prevent the Folder API from returning the /System folder correctly during a reindex. (#18951)
  • Fixed an issue that diallowed Golbal URLMaps by preventing a free-form url from being entered in the content type's detail page. (#18744)
  • Fixed an issue that could prevent containers to not display any content. (#18855)
  • Fixed issue that could cause errors to appear when invalid identifiers were used for customers using a version of dotCMS before 2.5x.

To view more information on these and other issues, please visit the dotCMS Github repository.

Additional Changes and Improvements in dotCMS 5.2.8.3

  • Added endpoint to the REST API to support viewing the folder tree. (#18314)
  • Removed 10,000 contentlet limit from the Content Export tool. (#18641)
  • Updated MonitorResource to consume less resources. (#18245)

On this page

×

We Dig Feedback

Selected excerpt:

×