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 |
dotCMS 5.3.8.14 LTS
Available: Sep 30, 2022 Demo starter image: 20200909
Bugfixes
- Copy Site copies all content; previously, the process encountered a silent cap at 10,000 items due to limits on indexes and Elasticsearch queries. [#22520]
- Copying a folder containing a page no longer copies the content displayed in that page's containers. [#22763]
- Workflow changes save properly for all users, including new users or users with special characters in their name. [#22696]
- Static Push Publishing no longer fails when pushing certain Base Content Types when a default language other than English is set. [#22266]
- Corrected issue that prevented limited users with sitewide viewing permissions from viewing content not explicitly permitted for their role. [#22237]
- Revamped push-publishing of users: It is now possible to push an individual user instead of all users, and interface labeling is clearer throughout. [#22149]
- Users with Front-End and Back-End permissions logged in to the front end are no longer redirected automatically to the same page in (Back-End) Edit Mode after manual URL entry. [#22124]
- Pushing a single piece of archived content no longer directly affects — i.e., unpublishes — other versions of the same content. [#21624]
- Removed performance drag from supporting on-the-fly configuration changes via file watchers and other blocking patterns, which are unsuited to a containerized paradigm. [#21619]
- Updating a Binary field via REST API no longer removes the value from other Binary fields in the same contentlet. [#21482]
- Switched to using Tomcat's
RemoteIpValvefor DNS resolution. [#19569] - A Content Type having a many-to-many relationship to itself will no longer cause contentlets to lose their many-to-many relationships under certain conditions. [#20491]
$dotcontentviewtool respects the passedlanguageIDand no longer returns the wrong language in certain situations. [#19774]
dotCMS 5.3.8.13 LTS
Available: Jul 5, 2022 Demo starter image: 20200909
Bugfixes
- Dispatcher now correctly sets servlet URI request parameter, preventing errors in certain Velocity calls.
- New URI normalization filter has been made less aggressive, and now plays nicely with slashes and equals signs.
dotCMS 5.3.8.12 LTS
Available: Jun 29, 2022 Demo starter image: 20200909
Bugfixes
- Bad results on ShortyIdentifier database calls are no longer cached. This prevents a condition in which a database error could result in persistent 404 status for ShortyIDs until their region is flushed.
dotCMS 5.3.8.11 LTS
Available: Jun 10, 2022 Demo starter image: 20200909
As a late-stage LTS build, dotCMS 5.3.8.11 consists chiefly of bugfixes and corrections. One such correction concerns its end-of-life (EOL) date. While longstanding policy holds that LTS releases are supported for 18 months, several recent releases had listed an EOL date 24 months out from original launch. This error was recently corrected; the 18-month EOL mark for 5.3.8 was June 3, 2022, which has now passed.
We realize that some users may have made plans around the erroneous EOL, and we apologize for this oversight. Accordingly, we have elected to extend support for 5.3.8 until at least September 30, 2022, with a possible further extension pending review. dotCMS always reserves the right to extend the EOL date for any release if we believe that we can continue to apply updates without affecting its stability.
Please note that “end of life” does not mean “end of service”; customers with access to the dotCMS Helpdesk can always ask for support on any dotCMS release, including those past their EOL.
Bugfixes:
- Pages built with URL Mapped content are now correctly created on a full-site Static Push.
- URL Mapped content likewise shows up properly in site search indices when including folders.
- Fixed a case where specific conditions could cause drafted content to fail to Push Publish.
- Changes to SCSS files are now recognized and processed immediately, without any delays from caching behavior.
- Fixed navigation error affecting users with both
Back-End UserandFront-End Userroles; URLs now update correctly when editing multiple page assets sequentially. - When a Site/Folder field is removed from a Content Type, content of that type will continue to live where it was originally placed, rather than move to
SYSTEM_HOST. - Fixed issue in which dotAsset titles would display as their identifiers on certain admin panel searches.
- When creating rules, users can now choose the session attribute keys to use to evaluate conditions, such as whether a session attribute exists.
- Contentlet buttons no longer fail to display on Edit Mode with an Edit Mode Anywhere page.
Content:
- Removed limit on number of widgets or forms displayed in Content Selector popup.
Enhancements:
- In Edit Mode, added lazy loading for buttons when editing contentlets within a page.
- Minor style improvements to Edit Mode.
dotCMS 5.3.8.10 LTS
Available: Mar 8, 2022 Demo starter image: 20200909
dotCMS 5.3.8.10 is a LTS release which includes several improvements, and fixes for several issues in previous releases.
Fixes
The 5.3.8.10 release includes fixes for the following reported issues.
For a list of issues addressed in dotCMS 5.3.8.10, please visit the dotCMS Github Repository.
| Issue | Github Link |
|---|---|
| Obfuscate Environmental Variables System Info Portlet | #20757 |
| SAML - Allow expression substitution from SAML roles mapped to dotCMS roles by role key | #20773 |
| Unable to push publish user | #20805 |
| Past Time Machine not working | #21097 |
| [Site Copy] : Copying a Site randomly fails | #21204 |
| Add the ability to stop/abort a workflow on velocity script actionlet | #21252 |
| [Push Publishing] : Single quote in content's title breaks JavaScript code in the portlet | #21699 |
| Sanitizing file name | #21791 |
dotCMS 5.3.8.9 LTS
Available: Jan 18, 2022 Demo starter image: 20200909
dotCMS 5.3.8.9 is a LTS release which includes several improvements, and fixes for several issues in previous releases.
Fixes
The 5.3.8.9 release includes fixes for the following reported issues.
For a list of issues addressed in dotCMS 5.3.8.9, please visit the dotCMS Github Repository.
| Issue | Github Link |
|---|---|
| [Static Publishing] : Problem with multi-language contents | #21537 |
dotCMS 5.3.8.8 LTS
Available: Jan 13, 2022 Demo starter image: 20200909
dotCMS 5.3.8.8 is a LTS release which includes several improvements, and fixes for several issues in previous releases.
Fixes
The 5.3.8.8 release includes fixes for the following reported issues.
For a list of issues addressed in dotCMS 5.3.8.8, please visit the dotCMS Github Repository.
| Issue | Github Link |
|---|---|
| Revert bad commit | #19842 |
dotCMS 5.3.8.7 LTS
Available: Jan 11, 2022 Demo starter image: 20200909
dotCMS 5.3.8.7 is a LTS release which includes several improvements, and fixes for several issues in previous releases.
Fixes
The 5.3.8.7 release includes fixes for the following reported issues.
For a list of issues addressed in dotCMS 5.3.8.7, please visit the dotCMS Github Repository.
| Issue | Github Link |
|---|---|
| Update log4j to 2.17 | #21441 |
| Content Export tool is not exporting relationships correctly | #20746 | Push publishing sometimes changes the order of contentlets in the multi-tree table on multilingual pages | #21313 | 200 redirects to external links are not rendering properly | #21198 | Large Bundles make the viewing publishing queue slow | #20971 | Delete All Bundles does not really delete all bundles | #20812 | Contentlets with future publish date prevent it from being Push Published | #20765 | [Reindex] : Perform Site check before Folder check | #20722 | "Login As" Data Constraints | #20721 | NPE on tags via graphql if no tags present | #20719 | [Vanity URL] : Missing parameters in Vanity URL cause problems in API | #20685 | IndexPolicy do not respected on wf toolview | #20649 | Tika failing to init, hanging dotCMS startup | #20640 | Container displays Add button twice under specific situations | #20623 | Button for Navigation Reorder is not working correctly | #20616 | Class in rows are lost when you remove a row | #20519 | Error retrieving content references in multilingual setup | #20494 | Concurrency Issues with loadPermission | #20464 | Unable to load very large images | #20446 | [Content] : Many to One relationship not displaying in Content Search | #20399 | Large bundles can take too long for load balancers | #19321 |
dotCMS 5.3.8.6.2 LTS
Available: Dec 13, 2021 Demo starter image: 20200909
dotCMS 5.3.8.6.2 is a LTS release which includes several improvements, and fixes for several issues in previous releases.
Fixes
The 5.3.8.6.2 release includes fixes for the following reported issues.
For a list of issues addressed in dotCMS 5.3.8.6.2, please visit the dotCMS Github Repository.
| Issue | Conditions | Github Link |
|---|---|---|
| Log4j2 zero day exploit | https://nvd.nist.gov/vuln/detail/CVE-2021-44228. | #21393 |
| Make userId immutable. | Once a user object has been created/inited, you should not be able to edit the userId.. | #21392 |
| Upgrade log4j version to permit JsonLayout custom key-value pairs. | Allows key-value pairs in Json for k8s and docker. | #20792 |
dotCMS 5.3.8.6.1 LTS
Available: Oct 7, 2021 Demo starter image: 20200909
dotCMS 5.3.8.6.1 is a LTS release which includes several improvements, and fixes for several issues in previous releases.
Improvements in dotCMS 5.3.8.6.1
- Improved error message for deleting a container used by a template. (#20277)
- Added the option to choose what fields are shown in a relationship field's overview. (#19215)
- Added automatic deletion of old inactive Elastic Search indices to prevent performance slowdowns. (#19931)
- Added header identifying what vanity URL directed the user to the page to help simplify debugging. (#20416)
- Improved how external caches and the dotCMS internal cache interact. (#20412)
- Improved error messages for WorkflowAPIImpl. (#20636)
- Edit Mode Anywhere now always expects UTF8. (#20629)
- Improve concurrency issues.(#20507)
- dotCMS is now fully ARM supported. (#19192)
- The cache is now flushed when the push publishing filter files are changed. (#19152)
- Additional GraphQL logging was added. (#20764)
- Warning log messages were updated when the user is lacking permissions to view a catagory associated with the contentlet.(#20801)
- The ability to customize TinyMCE and set it systemwide is now part of dotCMS. (#19651)
Fixes
The 5.3.8.6.1 release includes fixes for the following reported issues.
For a list of issues addressed in dotCMS 5.3.8.6.1, please visit the dotCMS Github Repository.
| Issue | Conditions | Github Link |
|---|---|---|
| Workflow modal failed to open in certain circumstances. | Only occured when selecting available workflow actions for all content in the content search for the content type, date, with more than 40 results. | #19677 |
| Subfolders in the site browser were not in alphabetical order in certain circumstances. | Only occured when a folder's name was changed. | #20104 |
| An infinite loop sometimes happened for specific vanity URLs. | Only occured when the vanity url had a 301/302 HTTP redirect from a URL with a trailing slash to the same url with no trailing slash. | #20280 |
| Unexpected behavior was happening when statically pushing some file assets. | Only occured when the file asset name had spaces in it. | #20295 |
| Workflow could not be copied in certain circumstances. | Only occurred when the Notify Assigned action was included in the workflow. | #20501 |
| URL field values were not included in pages in certain situations. | The URL field values were not included when the page was exported from Content->Search. | #20405 |
| Error sometimes occured when deleting or moving a field in a Content Type. | Only occured for some fields when they were related to another field. | #20342 |
| Copy workflow button sometimes resulted in incorrect next steps. | Only occurred sporadically. | #18111 |
| An error would sometimes occur for sites with lots of cookies. | Only occured when either of the following properties were set as shown below: COOKIES_HTTP_ONLY=TRUE or COOKIES_SECURE_FLAG=always/https. | #20334 |
| User with frontend permissions was sometimes seeing blank pages in certain situations. | Only occurred the user also had backend permissions. | #20452 |
| The page API was sometimes returning the wrong publish date in its JSON. | Only occurred when the page contained a contentlet with the publish date field. | #20791 |
| Problems trying to login from a PC.. | Only occured when MSSQL as the DB | #20499 |
| IPUtils was sometimes returning false incorrectly. | Only occurred when a specific IP utilizing a was passed in. | #20578 |
| Settings were sometimes not respected when an image was inserted into the WYSIWYG. | Only occurred when WYSIWYG_IMAGE_URL_PATTERN was set on the image. | #20642 |
| The User Resources endpoint wasn't parsing some parameters correctly. | Occured when the parameters includeAnonymous and includeDefault parameters were not being respected. | #20450 |
| A Workflow Scheme was not always able to be imported. | The issue only occured when the next assign or permission role did not exist. | #20488 |
| Elastic search was sometimes getting overwhelmed with index requests. | Only occured in clustered environments when doing a full reindex, bulk repermissioning or unding the definition of a major content type. | #20568 |
| The "Site or Folder" field dropdown sporadically disappeared. | Only occured for some content types in edit mode. | #20270 |
| dotCDN was not invalidating the correct information on prod ion certain situations. | Issue occurred when push publishing data that had been invalidated on auth. | #20690 |
| Date was sometimes parsed incorrectly in certain situations. | Issue occurred when a bundle was being created.. | #20766 |
| Users would sometimes see a multilingual site in the wrong language. | Occurred when the site was static and the default language was selected. | #20469 |
| Hanginging on the front end was sometimes experienced. | The error only occurred when a user was creating multiple independent SCSS files that were compiled separately using a build in compiler. | #18301 |
dotCMS 5.3.8.5
LTS
Available: May 20, 2021 Demo starter image: 20200909
dotCMS 5.3.8.5 is a release which includes several improvements, and fixes for several issues in previous releases.
Announcements, Deprecations and Breaking Changes
- A Breaking Change was caused by having the secure flag set on cookies sent securely and having the httponly flag set on all cookies. This could cause issues when updating from a previous version. See Improvements in dotCMS Section for more information.
Improvements in dotCMS 5.3.8.5
- Increased security when sending cookies. (#20063)
- Made the password reset feature more robust by removing the use of a token. (#19877)
- Improved resiliency to rules in push publishing, minimizing errors. (#19679)
- Added the ability to override `portal.properties` attributes with environmental variables(#20068)
- Allow mail session to be configured via environmental variables.(#19813)
- Improved error messages for Integrity Checker when fixing a File Asset conflict. (#20232)
- In Push Publishing improved error message when finding unique content after looking for a content match.(#20250)
- Improved JSON parsing.(#20164)
Fixes
The 5.3.8.5 release includes fixes for the following reported issues.
For a list of issues addressed in dotCMS 5.3.8.5, please visit the dotCMS Github Repository.
| Issue | Conditions | Github Link |
|---|---|---|
| User permissions were not acting as expected | Occurred when the user has a content type tool group permission. | #20156 |
| The "Send an Email" sub-action fails if executed before "Save content" sub-action | This failure only occurs when the Send email sub-action is used before the Save content sub-action. | #19993 |
| Cluster IDs containing underscores were causing errors | This occured when the cluster ID had a underscore | #20122 |
| Anonymous users couldn't fire specific actions when calling the Workflow API | This only occured when the specific action ID was used to execute that action. | #20053 |
| Invalid time zones were available for customers to use causing errors | Errors happened when an invalid timezone was chosen in the Basic Config tab of the Configuration Screen. | #20013 |
| Performance issues in GraphQL | Occurred when the server was under extreme load. | #19974 |
| Page was not able to be published when specific content was added | Occured when the content added to the page had a future push publish date. | #19511 |
| Error showed on every page request | Showed when `ENABLE_NAV_PERMISSION_CHECK` was set to true in `dotmarketing-config-ext.properties`. | #19926 |
| Timezone configuration was not being respected | Occured when using date time fields. | #19951 |
| Re-adding parent relationship in certain situations threw an error | Happened when a parent relationship was removed then re-added. | #19913 |
| Errors showed when running a time machine snapshot | Occurred when trying to run a past time machine snapshot. | #20041 |
| Error was sometimes thrown when Elastic Search was used | Happened intermittently often with memory or network issues. | #19992 |
| Error occured in log file and action didn't occur when remove was selected for push publishing | Happened intermittently specifically in when using the push publish modal. | #19992 |
| SAML Authentication created a new user instead of logging someone in. | Happened intermittently specifically when the SAML user ID was different from the user ID in dotCMS. | #20189 |
| Could not relate content to a macrolanguage | Happened when the same language already had a country code. | #20197 |
| Warnings would occur due to dates formated as text | Only occured when date fields were indexed as text fields. | #20252 |
| Only ten related parent contents retrieved when looking at a child content | Only occured for legacy relationships. | #19723 |
| Permission individually on a folder defaulted to all permissions not just the inheritable permissions | Happened intermittently. | #19412 |
| Could not open edit content screen in certain situations | Only occured when a user has specified a field that does not exist in their pattern. | #20147 |
| Portlets were not reloading when site was changed | Only occured a user changed the site in the top-right selector. | #19842 |
| Endpoint were sometimes returning a bad exception | Only occured when bad XML was posted to Content Resource | #20364 |
| dotCMS containers could have outputed sensitive informative in specific cases | Only occured when settings were defined with enviroment variables. | #20276 |
| SQL Vulnerability in certain areas. | Only vulnerable in containers api. | #19500 |
dotCMS 5.3.8.4 LTS
Available: Feb 16, 2021 Demo starter image: 20200909
dotCMS 5.3.8.4 is a minor release which includes several minor improvements, and fixes for several issues in previous releases.
Additional Changes and Improvements in dotCMS 5.3.8.4
- Added a "Download" button to the Log Files tab in the Maintenance portlet. (#19560)
- Improved logging messages for JSON Tool. (#19927 )
- Improved how the database handles content from deleted users. (#19555)
- Improved logging messages. (#19566 )(#19621)
- Increased the speed of the CVS Importer tool. (#19536)
- Updated the logout for SAML users to return users to a new logout page.(#19098)
- Improved error message for files created in site root attempting to use a name already in use. (#19831)
- 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.3.8.4 release includes fixes for the following reported issue. For a list of issues addressed in dotCMS 5.3.8.4, please visit the dotCMS Github Repository.
- Fixed an issue which sometimes caused unpublished related content to appear in Preview Mode / Live mode when pushed to a static site. (#19044)
- Fixed an issue that sometimes prevented GraphQL from retrieving image information. (#19449)
- Fixed an issue which caused contentlets to return in a lucene query even if they do not have the tag searched for. (#19458)
- Fixed an issue that sometimes caused push publishing to fail due to file-based containers. (#19497)
- Fixed an issue that sometimes prevented contentlets from returning in a query when it had a unique text field that included dashes. (#19489)
- Fixed an issue that sometimes prevented the Network tab on dotCMS instances from responding. (#19547)
- Fixed an issue that prevented parameters from being passed when a 301 or 302 vanity URL was used. (#19564)
- Fixed an issue that sometimes caused the Content API to not return the name or title when ID was entered in the call. ( #19639)
- Fixed an issue that sometimes caused bundling to fail when content was added to a bundle and a user tried to push or download the bundle. ( #19636)
- Fixed an issue that sometimes prevented content from being push published when it was manually selected. (#19571) ( #19634)
- Fixed an issue that prevented a user from logging into saml if the user id has special characters. (#19773)
- Fixed an issue that sometimes caused an error when a user defined a new content type with a variable name that was the same as a default variable used on the backend. (#19725)
- 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)
- 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)
To view more information on these and other issues, please visit the dotCMS Github repository.
dotCMS 5.3.8.2 LTS
Available: Nov 19, 2020 Demo starter image: 20200909
dotCMS 5.3.8.2 is a maintenance release which fixes a number of issues in earlier versions of the 5.3.x release series. It does not contain any new features, and does not include changes to any underlying structures from the 5.3.8 release, so customers upgrading from earlier versions of 5.3.8 can upgrade to this release with no change to dotCMS operation or content.
Fixes
The 5.3.8.2 release includes fixes for a number of reported issues. For a list of issues addressed in dotCMS 5.3.8.2, please visit the dotCMS Github Repository.
- Fixed an issue which could reorder fields in a content type. (#18834)
- Fixed an issue which caused the wrong filter name to show in the bundle details. (#19075)
- Fixed an issue which prevented push publishing filters from showing up until the server was restarted. (#19152)
- Fixed an issue which prevented the list from refeshing after an image was uploaded. (#19335)
- Fixed an issue that could prevent GIF files from showing up correctly on the backend. (#19338)
- Fixed an issue that caused a SQL injection vulnerability for the endpoint /api/v1/containers. (#19500)
- Fixed issues that prevented the custom layout from refreshing after saving changes. (#19165)
- Fixed an issue that prevented the Upload New File button from working in image or file fields. (#19181)
- Fixed an issue which could prevent a limited user from editing catagories. (#19267)
- Fixed an issue that could cause multiple issues in edit mode when adding content on a page. (#19304)
- Fixed an issue that blocked the api call to the secret store. (#19302)
- Fixed an issue which sometimes caused problems with GraphQL when running a cluster. (#19255)
To view more information on these and other issues, please visit the dotCMS Github repository.
