ChangeLogs documentation for the dotCMS Content Management System

This page displays information about the changes in each of the following recent dotCMS releases:

Latest Long Term Supported (LTS) 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.

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

VersionRelease DateEnd of Life Date
dotCMS 21.06.3 Sep 13, 2021 Mar 13, 2023
dotCMS 5.3.8.5 May 21, 2021 May 21, 2022

Agile releases

Rows with the icon: are Breaking Change Releases. This means that upgrading to this version will require extra testing and possible architecture updates.

Please see Current Releases for downloads.

VersionRelease DateEnd of Life Date
dotCMS 21.06.3 Sep 13, 2021 Mar 13, 2023
dotCMS 21.09 Sep 8, 2021 Sep 8, 2022
dotCMS 21.08 Aug 5, 2021 Aug 5, 2022
dotCMS 21.06 Jul 6, 2021 Jul 6, 2022
dotCMS 21.05.1 Jun 9, 2021 Jun 9, 2022
dotCMS 5.3.8.5 May 21, 2021 May 21, 2022
dotCMS 21.04 Apr 26, 2021 Apr 26, 2022
dotCMS 21.03 Mar 16, 2021 Mar 16, 2022
dotCMS 21.02.2 Feb 26, 2021 Feb 26, 2022
dotCMS 5.2.8.4 LTS Feb 17, 2021 Jun 3, 2022
dotCMS 5.3.8.4 LTS Feb 17, 2021 Jun 3, 2022
dotCMS 21.01 Jan 11, 2021 Jan 11, 2022
dotCMS 20.11.1 Dec 3, 2020 Dec 3, 2021
dotCMS 20.11 Nov 24, 2020 Nov 24, 2021
dotCMS 5.3.8.2 LTS Nov 20, 2020 Jun 3, 2022
dotCMS 20.10.1 Nov 5, 2020 Nov 5, 2021
dotCMS 5.3.9 Oct 8, 2020 Aug 8, 2021
dotCMS 5.3.8 Sep 18, 2020 Jun 3, 2022
dotCMS 5.3.7 Aug 26, 2020 Aug 26, 2021
dotCMS 5.3.6.1 Aug 14, 2020 Aug 14, 2021
dotCMS 5.3.6 Aug 12, 2020 Aug 12, 2021
dotCMS 5.3.5 Jul 29, 2020 Jul 29, 2021
dotCMS 5.2.8.3 LTS Jul 24, 2020 Jun 3, 2022
dotCMS 5.3.4.1 Jul 22, 2020 Jul 22, 2021
dotCMS 5.3.4 Jul 15, 2020 Jul 15, 2021
dotCMS 5.3.3 Jun 29, 2020 Jun 29, 2021
dotCMS 5.3.2 Jun 15, 2020 Jun 15, 2021
dotCMS 5.3.1 Jun 1, 2020 Jun 1, 2021
dotCMS 5.3.0 May 21, 2020 May 21, 2021
dotCMS 5.2.8 Apr 6, 2020 Jun 3, 2022
dotCMS 5.2.7 Mar 9, 2020 Mar 9, 2021
dotCMS 5.2.6 Feb 21, 2020 Feb 21, 2021
dotCMS 5.2.5 Feb 7, 2020 Feb 7, 2021
dotCMS 5.2.4 Jan 24, 2020 Jan 24, 2021
dotCMS 5.2.3 Jan 3, 2020 Jan 3, 2021
dotCMS 5.2.2 Dec 13, 2019 Dec 13, 2020
dotCMS 5.2.1 Nov 7, 2019 Nov 7, 2020
dotCMS 5.2.0 Oct 7, 2019 Oct 7, 2020
dotCMS 5.1.6 Jun 6, 2019 Jun 6, 2020
dotCMS 5.1.5 May 9, 2019 May 9, 2020
dotCMS 5.1.1 Mar 26, 2019 Mar 26, 2020
dotCMS 5.1.0 Mar 14, 2019 Mar 14, 2020
dotCMS 5.0.3 Nov 15, 2018 Nov 15, 2019
dotCMS 5.0.2 Sep 20, 2018 Sep 20, 2019
dotCMS 5.0.1 Aug 21, 2018 Aug 21, 2019
dotCMS 5.0.0 Aug 8, 2018 Aug 8, 2019
dotCMS 4.3.3 Apr 20, 2018 Apr 20, 2019

For information on earlier releases, please see the Previous ChangeLogs documentation.

dotCMS 21.06.3

Available: Sep 13, 2021

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

Announcements, Deprecations and Breaking Changes

  • Breaking Change: The rest call /api/v2/users no longer exists please use /api/v1/users instead. Any use of /api/v2/users needs to be replaced.

Improvements in dotCMS 21.06.3

  • Improved error messages for WorkflowAPIImpl. (#20636)
  • 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)
  • Made multiple improvements to Site Resource. (#20557)
  • A bulk move action is now available on the content search screen. (#20504)
  • License.zip files will not be moved, rewritten or duplicated on startup.(#20591)
  • Moved to glibc based Docker image from a musl based Docker image. (#20666)
  • Edit Mode Anywhere now always expects UTF8. (#20629)

Fixes

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

Issue Conditions Github Link
Duplicates of the same language were allowed to be created. A language should not be able to be created if a language with the exact same values already exist. #7342
In specific situations the network information did not show on the network tab and an error was produced. Only occurred when a license was applied for the first time and the network tab was navigated to right after. #20647
IPUtils was sometimes returning false incorrectly. Only occurred when a specific IP utilizing a \ was passed in. #20578
Users sometimes were unable to create a multilingual blog. Only occurred on the populate content for language page where the default content is shown. #20505
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
User couldn't view or edit a piece of content when it has certain multilingual properties. Only occurred when that content referenced a non-default language on a page that didn't exist in the default language. #20494
Copy workflow button sometimes resulted in incorrect next steps. Only occurred sporadically. #18111
Generating a resource link for file assets in certain circumstances failed. Only occurred when the file asset had a legacy identifier. #20597
Contentlet sometimes failed to render and threw an error in certain cases. Only occurred for content that had a file or image in its Content Type and the file/image was not published when the user was viewing the page. #18014
The add content button was sometimes showing up twice when adding or moving content in a specific container. Only occurred the dotCMS instance had legacy data. #20623
Update site was not correctly updating the aliases. This occurred when you Updated the site via the REST call. #20638
In certain situations when running containerized dotCMS initialization was getting stuck. Only occurred when new nodes were coming up and Tika was trying to initialize. #20640
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
Widgets index policy on a page was sometimes overridden by the default. Only occurred when an index policy was set in a code snippet widget on the page. #20649
Error was created when certain response header rules were set. Only occurred when the header required single quotes. #20659
Users were not allowed to push publish in another time zone in certain situations. Occurred when the user was trying to push publish in another timezone at a time that has already past in there current timezone. #20674
Users were able to login as all users in certain situations. Occurred when a user did not have login as permissions but were still able to use it. #20677
Vanity URLs could be created without required data. The vanity URL could be created without the title and the forward to field filled in. #20685
Site name was not able to updated a specific way. Issue occurred when trying to update a site name via the Update Site REST call. #20688
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
Error occurred when upgrading to 21.06 with a specific dotCMS setup. Issue occurred when a managed database was being used. #20725
OutOfMemoryError occurred when the user tried to import a Bundle Occurred when many events were triggered at the same time. #20799
Users would sometimes see a multilingual site in the wrong language. Occurred when the site was static and the default language was selected. #20469
Pulling tags with GraphQL returned an error in logs in specific circumstances. The error only occurred there were no tags existing. #20719
Classes assigned to rows in layout designer were removed in certain situations. Only occurred when one row in the layout designer was deleted all the rows below it would be effected. #20519
An exception was thrown on a fresh installation of the full starter depending on the database used. The exception was only thrown if MSSQL was used as the database. #20669
Image paths and CSS file paths were sometimes incorrect after a Static Publish or Time Machine run. Only occurred when the image path and dimensions were passed in a code snippet widget. #20707
Running fix conflicts after running an integrity check caused errors in specific situations. The error only occurred when trying to fix folder conflicts. #20714

dotCMS 21.09

Available: Sep 8, 2021

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

Announcements, Deprecations and Breaking Changes

  • Breaking Change: The rest call /api/v2/users no longer exists please use /api/v1/users instead. Any use of /api/v2/users needs to be replaced.

Improvements in dotCMS 21.09

  • Images can be added to a page using drag and drop. (#18411)
  • A downloadable bundle manifest is now available for each bundle. (#20010)
  • Icon picker and sort_order are now available on the content type screen and on the database. (#20426)
  • Created content resource that can be found by id or inode. (#20429)
  • A bulk move action is now available on the content search screen. (#20504)
  • License.zip files will not be moved, rewritten or duplicated on startup.(#20591)
  • Improved error messages for WorkflowAPIImpl. (#20636)
  • Added REST call /api/v1/content (#20429)

Fixes

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

Issue Conditions Github Link
Duplicates of the same language were allowed to be created. A language should not be able to be created if a language with the exact same values already exist. #7342
The search and replace utility was replacing characters with invalid ones on MS SQL Server in certain circumstances Only occurred when the characters being searched and replaced were non latin characters. #18209
Content search card view sometimes wrongly ran in background in certain circumstances Occurred when List view was requested. #19290
Theme selector sometimes failed to return to the home page in certain situations. Issue occurred when a user switches sites while on the theme selector. #19874
Sometimes the images and files were unable to be accessed in the task details page on the task portlet. Occurred when the task details were for a piece of content that was executing a workflow.. #20047
User with frontend permissions was sometimes seeing blank pages in certain situations. Only occurred the user also had backend permissions. #20452
User couldn't view or edit a piece of content when it has certain multilingual properties. Only occurred when that content referenced a non-default language on a page that didn't exist in the default language. #20494
Multiple UI bugs were seen. Bugs were on the content search screen, and the site browser. #20566
Generating a resource link for file assets in certain circumstances failed. Only occurred when the file asset had a legacy identifier. #20597
Reordering navigation items did not always work as expected. The UI was not allowing multiple tasks related to reordering occur. #20616
The add content button was sometimes showing up twice when adding or moving content in a specific container. Only occurred the dotCMS instance had legacy data. #20623
Update site was not correctly updating the aliases. This occurred when you Updated the site via the REST call. #20638
In certain situations when running containerized dotCMS initialization was getting stuck. Only occurred when new nodes were coming up and Tika was trying to initialize. #20640
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
Widgets index policy on a page was sometimes overridden by the default. Only occurred when an index policy was set in a code snippet widget on the page. #20649
Error was created when certain response header rules were set. Only occurred when the header required single quotes. #20659
Users were not allowed to push publish in another time zone in certain situations. Occurred when the user was trying to push publish in another timezone at a time that has already past in there current timezone. #20674
Users were able to login as all users in certain situations. Occurred when a user did not have login as permissions but were still able to use it. #20677
Vanity URLs could be created without required data. The vanity URL could be created without the title and the forward to field filled in. #20685
Site name was not able to updated a specific way. Issue occurred when trying to update a site name via the Update Site REST call. #20688
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
Errors were occurring after a ES reindex under certain circumstances. Issue occurred when the host inode was changed in the database. #20722
Error occurred when upgrading to 21.06 with a specific dotCMS setup. Issue occurred when a managed database was being used. #20725
Content Export Tool was able to export certain contentlets. Issue occurred when the contentlets to be exported didn't have CMS Anonymous access. #20746
Sensitive information was showing in the System Info tab of the dotCMS Maintenance page. Issue occurred system or environmental variables were set for sensitive information. #20757
Reordering items in page menu did not always work as expected. The UI was not allowing multiple tasks related to reordering occur. #20868
Duplicate data was shown in the System Info tab of the dotCMS Maintenance page. Occurs because the old data is never cleared instead the table keeps being appended with the same data. #20757
ReindexThread was filling up the log in certain circumstances. Occurred on 5.2.8.5 #20821
OutOfMemoryError occurred when the user tried to import a Bundle Occurred when many events were triggered at the same time. #20799
Errors were thrown when someone pushed a user. Only occurred when a user pushed multiple users without explicitly adding them to a bundle. #20805

dotCMS 21.08

Available: Aug 5, 2021

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

Announcements, Deprecations and Breaking Changes

  • Breaking Change: dotCMS is moving from away from using Hibernate. If your company uses Hibernate in your custom code you should update it.
  • Breaking Change: dotCMS is moving from Alpine a musl based docker image to Ubuntu LTS a glibc docker image. The minimized Java 11 distribution being used may not contain all the modules you are currently relying on for custom plugins.
  • Breaking Change dotCMS will be completely deprecating support for Java 8 as of this version 21.08 and instead requiring Java 11 to run.

Improvements in dotCMS 21.08

  • Admins can now choose the default view when they create a custom content tool. (#17877)
  • 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)
  • Made multiple improvements to Site Resource. (#20557)
  • Added a short lived cache for the MonitorResource. (#20578)
  • Search and aggregation are now allowed on key/value fields through the REST API. (#20603)
  • Edit Mode Anywhere now always expects UTF8. (#20629)
  • Moved to glibc based Docker image from a musl based Docker image. (#20666)
  • Created a Bash Command Line Interface (CLI) for users to checkout a dotCMS GitHub directory with all Content Types using curl then push that directory to a dotCMS instance. (#20369)
  • Updated legacy data model by replacing HibernateUtil with DotConnect. (#19399) , (#19398), (#19394)

    Fixes

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

    Issue Conditions Github Link
    Contentlet sometimes failed to render and threw an error in certain cases. Only occurred for content that had a file or image in its Content Type and the file/image was not published when the user was viewing the page. #18014
    Images were failing to load and causing an error in certain cases. Only occurred when images were very large. #20446
    Error sometimes happened when using the API to insert content. Only occurred when a large amount of content was inserted at the same time. #20110
    Users would sometimes see a multilingual site in the wrong language. Occurred when the site was static and the default language was selected. #20469
    Contentlets lost their many to many relationships in specific situations. Occurred when the Content Type has a many-to-many relationship to itself. #20491
    Workflow could not be copied in certain circumstances. Only occurred when the Notify Assigned action was included in the workflow. #20501
    Users sometimes were unable to create a multilingual blog. Only occurred on the populate content for language page where the default content is shown. #20505
    Classes assigned to rows in layout designer were removed in certain situations. Only occurred when one row in the layout designer was deleted all the rows below it would be effected. #20519
    IPUtils was sometimes returning false incorrectly. Only occurred when a specific IP utilizing a \ was passed in. #20578
    Creating or copying a site failed in certain situations. Only occurred when using the Add Site button on the Sites Portlet. #20609
    In specific situations the network information did not show on the network tab and an error was produced. Only occurred when a license was applied for the first time and the network tab was navigated to right after. #20647
    No message showed on the search content portlet in specific situations. Only occurred when the content type searched was empty. #20648
    Site Search Job sometimes produced an error and failed to run. Only occurred when the site search was scheduled to run now. #20653
    Image paths and CSS file paths were sometimes incorrect after a Static Publish or Time Machine run. Only occurred when the image path and dimensions were passed in a code snippet widget. #20707
    An exception was thrown on a fresh installation of the full starter depending on the database used. The exception was only thrown if MSSQL was used as the database. #20669
    Copy workflow button sometimes resulted in incorrect next steps. Only occurred sporadically. #18111
    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
    Running fix conflicts after running an integrity check caused errors in specific situations. The error only occurred when trying to fix folder conflicts. #20714
    Pulling tags with GraphQL returned an error in logs in specific circumstances. The error only occurred there were no tags existing. #20719

    dotCMS 21.06

    Available: Jul 6, 2021

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

    Announcements, Deprecations and Breaking Changes

    • dotCMS 21.06 can now run with Java 8 or Java 11 in order to run properly. That said, we expect that within the next 3 months, dotCMS will be deprecating support for Java 8 and instead require Java 11 to run. We will keep the community posted.
    • Many new features have been introduced in 21.06 please see the New Features section to see all the new features.

    New Features

    The following new features have been added in dotCMS 21.06:

    • dotCMS reimplemented the cache networking layer using postgres's pub/sub capabilities and made clustering easier and scaling more resilient.
      • Customers using Postgres will automatically be switched to the new transport on upgrade.
      • This allows postgres installations to cluster without relying on Hazelcast.(#20153)
      • Customers who wish to revert to Hazelcast transport can explicitly configure their cluster transport configuration
    • dotCMS moved Docker images to the core repo and now builds docker images programatically with github action. This does the following:
      • Multi-arch docker images
      • Appropriate tags based on the build information
      • Dockpushes directly to dockerhub.
    • For more information see (#20248)

    Improvements in dotCMS 21.06

    • Enabled the ability to replace dotCMS logo on backend. (#19970)
    • Created a new REST endpoint to return the version of versionables when the identifier is passed in. (#19778)
    • Improved confusing E-mail address used for system and anonymous user. (#20095)
    • Updated GraphQL PageAPI call. (#20203)
    • Introduced new metadata attributes for GraphQL. (#20209)
    • Improved error message for deleting a container used by a template. (#20277)
    • Added the ability to copy a site from a REST call. (#20272)
    • Updated bundle output file type to TAR/GZIP to improve performance. (#20325)
    • Added the ability to specify in the GraphQL query if a given field should be returned velocity-rendered in the response. (#20407)
    • 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)
    • Added the ability to update a site via REST using Site Resource. (#20393)
    • Added ability for Felix load to be overridden by enviromental variables. (#20601)

    Fixes

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

    IssueConditionsGithub Link
    Only ten related parent contents were retrieved when looking at a child content. Only occured for legacy relationships. #19723
    Backend fonts were broken in certain situations. Only occured when there was no internet access. #19980
    Push publishing sometimes didn't respect time zones. Occured when the user's computer time was ahead or behind the server time. #20110
    The user was unable to choose the session attribute key to evaluate a condition in certain situations. Occured when a user made a new rule to check if the session attribute existed. #20153
    Empty starter wasn't starting in certain circumstances. Occured when the default language was changed in the marketing configuration properties. #18766
    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
    Errors in the Users, Sites, Template and Content Types menus happened in specific circumstances. Only occured when the default language was changed in the marketing configuration properties. #20112
    The "Site or Folder" field dropdown sporadically disappeared. Only occured for some content types in edit mode. #20270
    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
    Error sometimes happened when adding content to a page. Only occured when the content added was new and so was the page. #20486
    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
    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
    The link to edit a site configuration in Apps did not work for the entire row The link only failed when not clicking on words. #20304
    The selected push publishing environment didn't always show in the push to field. The environment only failed to show when it had already been selected previously. #20433
    The User Resources endpoint wasn't parsing some parameters correctly. Occured when the parameters includeAnonymous and includeDefault parameters were not being respected. #20450
    Metadata attributes were not always available from all Content Types. The issue only occured when someone tried to get the metadata directly from VTL files. #20457
    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
    The reindex process was sometimes killed before it finished. The issue only occured when the reindex is of a large database that takes more than five minutes. #20607

    dotCMS 21.05.1

    Available: Jun 9, 2021

    Announcements, Deprecations and Breaking Changes

    • This version requires a reindex after upgrade.
    • dotCMS can now run with Java 8 or Java 11.
      • We recommend that all new customers run on Java 11, and that all existing customers running dotCMS 21.05.1 or later migrate to using Java 11 as soon as practical.
      • We expect that support for running on Java 8 will be deprecated before the end of the year. We will keep the community posted.
    • The format of the "metadata" attribute of the contentlet object has changed.
      • Code which accesses values in the metadata attribute may need to be modified to read values in the new format.
      • Please see below for more information.

    New Features

    The following new features have been added in dotCMS 21.05.1:

    • A new tool called Focal Point has been added to dotCMS.
      • This tool allows a focal point to be set for images on the edit screen for images.
      • The Focal Point will draw your customer's eye to the most important area of the image.
      • Once a focal point is set for an image it will be persisted until it is changed.
    • The newly revamped tool Enhanced Inline Editing has been added to dotCMS.
      • This gives content editors the abiltity to edit content directly on the page edit screen as long as they add a specific HTML block to the container.
      • See documentation for more information.
    • A new tool called the GraphQL Playground has been introduced to this version of dotCMS.
      • This tool provides an area for users to test GraphQL calls, and see what would be outputted.
      • The GraphQL playground is available under dev tools.
      • Example data is provided.
    • Doing a headless bulk update is now possible using the workflow fire endpoint.
      • The workflow fire endpoint can now take multiple pieces of content.
      • See the Improvements in dotCMS section for details.
    • Metadata has been greatly enhanced.
      • Metadata now has new data including the data for a focal point along with many others.
      • Metadata caching has been greatly improved. There is now a dedicated cache region for metadata, which may be sized and cleared separately from other cache regions.
      • Metadata in the contentlet object is now returned as a map, instead of a string, allowing access to individual metadata fields without the need to parse a string.
      • For more information, please see the documentation.
    • A System Theme, Container, and Template have been introduced in this version of dotCMS.
      • This gives the ability to create simple headless pages with a brand new instance of dotCMS.

    Improvements in dotCMS 21.05.1

    • Improved push publishing performance.(#19646)
    • Streamlined log by removing uneccessary output.(#20313), (#20317)
    • Added validation type none for SAML.(#20420)
    • The ability to add multiple content pieces when calling the workflow fire endpoint now exists. (#20080)
    • 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)
    • Added copy options for host ID's in app section.(#20135)
    • Improve concurrency issues.(#20507)

    Fixes

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

    20499
    IssueConditionsGithub Link
    Limited user could not retrieve data from User API Occured for many methods in the User API when a limited user tried to call the API. #19731
    GraphQL API was requiring language Only occured when there was multiple languages. #19827
    Portlet was not reloaded even when the site was changed Only occured when the site was changed in the top right corner while on a portlet. #19842
    Some images uploaded to an image field did not show up as images Only occured when the images were uploaded via drag and drop. #19939
    Applying a license on specific browsers was not working Only occured when the user was using Safari. #20097
    Content Type Product broke in specific situations Only occured when it was rendered in the contentlet edit dialog. #20154
    Contentlet state icon was missing in certain situations Only occured in the card view of the content search. #20278
    Loading a starter was creating many errors in log Occured due to internal systems not working that did not need to be in log. #20351
    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
    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
    Endpoint was sometimes returning a bad exception Only occured when bad XML was posted to Content Resource endpoint. #20364
    Garbage collection issues due to Java 11. Only occured when Mockito was used. #20506
    Problems trying to login from a PC.. Only occured when MSSQL as the DB #20499

    dotCMS 5.3.8.5

    Available: May 21, 2021

    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.

    IssueConditionsGithub 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 21.04

    Available: Apr 26, 2021

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

    Announcements, Deprecations and Breaking Changes

    • dotCMS 21.04 still requires Java 8 in order to run properly. That said, we expect that within the next 3 months, dotCMS will be deprecating support for Java 8 and instead require Java 11 to run. We will keep the community posted.
    • Breaking Change: The UserProxy table in the database is now deprecated.
      • The table is still available, but no new data will be added to it starting in this release and the get method will no longer work.
      • The UserProxy table will be removed all together within the next 3 months.

    Changes in dotCMS 21.04

    Push publishing authentication now uses API tokens. This means that it is no longer necessary to configure the “receiver” in a Push Publish architecture, just have a valid admin token.
    • If you are upgrading, any existing push publishing configuration will continue to work normally and will be maintained.
    • There is a `Get Token` utility on the Endpoint screen that can be used to generate and retrieve a valid token from the receiving server.
    • To change Push Publishing Environments to use the "Receive From" configuration instead of automated authorization tokens, set the following `USE_JWT_TOKEN_IN_PUSH_PUBLISH` in the `dotmarketing-config.properties` file to `FALSE`.

    Improvements in dotCMS 21.04

    • Added "Don't show this again" checkbox to Edit User Page.(#20090)
    • Added the ability to override portal.properties attributes with environmental variables.(#20068)
    • Allow mail session to be configured via environmental variables.(#19813)
    • Created a new container called the System Container this container allows all Content Types. (#19080)
    • Improved logging messages for Get Token action in the Add Endpoints tab. (#20194)
    • JSON Tool parsing improvements were added. (#20164)

    Fixes

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

    IssueConditionsGithub Link
    Icon selector didn't recognize value The problem occurred went attempting to paste a value in the icon selector. #20157
    User permissions were not acting as expected Occurred when the user has a content type tool group permission. #20156
    The System Roles screen were showing an error instead of filtering This error occured when the role item itself was clicked on. #20139
    Cluster IDs containing underscores were causing errors This occured when the cluster ID had a underscore. #20122
    Get Token tool sometimes invalidated a user's session Issue occured when adding a new endpoint on the reciever side for Push Publishing, and the Get Token tool was used. #20117
    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
    Logger didn't work for OSGI plugin in specific situations Occurred when the logger was undeployed and redeployed. #20039
    Screen didn't scroll when moving fields on the Content Type page. Occured when dragging and dropping fields. #20020
    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
    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
    Performance issues in GraphQL Occurred when the server was under extreme load. #19974
    Timezone configuration was not being respected Occured when using date time fields. #19951
    Content Type REST API was not accepting field variables This specifically occured when someone attempted to create a single call to create Content Type that includes a WYSIWYG field with tinyMCE field variables. #19376
    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
    Dotcontent viewtool returned the wrong language in certain situations The dotcontent viewtool method, pullRelated, was not honoring the languageId that was passed in. #19774
    URL validation for new pages under Site root was wrong in certain situations This occured when a new page was created with the same name as an existing page. #19831
    Re-adding parent relationship in certain situations threw an error Happened when a parent relationship was removed then re-added. #19913
    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. #19992

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


    dotCMS 21.03

    Available: Mar 16, 2021

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

    Announcements and Deprecations

    • 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.
    • This version of dotCMS ships with Tomcat 9. Any plugins or overrides that specify files in the tomcat directory tomcat-8.5.32 will need to be updated.
    • dotCMS 21.03 still requires Java 8 in order to run properly. That said, we expect that within the next 3 months, dotCMS will be deprecating support for Java 8 and instead require Java 11 to run. We will keep the community posted.

    New Features

    The following new features have been added in dotCMS 21.03:

    • A new Tool called "Getting Started" has been added to dotCMS.
      • The tool will be shown when admins log into dotCMS for the first time.
      • This tool will supply admins with relavant examples and resources to get started with dotCMS quickly and easily.
      • Admins will be able to dismiss this tool if they don't feel they need it.

    Improvements in dotCMS 21.03

    • Added three informational fields to the relationship field popup; direction of the cardinality relationship, is this content the parent or chilld, and what related content type field is this relationship connected to.(#18706)
    • Upgraded security and infrastructure by upgrading to Tomcat 9.(#19241)
    • Included a new "Generate Metadata" button in SAML app.(#19503)
    • Improved personalization in GraphQL to better handle URL maps and personalization.(#19508)
    • Added a "Download" button to the log files tab in the maintenance tool.(#19560)
    • Created a component allowing users to preview material icons before they choose one.(#19592)
    • Improved our infrastructure by upgrading to Gradle 4.10.2 . (#19714)
    • Made XStream initialization static so less resources are now needed. (#19715)
    • Made the password reset feature more robust by removing the use of a token. (#19877)
    • Improved logging in the JSON Tool. (#19927)
    • Increased security when sending cookies. (#20063)

    Fixes

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

    IssueConditionsGithub Link
    Using website navigation while editing a page returned the user to the wrong place The problem occurred under specific conditions when using page navigation in page edit mode. #19737
    Field variable tab on content type showed as in use incorrectly Occurred when the field variable is edited, the window is closed and then the same field is edited again. #19556
    SQL Viewtool was not returning results Occurred in newer versions of dotCMS. #19746
    Thumbnail creater not working for .pdf files A page would have to be specified in the thumbnail link for a thumbnail to show. #19753
    Logout page did not show when active session was left open When an active session was left open without activity for a long time a blank page with 404 in the corner showed. #19772
    Inability to log into dotCMS with SAML When the SAML IDP sent a User ID with the wrong format the issue occurred. #19773
    Errors sometimes occurred when push publishing a bundle Occurred when a bundle was created then immediatly pushed. #19791
    Depth of 3 or more doesn't return for self related content Showed when depth of 3 or more is added to the tail of a self related call. #19796
    Content Type tabs missing frame Occurred when viewing fields or permissions on a content type. #19824
    Error shows for when viewing a page Arose when a limited user tried to create content in a language that isn't the default, then someone tried to view the content in that language. #19854
    Relate button hid in relation content search Occurred when a user scrolled in the relationship content search. #19880
    Google Translate sub action was sending an error Happened when creating a workflow sub action using the "Translate Content subaction. #19910
    Forgot and reset password actions did not show an error Error failed to show when the the password requirements were not met. #19916
    Recover password incorrectly redirected to sign in page Appeared once a recovery email was sent. #19917
    Error showed on every page request Showed when `ENABLE_NAV_PERMISSION_CHECK` was set to true in `dotmarketing-config-ext.properties`. #19926
    Adding a folder to the root directory threw an error Happened when a folder was added to the root direcotry in the site browser. #19934
    Error showed in content type Occurred when a new field was added to the Content Type. #19987
    User prevented from logging out Happened when a logged in tab was closed and opened again. #19991
    Error was sometimes thrown when Elastic Search was used Happened intermittently often with memory or network issues. #19992
    Element stuck to cursor in drag and drop disappeared Showed up in Content Type section when adding a field. #20015
    Errors showed when running a time machine snapshot Occurred when trying to run a past time machine snapshot. #20041

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


    dotCMS 21.02.2

    Available: Feb 26, 2021

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

    Improvements in dotCMS 21.02.2

    • Created a new endpoint to remove a layout from a role. (#19581)
    • The ability to customize TinyMCE and set it systemwide is now part of dotCMS. (#19651)
    • The filtering of related content items returned in GraphQl is now available. (#19652)
    • Enhanced logging messages for the deletion of roles. (#19664)
    • Built a history tab in the template detail screen. (#19668)
    • Allow the /api/content/search endpoint to accept POST parameters; this avoids having to URL encode your content queries. Also added curl examples of this to the content query dialog box. (#19691)
    • Improved resiliency to rules in push publishing, minimizing errors. (#19679)
    • Upgraded the edit page experience with multiple improvements including better drag and drop. (#19711)
    • Included a new endpoint in which a specific inode is passed and that version is deleted. (#19776)
    • Added the ability to close all dialog boxes in template portlet with the ESC key. (#19838)
    • Revamped the legacy template UI, moved it to Angular. Templates can now be designed using the same layout tool as pages.(#19087)
    • Ingesting a push publish bundle is now a stateful job and acts like a queue. This will prevent multiple bundles from being imported at a single time which can cause errors and performance issues. (#18722)
    • Vanity Url redirects can now include parameters.(#19564)
    • Updated translations.(#19823)

    Fixes

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

    • Fixed an issue that caused an error when creating a page on a site without templates. (#19999)
    • Fixed an issue that caused an error when editing a page and selecting any persona in order to create a personalized version of the page. (#20009)
    • Fixed an issue that sometimes prevented the value of a field from being saved when it was created in the content type with the variable name properties. (#18073)
    • Fixed an issue that sometimes prevented a new user from being given permissions on folders. (#18208)
    • Fixed an issue that sometimes prevented a single quote from being accepted in the name of a content type. new user from being given permissions on folders. (#18241)
    • Fixed an issue that sometimes caused push publishing errors when multiples users were attempting to push publish at the same time. (#18722)
    • Fixed an issue that sometimes caused apps to break when Elastic Search was unavailable. (#19515)
    • Fixed an issue that prevented $dotcontent.pull from returning over 10,000 content items. (#19527)
    • 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 caused the push publish batch button to select all content items on the site instead of all of the content items on that specific page. (#19620)
    • Fixed an issue that caused rules to always be forced pushed even when they were excluded in the push publishing filter. (#19648)
    • Fixed an issue that prevented the Language, Device and Persona dropdowns buttons from hiding when the browser window shrunk while in Edit Page. (#19656)
    • Fixed an issue that caused scroll problems in the content search when tag fields are used. (#19688)
    • Fixed an issue that prevented "Push Publish" and "Add to Bundle" options from showing when you add a rule to a page. (#19708)
    • Fixed an issue that caused a blank screen to be presented after the "Pick Design" or "Advanced" dialog boxes were closed on the template list. (#19713)
    • Fixed an issue that prevented the thumbnail from loading when a new page was created whose template has a thumbnail. (#19727)
    • Fixed an issue that prevented the portlet title from updating when navigating through the backend. (#19792)
    • Fixed an issue that prevented the user from being redirected to "Edit Page" after creating and publishing a new page. (#19812)
    • Fixed an issue that prevented "No Results" from showing when the user searches the template list for something with no results. (#19839)
    • Fixed an issue that prevented the template portlet from refreshing when the site is changed. (#19840)
    • Fixed an issue that prevented the creation or editing of an advanced template in Safari. (#19841)
    • Fixed an issue that prevented the template list to return templates from sites other than the current one. (#19845)
    • Fixed an issue that caused an error to show when attempting to see details of a container. (#19867)
    • Fixed an issue which could cause problems switching over to a new index in clustered instances.(#19738)
    • Fixed an issue that sometimes prevented a custom layout included in a push publish from showing on the reciever.(#19890)
    • Fixed an issue that caused errors when reindexing on an instance with an empty starter. (#19959)

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

    Announcements and Deprecations

    • dotCMS 21.02.1 still requires Java 8 in order to run properly. That said, we expect that within the next 6 months, dotCMS will be deprecating support for Java 8 and instead require Java 11 to run. We will keep the community posted.
    • The next version of dotCMS will ship with Tomcat 9. Starting with the next version, any plugins or overrides that specify files in the tomcat directory tomcat-8.5.32 will need to be updated.

    dotCMS 5.2.8.4 LTS

    Available: Feb 17, 2021

    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.3.8.4 LTS

    Available: Feb 17, 2021

    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 21.01

    Available: Jan 11, 2021

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

    Fixes

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

      • Fixed an issue which prevented a valid license from being recognized for some servers in a cluster. (#18860)
      • Fixed an issue which prevented content from appearing when using the advance search option, select, on the Content Search screen.(#19337)
      • 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 which sometimes prevented a bundle from being deleted when it contains thousands of items. (#19378)
      • 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 prevented contentlets from returning in a query when it had a unique text field that included dashes. (#19489)
      • Fixed an issue that sometimes prevented content from being push published when it was manually selected. (#19571) ( #19634)
      • 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 caused the Content API to not return the name or title when ID was entered in the call. ( #19639)
      • Fixed an issue that could have prevented dotCMS from starting up. (#19653)
      • 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 in EMA app that caused an error when proxying the request to a 3rd party server. (#19709)
      • Fixed an issue that sometimes caused GraphQL to freeze when push publishing new content. (#19660)
      • 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 a SQL error when a user tried to browse by a specific content type using the filter in the content types portlet. (#19744)
      • 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)

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

      Additional Changes and Improvements in dotCMS 21.01

    • Added the ability to get a token to the Add Endpoint screen to streamline push publishing. (#19275)
    • Improved behavior of SAML log out screen. (#19299 )
    • Added Import button on Application listing configuration page. (#19517)
    • Improved the speed of the CVS Importer tool. (#19536)
    • Improved how the database handles content from deleted users. (#19555)
    • Improved logging messages. (#19566 )(#19621)


    dotCMS 20.11.1

    Available: Dec 3, 2020

    dotCMS 20.11.1 is a minor release which includes fixes for an issue in previous releases.

    Fixes

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

    • Reverted a prior fix (#19558) to prevent an issue which could cause push publishing to fail under certain conditions. (#19634)

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


    dotCMS 20.11

    Available: Nov 24, 2020

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

    Changes to Default Behavior

      The following differences in default behavior in dotCMS 20.11 may change your expectations and require a review of your administration practices. Please review all of these changes before upgrading from a previous release.

    • Changed default location for generated image to /assets.

    Fixes

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

    • Fixed an issue which prevented a file added to a binary field from saving in the form. (#18346)
    • Fixed an issue which sometimes caused errors when changing the version of a piece of content. (#18550)
    • Fixed an issue which sometimes prevented page personalization from showing up when using legacy containers. (#19285)
    • Fixed an issue which sometimes reordered fields in a content type. (#18834)
    • Fixed an issue that sometimes prevented GraphQL from retrieving image information. (#19449)
    • Fixed an issue that sometimes caused existing URL maps on newly upgraded systems to throw an error. (#19452)
    • Fixed an issue that sometimes caused push publishing to fail due to file-based containers. (#19497)
    • Fixed an issue that prevented the deletion of conditions in rules. (#19538)
    • Fixed an issue that caused the layout editor to look abnormal when coming from the edit page. (#19540)
    • Fixed an issue that sometimes caused the login username field to appear as a selector. (#19585)
    • Fixed an issue that prevented task details from showing up in the workflow portlet. (#19598)

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

    Additional Changes and Improvements in dotCMS 20.11

    • Added secrets exporter and importer which encrypts and decrypts files as json for CMS Admins. (#18236)
    • Added endpoints to the GraphQl API to get page information. (#18297)
    • Added default vtl files allowing users to be able to create content with a new out of the box dotCMS instance. (#19086)
    • Added the ability to shut down a dotCMS instance from the console.(#19319)
    • Update theme to PrimeNG 10 from PrimeNG7. (#19341)
    • Added a tool to show cache size estimates catagorized by object and region. . (#19379)
    • Added parameters to the api/v1/templates endpoint. (#19421)
    • Folder's default file type is now based on the parent folder's default file type. (#19410)
    • Changed naming logic for upgrade tasks. (#19424)
    • Added a button type to allow intergration with third-party systems. (#19439)(#19440)
    • Added Create Export buttons on site listing configuration page. (#19490)
    • Resized the visitor location map pop-up in rules to be wider. (#19539)
    • Implemented WebDAV improvements. (#19428)


    dotCMS 5.3.8.2 LTS

    Available: Nov 20, 2020

    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.

    Additional Changes and Improvements in dotCMS 5.3.8.2

    • Improved detail of log messages for certain errors. (#19566), (#19310)

    dotCMS 20.10.1

    Available: Nov 5, 2020

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

    Changes to Default Behavior

    The following differences in default behavior in dotCMS 20.10.1 may change your expectations and require a review of your administration practices. Please review all of these changes before upgrading from a previous release.

    • The cancel option has been removed for the push publishing integrity check.
      • In previous versions, a user could cancel an integrity check while it was in progress.
      • With dotCMS 20.10.1, a user can not longer cancel an integrity check once it is in progress.
    • The Receive-From section has been removed from the publishing enviroments section of the control panel.
    • Jsontool.generate now returns velocity by default instead of JSON.
      • In previous versions, the publishing enviroments section of the control panel would state what enviroment would be the reciever of the push publishing data.
      • With dotCMS 20.10.1, a user can now use JWT in the authentication process for publishing eviroments instead
      • For more information, please see Additional Changes.
    • Users with SAML configured will now see a logout screen user.
      • If a user with SAML configured logs out they will be sent to a logout page.
      • When a browser timeouts for user with SAML configured,the user will see no change until they refresh, then they will see a logout page.
      • For more information, please see Additional Changes.

    Privacy and Security Updates

    The following changes in dotCMS 20.10.1 fix potential security or privacy issues which have been identified by dotCMS. For more details on any of these issues, please contact dotCMS Support.

    • Fixed a security vulnerability which could allow an authenticated user to exploit a weakness in certain API calls.
      • In addition to the fix in dotCMS 20.10.1, a plugin which mitigates the vulnerability has been created for all affected dotCMS versions (all release from 5.0.3 to 5.3.9), which can be applied without a server restart.
      • Mitigation has already been performed for all dotCMS Cloud customers.
      • Detailed information on this vulnerability, including a link to the patch plugin, will be provided in a Security Issue notice on the Known Security Issues page once all on-premesis customers have had an opportunity to apply the patch.

    It's important to understand that some security issues may have privacy implications for your existing dotCMS installation. Therefore we recommend that you review these changes, and if necessary modify any appropriate content, to ensure your site maintains compliance with any security and privacy standards and regulations you adhere to.

      Fixes

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

      • Fixed an issue which could prevent push publishing when attempting to fix a folder conflict. (#19471)
      • Fixed an issue which could prevent the permissions tab from displaying for a limited user. (#19364)
      • Fixed an issue which could temporarily prevent the file list from refreshing after an image is added. (#19335)
      • Fixed an issue which could prevent display of an appropriate error to appear when adding a file to a folder with filters. (#19182)
      • Fixed an issue causing the wrong filter name to appear in bundle details. (#19075)
      • Fixed an issue causing the Integrity Checker to fail when JWT was used for Push Publishing authentication. (#18690)
      • Fixed an issue preventing SVG images from displaying correctly in the UI. (#18656)
      • Fixed an issue that sometimes cause errors when integity checker was run on dotCMS clusters. (#18554)
      • Fixed an issue causing the JSONTool to return a single content item instead of a list. (#18505)

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

      Additional Changes and Improvements in dotCMS 20.10.1

      • Added endpoints to the Page API to support operations on the Query Tool. (#18314)
      • Added endpoints to the Bundle API to support operations on Creating a Bundle. (#19321)
      • Added fireRules parameter at page level of the GraphQL API.(#19219)
      • Updated the logout for SAML users to return users to a new logout page.(#19098)
      • Added JWT support to push publishing authentication. (#16796)
      • Updated HTTP Client to Angular 10.(#19073)


      dotCMS 5.3.9

      Available: Oct 8, 2020

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

      Changes to Default Behavior

      The following differences in default behavior in dotCMS 5.3.9 may change your expectations and require a review of your administration practices. Please review all of these changes before upgrading from a previous release.

      • The Permissions required to edit Categories have been changed.
        • In pervious versions, a user could not create top-level Categories without Edit Permissions rights for Categories on the System Host (All Hosts).
        • With dotCMS 5.3.9, permissions have been changed to allow you to give non-administrative users the ability to create and edit top-level Categories. The permissions required to edit Categories are now the following:
          • Create Top-Level Category: Publish rights for Categories on the System Host (All Hosts).
          • Create Subcategory: Publish rights for Categories on the parent Category.
          • Edit Any Category: Edit rights for the Category to be edited.
      • Unused Elasticsearch _text fields have been removed.
        • _text fields in the index, which were created by default in previous versions but not used by dotCMS, are no longer created by default.
        • Creation of these fields can be re-enabled by setting the CREATE_TEXT_INDEX_FIELD_FOR_NON_TEXT_FIELDS configuration property to true.
        • For more information, please see the Github issue.

      Fixes

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

      • Fixed an issue preventing pagination of content displayed in the add content popup in the Page Editor (#19304)
      • Fixed an issue which could cause extra content to be exported in some circumstances when creating a new starter.zip (#19300)
      • Fixed an issue preventing the use of the "UPLOAD NEW FILE" button when setting the value for Image and File fields (#19181)
      • Fixed an issue which could temporarily prevent a changed layout from displaying properly when changing the view in the Page Editor (#19165)
      • Fixed an issue which could cause errors when using a File-based Container on a Site other than the Default Host (#18780)
      • Fixed an issue which prevented display of content added to a Container when the Template was changed to one that used the same Container (#18607)
      • Fixed an issue preventing the use of the #dotParse() directive in Custom Fields when the included file was on a different Site (#18573)
      • Fixed an issue causing improper display of the Page Editor toolbar in Edit mode on some screen sizes (#18203)

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

      Additional Changes and Improvements in dotCMS 5.3.9

      • Improved Permissions used to control access to Top-level Categories (#8538)
      • Improved the display of error messages when some types of runtime exceptions are encountered (#19310)
      • Updated the release Docker images to enable execution on ARM architecture (#19334)
      • Improved error handling when the Apps Secret Store file became corrupted (#19302)
      • Added several minor improvements to the dotCMS starter site that ships with the release (#19289)
      • Made some minor improvements to the GraphQL Page API (#18990, #19190)
      • Improved GraphQL cache handling to improve performance in a cluster (#19255)
      • Restricted access to SAML App metadata (#19157)
        • Although exposing the SAML metadata poses no known security risks, access to this data was restricted to support a security posture of restricted data access by default.
      • Added endpoints to the Page API to support operations on Templates (#19096)
        • These endpoints are currently intended for internal use only; official support for customer use may be provided in later versions.
      • Reduced the default size of Elasticsearch indexes by removing unused fields (#18988)
      • Added a REST endpoint enabling App configuration to be imported from and exported to external files, for backup and portability (#18237).


      dotCMS 5.3.8

      Available: Sep 18, 2020

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

      Important: With the release of dotCMS 5.3.8, support for using dotCMS with MySQL is officially deprecated. Please see below for more information.

      Fixes

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

      • Fixed an issue which could cause performance issues, and in some cases application hangs, due to Apps configuration (#19282)
      • Fixed an issue which could sometimes prevent the content list from being shown in the content selection modal (#19263)
      • Fixed an issue preventing display of available actions in the batch action modal after executing a Workflow Action directly in Content Search (#19257)
      • Fixed an issue which could cause content to be removed from a Page when the same content was edited within another Page (#19245, #19212, #19213)
      • Fixed an issue which could cause errors to be generated when using GraphQL to pull content containing Binary fields (#19240)
      • Fixed an issue which could prevent Push Publishing from working properly when the content being pushed already existed in an archived state on the receiver (#18920, #19221)
      • Fixed an issue which could cause editing of a VTL file in Page edit mode under specific circumstances (#19220)
      • Fixed an issue which caused errors editing content on a Page if the Content Type used a #}dotParse directive in the tinymceprops field variable (#19214)
      • Fixed an issue which could cause results to stop displaying in Content Search after sorting on a field for which no content contains a value (#19210, #19169)
      • Fixed an issue preventing the use of GraphQL in Community Edition (#19206)
      • Fixed an issue preventing display of "Language" and "Host" Search fields when relating content on Content Types with multiple relationship fields (#19204)
      • Fixed an incorrect Site name in the starter site (#19203)
      • Fixed an issue preventing display of Binary images on the front-end of the site if the working version of the content is not the same as the live version (#19201)
      • Fixed an issue which could cause some Categories to be lost when exporting and then importing content (#19195)
      • Fixed an issue which could prevent content from saving if no value existed in a non-required Tag field (#19189)
      • Fixed an issue prevented the changing of Loggers with the LoggerResource if the classes were not in the classpath (#19183)
      • Fixed an issue preventing limited users from creating content in languages other than the default language (#19155)
      • Fixed an issue preventing Vanity URLs from being evaluated in the proper order (#19147)
      • Fixed an issue preventing the Push Publish modal from working from some screens (#19133)
      • Fixed an issue prevented second-level (grandchild) category values from being returned with content in multiple REST API calls (#19121)
      • Fixed an issue which could cause elevated server load if multiple background operations were executed in a short period of time (#19006)
      • Fixed an issue which could sometimes prevent some content items from being added to the Elasticsearch index (#18951)

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

      Deprecated Features

      The following features have been officially deprecated in dotCMS 5.3.8. These features have not been removed, and still work normally, but are no longer fully supported, and may be removed in a future dotCMS release.

      • Support for MySQL has been deprecated.
        • Future features may not be supported in MySQL, and fixes for issues which are not security- or privacy-related may not be fixed for systems running on MySQL.
        • Support for MySQL may be fully removed in a future release.

      Additional Changes and Improvements in dotCMS 5.3.8

      • Added several new fields to the GraphQL Page API (#19159, #19143, #19136, #19108)
        • The following new properties were added:
          • layout
          • render
          • urlContentMap
          • ViewAs
      • Improved Apps to allow the storage of multi-line secrets (hidden fields) (#19074)
      • Reordered the tabs in the Publishing Queue to show the most-commonly used tab (Status/History) first (#19071)
      • Moved configuration for Google Translate (and the Translate Workflow Sub-Action) to the Apps feature (#19061)
      • Added a new REST endpoint to retrieve an entire folder tree (#18964)


      dotCMS 5.3.7

      Available: Aug 26, 2020

      dotCMS 5.3.7 is a minor update which includes several improvements and minor fixes for several issues in previous releases.

      New Features

      The following new features have been added in dotCMS 5.3.7:

      • New Apps Integrations feature
        • The new Apps Tool allows developers to create and manage information used to integrate with third-party applications and external servers.
        • Apps supports custom configurations which can be managed through the back-end UI, a secure Secrets repository, and a REST API to integrate those configurations with your own plugins.
        • The dotCMS 5.3.7 starter site ships with several built-in Apps as examples; for more information on these, please see the Apps Tool in the dotCMS starter or demo site.
        • When you upgrade to dotCMS 5.3.7, all administrative users with access to the Maintenance Tool (Control Panel -> Maintenance) will automatically be given access to the Apps tool.
          • If you wish to change which users have access to the Apps Tool, or if you wish to hide it from existing users, you can modify which Roles have access to it through the Roles & Tools screen (Control Panel -> Roles & Tools) just like any other Tool.
          • For more information, please see the Roles and Tools documentation.
        • For more information on Apps, please see the Apps Integrations documentation.
      • New Environment Variable Configuration capability
      • New GraphQL Additions and Improvements
        • The GraphQL interface has been enhanced with several new features and improvements, including:
          • New BaseType Interfaces allow return of dotCMS Base Types.
          • Added a total results count to all GraphQL results, to aid in handling pagination.
          • Improved the Site field in the GraphQL response to include all content fields added to the Host Content Type.
        • For more information on all of these additions, please see the GraphQL documentation.

      Fixes

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

      • Fixed an issue preventing proper use of cluster Autowire when Hazelcast discovery was enabled (#19163)
      • Fixed an issue which could prevent display of the Template Designer for Sites with certain characters in the Aliases field (#19123)
      • Fixed an issue preventing use of the Cancel button when editing existing Content Type fields (#19120)
      • Fixed an issue preventing display of some Content Types in the Content Search Tool under certain conditions (#19118)
      • Fixed an issue preventing display and editing of Task details in the Tasks Tool (#19117)
      • Fixed an issue preventing the insertion of links in the WYSIWYG Field when using Community Edition (#19102)
      • Fixed an issue preventing scrolling of the Tools menu when the back-end UI navigation was collapsed (#19030)
      • Fixed an issue preventing the Push Publish popup from displaying in the Page editor (#18678)
      • Fixed an issue causing the Permission tab to incorrectly display (but not allow editing) for users without "Edit Permissions" rights to the content (#18583)
      • Fixed an issue some UI problems when adding Content Types with reserved names (#18474)
      • Fixed an issue preventing the use of "force unlock" by administrators in the Page editor (#18204)
      • Fixed an issue causing incorrect display of some portions of the Page editor on smaller screens (#18203)

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

      Additional Changes and Improvements in dotCMS 5.3.7

      • Improved validation of YAML formatting on Push Publish Filter configuration files (#18986)
      • Added a REST API endpont that returns a list of users based on selected Roles (#18979)
      • Added information about the default language to the response from the /api/v2/languages endpoint (#18969)


      dotCMS 5.3.6.1

      Available: Aug 14, 2020

      dotCMS 5.3.6.1 is a maintenance release which includes a fix for one minor issue with the 5.3.6 release which may affect some larger sites.

      Fixes

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

      • Fixed an issue which could sometimes cause reindexing to fail on sites with many content type fields (#19092)

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


      dotCMS 5.3.6

      Available: Aug 12, 2020

      dotCMS 5.3.6 is a maintenance release which adds one new feature, removes one deprecated feature, and includes several minor fixes and improvements.

      New Features

      The following features have been added in dotCMS 5.3.6:

      • New Push Publishing Notifications
        • dotCMS will now automatically notify a user when a Push Publishing operation they initiated either succeeds or fails.
        • Notifications will be displayed automatically in a popup, and can be viewed in the notification history window (accessible via the "bell" icon in the top-right corner of the back-end UI).

      Fixes

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

      • Fixed an issue preventing the creation of links in the WYSIWYG field editor (#19041)
      • Fixed an issue which caused the Push Publishing Filters to be removed when the deploy-plugins.sh script was run (#19037)
      • Fixed an issue which could cause a reindex to time out on sites with very large numbers of Content Type fields (#19033)
      • Fixed an issue preventing drag-and-drop of images into WYSIWYG fields (#19018)
      • Fixed an issue allowing users to delete a just-archived Page, even if no Workflow Action existed to perform a delete (#19015)
      • Fixed an issue which could cause an error when fetching a contentType collection with no content via GraphQL (#18977)
      • Fixed an issue which could prevent selection of a file-based-Container when the title did not match the file name (#18921)
      • Fixed an issue which prevented proper front-end operation when running AdoptOpenJDK v8u262b10 (#18917)
      • Fixed an issue which incorrectly allowed creation of Content Type fields with variable named "host" (#18882)
      • Fixed an issue which could sometimes cause some Containers to not display any content (#18855)
      • Fixed an issue preventing the Time Machine from respecting Publish and Expire dates in content displayed by Widgets (#18795)
      • Fixed an issue which could prevent the Available Workflow Actions button from working in specific circumstances (#18697)
      • Fixed an issue which could cause relationships on a receiver to get temporarily out-of-sync with the sender in specific circumstances (#18571)

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

      Features and Dependencies Removed from dotCMS 5.3.6

      A number of previously-deprecated features and dependencies have been removed from dotCMS 5.3.6.

      For customers which only use the standard dotCMS distribution, these changes will likely have no impact. However for customers which build dotCMS from source or who use custom plugins, these changes may impact your build process. If you do build dotCMS or custom plugins, please review the below list to identify any dependencies which may affect your build process.

      Removed Features

      • The Workflow Actions Code field has been removed.
        • Customers who have existing Workflow Actions that use the Code field should do one of the following before upgrading to dotCMS 5.3.6:
          • If the Large Message Subaction is available in your current dotCMS version: Move the contents of the Code field to a Large Message Subaction.
          • If the Large Message subaction is not available in your version, then:
            • Before the upgrade, move anything in the Code field to a .vtl file, and include that file with a #dotParse() directive.
            • After the upgrade, create a Large Message Subaction, and use a #dotParse() directive in that Subaction to parse the same .vtl file.

      Additional Changes and Improvements in dotCMS 5.3.6

      • Added the ability to change the location of the dotGenerated folder in the dotCMS installation (#18958)
      • Added the ability to use Push Publishing Filters when downloading Bundles (#18293)
      • Added a new LoggerResource, which enables logging levels to be changed dynamically (without restarting dotCMS) (#18889)
      • Added a new REST API endpoint to upload Bundles (#18563)
      • Added support for the hazelcast-kubernetes discovery jar, to support Hazelcast discovery in all Kubernetes distributions (#18904)
      • Improved folders to allow inclusion of spaces in folder names (#16216)
      • Improved Elasticsearch field mappings to perform custom mappings immediately (when a field is created, instead of just during a reindex) (#18887)
      • Improved the Content Type selector drop-down to enable scrolling (#18840)
      • Improved the Content Type Tool to allow editing of Content Types even if there is not a valid ES index (#18837)
      • Removed an unused and unneeded icu4j library (dot.icu4j-4.0.1_2.jar) from the dotCMS Classpath (#18927)


      dotCMS 5.3.5

      Available: Jul 29, 2020

      dotCMS 5.3.5 is a maintenance release which includes fixes for two security vulnerabilities, and some minor fixes and improvements.

      Privacy and Security Updates

      The following changes in dotCMS 5.3.5 fix potential security or privacy issues which have been identified by dotCMS. For more details on any of these issues, please contact dotCMS Support.

      It's important to understand that some security issues may have privacy implications for your existing dotCMS installation. Therefore we recommend that you review these changes, and if necessary modify any appropriate content, to ensure your site maintains compliance with any security and privacy standards and regulations you adhere to.

      • Fixed a potential XSS vulnerability in a specific dotCMS component (#18961)
      • Updated the com.fasterxml.jackson.core library to the latest version, to address potential vulnerabilities (#18151)

      Fixes

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

      • Fixed an issue which could prevent creation of a new dotAsset when dragging an image onto the WYSIWYG file browser (#18980)
      • Fixed an issue which resulted in a Bad Request response when passing the 'uri' parameter to the sitename endpoint (#18848)
      • Fixed an issue which could cause errors and prevent some Workflows from working properly after upgrading a system which uses Oracle as a database (#18782)
      • Fixed an issue which caused a dojo/parser error in console when adding more than 2 relationship fields (#18764)
      • Fixed an issue preventing the "com.dotcms.hooks" sample plugin from working properly (#18756)
      • Fixed an issue which prevented the use of relative URL Map patterns which worked in earlier dotCMS releases (#18744)
      • Fixed an issue which could cause Container Ids to be duplicated under certain conditions (#18714)
      • Fixed an issue which could cause all Push Publishing Filters to fail when bad data was found in any of the filter files (#18705)
      • Fixed an issue which could cause reindexing to fail on some systems upgraded from very old versions of dotCMS (#18673)
      • Fixed an issue which could cause errors when attempting to Push Publish files that were uploaded via WebDAV (#18626)
      • Fixed an issue which could cause errors on some systems when upgrading from earlier dotCMS versions (#18524)

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

      Deprecated Features

      The following features have been officially deprecated in dotCMS 5.3.5. These features have not been removed, and still work normally, but are no longer fully supported, and may be removed in a future dotCMS release.

      • The Code field in Workflow Actions is deprecated, and will be removed in dotCMS 5.3.6.
        • Anything which is displayed in a Code field should be moved into a Large Message Subaction instead.
        • The Large Message subaction provides the same functionality as the Code field, but enables you greater control over the size of the popup message, and when the popup appears (relative to the other Subactions).

      Additional Changes and Improvements in dotCMS 5.3.5

      • Removed unnecessary messages written to the log file when using MySQL as database (#18947)
      • Improved the error message displayed when a Push Publish fails due to Push Publish Filter excluding dependencies (#18792)
      • Improved Elasticsearch connection in a cluster, to utilize ES load balancing features without using an external load balancer (#18870)
      • Improved content export to allow export of unlimited number of content items (#18641)
      • Added a Page field to GraphQL which contains properties of the Page (#18599)
      • Improved the Log File pop-up window to expand the messsage display portion of the window when the window is resized (#18556)
      • Unrepackaged the com.fasterxml.jackson.core library (#18151)
        • Any customers which reference the repackaged libraries in their code will need to modify the code to refer to the unrepackaged libraries instead. For example, import com.dotcms.repackage.com.fasterxml.jackson.annotation.JsonProperty; should be changed to import com.fasterxml.jackson.annotation.JsonProperty;.
      • Upgraded GraphQL from v11.0 to v13.0
      • Upgraded the kickstart library from v7 to v9.


      dotCMS 5.2.8.3 LTS

      Available: Jul 24, 2020

      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)

      dotCMS 5.3.4.1

      Available: Jul 22, 2020

      dotCMS 5.3.4.1 is a maintenance release which includes a fix for one significant issue which may affect all sites, and fixes for several issues which may affect sites which use MSSQL or Oracle databases.

      Fixes

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

      • Fixed an issue preventing dotCMS startup on sites using MSSQL (#18940)
      • Fixed an issue causing an error when a cluster was initialized on sites using Oracle (#18918)
      • Fixed an issue prevented reindexing on sites using MSSQL (#18912)
      • Fixed an issue which could cause the Site Browser to fail to display some folders (#18901)
      • Fixed an issue causing startup and reindexing failures on sites using Oracle (#18878)

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


      dotCMS 5.3.4

      Available: Jul 15, 2020

      dotCMS 5.3.4 is a maintenance release which includes some minor fixes, and improvements.

      Fixes

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

      • Fixed an issue which prevented users from being able to change which Site Search index was the default (#18872)
      • Fixed an issue preventing site search indexing jobs from completing and being assigned as the new default Site Search index (#18869)
      • Fixed an issue which could prevent a Container from displaying any content in some circumstances (#18855)
      • Fixed an issue preventing the Page layout editor from working properly for some Pages (#18830)
      • Fixed an issue which could cause incorrect results to be returned when searching for Site Aliases with Elasticsearch (#18805)
      • Fixed an issue which could prevent the parent content in a self-joined relationship from being pushed by dependency (#18804)
      • Fixed an issue preventing proper operation of Workflows in Oracle (#18782)
      • Fixed an issue causing only partial display of very long file names in the Asset information window (#18691)
      • Fixed an issue which could cause Push Publishing to fail in specific circumstances (#18621)
      • Fixed an issue which prevented some Site Aliases from working correctly (#18187)

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

      Additional Changes and Improvements in dotCMS 5.3.4

      • Added display of a notification when Elasticsearch is in read-only mode (#17842)
        • When content is saved, if the Elasticsearch server is unavailable (due to a network error, for example), a notification will be displayed in the back-end UI.
        • Availability of the Elasticsearch server will be automatically re-checked until the server is once again available - when a new notification will be displayed in the back-end UI.
      • Added display of the instance Secret Key (SHA-3 Key Digest) and Cluster Id to the System -> Configuration -> Basic Info screen (#17938)
      • Added the ability to update or regenerate the instance Secret Key from the System -> Configuration -> Basic Config screen (#18381)


      dotCMS 5.3.3

      Available: Jun 29, 2020

      dotCMS 5.3.3 is a maintenance release which includes some minor upgrades, fixes, and improvements.

      This release includes a number of changes which may affect existing installations. We recommend that you read through this changelog in full before upgrading any existing installations.

      Important Changes

      A number of important changes in dotCMS 5.3.3 configuration may impact your performance when upgrading an existing site. Please read the documentation sections on all of these changes before upgrading from a previous release.

      Configuration Changes

      The following important changes have been made to configuration in dotCMS 5.3.3:

      • The "Push Now" Workflow Sub-Action now allows you to specify a Push Publishing Filter (see below)
        • Existing "Push Now" Sub-Actions will use whichever filter is defined as the default filter.
        • By default, this will preserve the Push Publishing behavior of previous versions
          • However, if you modify your Push Publishing Filters to change which filter is used as the default filter, the "Push Now" Sub-Actions will change to use the new default filter.
        • You may change each "Push Now" Sub-Action to specify a filter by name, instead of using the default filter.
      • The Vanity URL cache regions have changed
        • Vanity URLs continue to work the same as they have in previous versions, but the underlying code has been significantly updated to improve performance and reliability.
        • As part of this change, there are now two different cache regions for Vanity URLs: vanityurlsitecache and vanityurldirectcache.
          • The vanityurlsitecache region stores a separate list of Vanity URLs for each host on your system
            • The default size of 5000 should work for almost all dotCMS instances, but if you have thousands of sites on the same dotCMS instance, you should set this region to a size that's larger than the number of hosts you expect to have on your system.
          • The vanityurldirectcache region stores the most recently matched Vanity URLs.
            • The default size of 25000 will work for the majority of sites, but if your sites use Vanity URLs heavily, you may wish to monitor the cache statistics, and increase the size of this region appropriately if necessary.

      New Features

      The following new features have been added in dotCMS 5.3.3:

      • New Push Publishing Filters enable you to selectively limit which types of content and dependencies are pushed to a receiving environment
        • You may create different filters, to give your users a choice of how to push content.
        • You may give different permissions to each filter, to limit the use of some filters by Role.
        • You may specify a default filter, which will be automatically selected, and which will be used by default in all existing Workflow Actions.
          • When upgrading your site, the default filter will be set to the "Everything and Dependencies" filter, which pushes content with all dependencies, matching the behavior of pushes in earlier dotCMS versions.
        • The dotCMS starter site includes a set of standard filters.
          • When upgrading your site, these filters will be installed automatically.
        • For more information, please see the Push Publishing Filters documentation.

      Fixes

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

      • Removed unnecessary file metadata log messages during reindexing (#18752)
      • Fixed an issue preventing the main navigation in the back-end from scrolling (#18716)
      • Fixed an issue causing an error when renaming a file while creating new content (#18685)
      • Fixed an issue which could cause an error when a Page without a valid template was bundled (#18598)
      • Fixed an issue which could prevent import of a starter site with XML 1.1 characters in it (#18576)
      • Fixed an problem with the download link on File Assets (#18561)
      • Fixed an issue which could cause the Drop Old Assets Versions tool to fail when deleting a large number of records (#18494)
      • Fixed an issue which could cause Elasticsearch indexing issues with heavy use of Key/Value fields (#18446)
      • Fixed an issue which could cause an error when an empty VTL file was push published (#18051)
      • Fixed performance and consistency issues when Vanity URLs were used in a cluster (#17278)
      • Fixed an issue which could cause the buttons in the Content Type properties window to stop working under certain conditions (#18595)
      • Fixed an issue which could sometimes cause GraphQL to return an incomplete URL (without the full path) #18286)
      • Fixed an issue which could cause a UI (Javascript) error when a content type had two relationship fields to the same parent content type (#18152)

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

      Additional Changes and Improvements in dotCMS 5.3.3

      • Created a new REST endpoint to load all message keys (#18530)
      • Upgraded the #dotParse() directive to accept dotAssets (#18402)
      • Added the ability to open the File Browser with one click from the WYSIWYG field (#18498)
      • Upgraded the Workflow Scheduled Action to support multi-lingual content (#18591)
      • Implemented some internal performance improvements (#18682)
      • Improved error logging in several areas (#18645)
      • Improved resource handling in the Temp file API (#18676)


      dotCMS 5.3.2

      Available: Jun 15, 2020

      dotCMS 5.3.2 is a maintenance release which includes some minor upgrades, fixes, and improvements.

      New Features

      The following new features have been added in dotCMS 5.3.2:

      • Improved file handling in the WYSIWYG field
        • Added the ability to drag and drop images into the WYSIWYG field.
          • Dropped images will be saved as dotAssets, and automatically assigned to a dotAsset Content Type based on the file type, in the way as files dropped into the Content Search screen.
        • Added the ability to open the File browser with one click.
        • Added a button to edit image properties.

      Privacy and Security Updates

      The following changes in dotCMS 5.3.2 fix potential security or privacy issues which have been identified by dotCMS.

      It's important to understand that both security and privacy issues may have privacy implications for your existing dotCMS installation. Therefore we recommend that you review these changes, and if necessary modify any appropriate content, to ensure your site maintains compliance with any security and privacy standards and regulations you adhere to.

      • Fixed an issue causing some screens in the back-end UI to display improperly when the X-Content-Type-Options header was specified (#16955)
        • This issue did not cause any security issues, but prevented the use of the X-Content-Type-Options header, which can be used to improve security.
        • The X-Content-Type-Options header may now be used to improve browser security while accessing the dotCMS back-end UI.

      Fixes

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

      • Fixed an issue preventing upgrade from earlier release when using older versions of Postgres (#18640)
      • Fixed an issue which sometimes caused conflicts when pushing legacy relationships upgraded to new relationship fields (#18616)
      • Fixed an issue preventing scrolling in the Content Types Tool (#18588)
      • Fixed an issue which could sometimes cause Content Type fields to be reordered unpredictably (#18542)
      • Fixed an issue which could cause errors in the Content editor when a content item had related Parents that were archived (#18525)
      • Fixed an issue which could sometimes prevent OSGI plugins from initializing properly, and cause noisy logging (#18501)
      • Fixed an issue which caused Key Value field data to be returned in the wrong order (#18479)
      • Fixed an issue which prevented GraphQL from returning related content in any Language other than the default Language (#18444)
      • Fixed an issue which prevented GraphQL from returning any content in specific circumstances (#18443)
      • Fixed an issue which prevented a reindex from finishing under specific conditions (#18424)
      • Fixed an issue which could prevent the "What's Changed" feature from detecting content changes on the page (#18356)
      • Fixed an issue which sometimes prevented access to an asset using the ID Path URL, even for admin users (#18345)
      • Fixed an issue preventing multiple Tools from updating properly when the Site was changed in the back-end UI (#18148)
      • Fixed an issue causing errors in the content editing screen when the Tab divider and other fields shared the same name (#18102)

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

      Additional Changes and Improvements in dotCMS 5.3.2

      • Added a CORS filter to the GraphQL interface (#18567)
      • Added a new REST API endpoint to retrieve the image URL from a dotAsset (#18427)
      • Improved the query strings displayed in the Show Query popup to better match the content displayed in the Content Search screen (#18316)


      dotCMS 5.3.1

      Available: Jun 1, 2020

      dotCMS 5.3.1 is a maintenance release which includes a single important fix for the 5.3.0 release.

      Fixes

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

      • Fixed an issue preventing the same File-based Container from being added to a Page more than once (#18558)

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


      dotCMS 5.3.0

      Available: May 21, 2020

      dotCMS 5.3.0 is a major release which includes some significant upgrades and new features, performance and stability improvements, upgrades to a number of key components, and some significant changes to existing functionality.

      This release includes a number of changes which may affect existing installations. We recommend that you read through this changelog in full before upgrading any existing installations.

      Important Changes

      A number of important changes in dotCMS 5.3.0 configuration may impact your performance when upgrading an existing site. Please read the documentation sections on all of these changes before upgrading from a previous release.

      Configuration Changes

      The following important changes have been made to configuration in dotCMS 5.3.0:

      • The dotCMS distribution files are now delivered as Docker images and Amazon AWS Images (AMIs), in addition to binary files.
        • For the most seamless demonstration experience, dotCMS recommends Docker images for most new dotCMS users.
        • However experienced dotCMS users may still download the dotCMS binary distribution for installation and upgrades.
      • The internal Elasticsearch server has been removed
        • All dotCMS installations must now use an external Elasticsearch server.
        • All dotCMS Docker images include an external Elasticsearch server which is started and managed transparently by the Docker image.
      • The main database configuration for dotCMS installations has been changed from the context.xml file to the db.properties file.
        • The dotCMS distribution no longer ships with a context.xml file.
        • The context.xml file will still be used if no db.properties file exists, so the context.xml files of customers upgrading from earlier releases will continue to work without changes.
        • For more information on the new db.properties file, please see the Database Configuration documentation.
      • Elasticsearch SSL/cert verification has disabled by default.
        • This change was made to improve Elasticsearch security, by allowing Elasticsearch to use HTTPS protocol even when connecting to hosts which may not have a valid cert.
        • You may re-enable SSL/cert verification by setting the property ES_TLS_ENABLED=true in the dotcms-config-cluster.properties file.

      Changes to Default Behavior

      The following differences in default behavior in dotCMS 5.3.0 may change your expectations and require a review of your administration practices. Please review all of these changes before upgrading from a previous release.

      • The default database configuration file has been changed from context.xml to db.properties.
        • The context.xml file is still supported, but has been deprecated, and will stop being supported in a future release.
        • For more information on using the new db.properties file, or configuring your database using system variables or Docker secrets, please see the Database Configuration documentation.
      • A number of potential Content Type variable names have now been designated as reserved.
        • If you create a new Content Type and the variable name resolves to one of these reserved names, the variable name will automatically be modified to prevent an exact match with the reserved name.
        • Existing Content Types which match these new reserved names will not be changed, but it is recommended that you consider changing Content Types with variables matching a reserved name, as the Content Type variable name may cause conflicts in some cases.
        • For more information on the list of reserved names for Content Types, please see the Content Types documentation.
      • Changed the default value of the H22 Cache Provider recovery threshold.
        • The default value of the cache.h22.recover.if.restarted.in.milliseconds has been changed to 0, to prevent a restarted server from attempting to recover a bad cache.

      New Features

      In addition to the Important Changes listed above, the following additional new features have been added in dotCMS 5.3.0:

      • New dotAsset Base Content Type
      • New Tile View of the Content Search screen
        • Users may now choose to view the Content Search scren in either List view (the traditional view) or Tile view.
      • New File Drag-and-Drop capability in the Content Search screen
        • Users may now upload files via drag-and-drop into the Content Search screen.
        • System administrators may configure dotAsset Content Types so uploaded files are automatically assigned to appropriate Content Types, based on the MIME type of the uploaded file.
        • For more information, please see the File Assets and dotAssets documentation.
      • New Database Configuration capabilities.
        • Database configuration can now be performed via a configuration file, via system variables, or via Docker Secrets.
        • For more information, please see the Database Configuration documentation.
      • Vanity URLs can now be created to pass parameters to the target URI.
      • The distribution now ships with an empty starter site, to enable quick development of sites from scratch.
      • An External Elasticsearch server is now supported by default.
      • Added new RestClientProvider and DotRestClientProvider interfaces to enable custom Elasticsearch behavior

      Fixes

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

      • Fixed an issue which caused an error when the Set Value Workflow Sub-Action was executed (#18468)
      • Fixed an issue preventing the ESQueryCache from initializing properly when used in a cluster (#18458)
      • Fixed an issue which left the old key in use after importing a new starter (#18394)
      • Fixed an issue which could sometimes cause multiple Vanity URLs to stop working, requiring a cache flush (#18364)
      • Fixed an issue which could prevent the use of Time Machine future snapshots (#18355)
      • Improved URL normalization to prevent the use of site specification characters (//) (#18354)
      • Fixed an issue which could prevent users from added content to pages when using MySQL (#18341)
      • Fixed an issue which could cause OSGI initialization errors in a clustered environment (#18319)
      • Fixed an issue which could cause form submission to fail due to a permission error (#18292)
      • Fixed an issue which could prevent the Site Variables window from appearing after deleting a user (#18256)
      • Fixed could cause Push Publish of a new site to fail in some circumstances (#18210)
      • Improved real-time validation checks in the content editing window (#18192)
      • Fixed an issue which could cause the admin user menu to display incorrectly after a Login As operation (#18182)
      • Fixed an issue which could cause an empty or incorrect content title to be returned in some circumstances (#18177)
      • Fixed an issue which could cause Site Search indexing to fail when a Content Type detail page was not found (#18164)
      • Fixed an issue which could prevent Site Search from indexing some multi-lingual versions of URL Mapped content (#18132)
      • Fixed an issue preventing widget Pre-execute code from running in Page Edit mode (#18086)
      • Fixed problems with the Language drop down in Page Edit mode (#18084)
      • Fixed error messages in the log files when running the "Download Data/Assets" maintenance tool (#18080)
      • Fixed an issue causing an incorrect error message when using Login As to a user with limited permissions (#18069)
      • Fixed an issue preventing the Page Editor from correctly limiting the number of contents added to a Container (#18021)
      • Fixed an issue causing incorrect $navtool operation when ENABLE_NAV_PERMISSION_CHECK was set to true (#18016)
      • Fixed an issue causing URL Maps to fail when the content in a URL mapped field contained a forward slash (/) (#18015)
      • Fixed a spurious log error message after the completion of a reindex of a large site (#17918)
      • Added configuration options to allow Elasticsearch to be run without SSL for testing purposes (#17879)
      • Fixed an issue preventing automatic redirection to the login page when an unauthenticated user attempts to access a resource requiring authentication (#17858)
      • Fixed an issue preventing indexing of content if the Content Type was assigned a variable name of title (#17850)
      • Fixed an issue preventing File-based Containers from working properly when the files were not on the Default Site (#17749)
      • Fixed an issue preventing Site Search from respecting default language fallback for Velocity files included with dotParse (#17672)
      • Fixed an issue which could cause legacy relationships to be cleared if an attempt was made to save content while the Elasticsearch index was not writable (#17601)
      • Fixed an issue which could cause errors in URL Maps after an upgrade when using a root-based URL Map pattern (#17514)

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

      Privacy and Security Updates

      The following changes in dotCMS 5.3.0 fix potential security or privacy issues which have been identified by dotCMS.

      It's important to understand that both security and privacy issues may have privacy implications for your existing dotCMS installation. Therefore we recommend that you review these changes, and if necessary modify any appropriate content, to ensure your site maintains compliance with any security and privacy standards and regulations you adhere to.

      • Fixed an issue which could causing some file contents to be interpreted by the user's browser when editing the file (#18369)
      • Added additional restrictions to limit access to context from scripting (#18318)

      Deprecated Features

      The following features have been officially deprecated in dotCMS 5.3.0. These features have not been removed, and still work normally, but are no longer fully supported, and may be removed in a future dotCMS release.

      Additional Changes and Improvements in dotCMS 5.3.0

      • Added a unique key to the Workflow Tasks table, to prevent the possibility that multiple Workflow tasks could end up with the same Identifier and Language Id (#17088).
      • Content Type variable names are now required to be case-insensitively unique, to prevent potential conflicts (#18382).
      • Added support for the INDEX_POLICY on the query string in the Workflow REST API (#18357)
      • The ResourceLink feature has been updated to support all Binary fields in all Content Types (#18310)
      • Several improvements were made to logging, to both reduce noise and improve messaging in some situations (#18183, #18072)
      • The Temporary file endpoint has been updated to auto-assign the Content Type for dotAssets (#18064)
      • The Elasticsearch String.intern property has been disabled to reduce CPU usage (#17899)
      • Elasticsearch has been upgraded from OpenDistro version 1.2.0 to OpenDistro version 1.3.0 (#17885)
      • On startup, dotCMS now automatically waits until an Elasticsearch server is available (#17883)
      • The ESIndexResource class has been updated to call dotCMS API methods instead of calling Elasticsearch directly (#17848)
      • Automaticaly generated Site Search index Aliases are now automatically prefixed with the Cluster Id to ensure uniqueness (#17747)
      • A new custom Docker image has been made available for running Open Distro Elasticsearch with dotCMS (#16806)
      • Significantly improved the performance of the /api/v1/page/render endpoint (#18397)
      • Synchronized the "Download Data/Assets" and "Backup Data/Assets" maintenance tools to produce compatible ZIP files (#18388)
      • Significantly reduced the CPU utilization of the MonitorResource (#18245)
      • Improved the status endpoint to allow access from locations other than localhost (for use with Docker and other applications) (#18215)
      • Added "title" to the list of file metadata fields indexed by default (#18172)
      • Options to download index snapshots were removed from both the Index tab of the Maintenance Tool and the Site Search Tool (#18059)

      dotCMS 5.2.8

      Available: Apr 6, 2020

      dotCMS 5.2.8 is a maintenance release which includes some minor upgrades, fixes, and improvements.

      Changes to Default Behavior

      The following differences in default behavior in dotCMS 5.2.8 may change your expectations and require a review of your administration practices. Please review all of these changes before upgrading from a previous release.

      • Front-end Users may no longer preview unpublished (working) content in any location
        • In previous versions of dotCMS, Front-end users could in some circumstances preview unpublished content, if they were assigned appropriate permissions to the unpublished content.
        • dotCMS 5.2.8 standardizes access permissions of Front-end users across all APIs and access methods, preventing Front-end users from previewing unpublished content in any way.
        • If you have existing Front-end users that need to be able to preview unpublished content, you will need to:
          1. Change the users from Front-end users to Back-end users (via the Users screen),
          2. Limit their access to the dotCMS back-end (via the Roles and Tools screen), and
          3. Limit their access to appropriate content (through regular Permissions).
        • For more information, please see the Preview vs. Live documentation.

      New Features

      The following new features have been added in dotCMS 5.2.8:

      • New REST API Front-end User Authentication capability
        • Users can now be authenticated as either front-end or beck-end users using the REST API.
        • For more information, please see the Preview vs. Live documentation.

      Fixes

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

      • Fixed an issue which caused columns in the Content Search screen to be displayed in the wrong order (#18159)
      • Fixed an issue preventing the Page API from returning content items placed in Advanced Templates (#18158)
      • Fixed an issue which caused Content Type Text fields configured for Numeric data to be saved as Text data (#18147)
      • Fixed an issue which caused error messages in the My Account popup to be displayed incorrectly (#18143)
      • Fixed an issue preventing new pages from being Push Published under certain conditions (#18126)
      • Fixed issues preventing the Site name from refreshing when the a new Site was selected (#17937, #18125)
      • Fixed an issue preventing a user from being remembered with the Remember Me feature after another login of the same user from a differen location (#18101)
      • Fixed an issue which could cause Front-End users to get a 403 (access denied) error when accessing a front-end form requiring authentication (#18076)
      • Fixed an issue which caused already-pushed content to be re-pushed after a bundle was deleted on the sender (#18025)
      • Fixed an issue which caused content which was archived on the sender to be deleted from the receiver when Push Published (#17994)
      • Fixed an issue which caused items to continue to appear in Site Search after being unpublished or archived (#17976)
      • Fixed an issue which could prevent a limited user from being able to create rules, even when granted appropriate permissions (#17901)
      • Fixed an issue preventing Vanity URLs from working if there was a trailing slash in Uri field (#16433)

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

      Additional Changes and Improvements in dotCMS 5.2.8

      • Improved the user interface of the Relate Content popup:
        • Added the ability to search by hitting the Enter key in the Relate Content popup (#18038)
        • Updated the Relate Content popup to allow a click anywhere on the line to select content (#16936, #17981)
      • Improved the management and performance of clusters when using Docker containers and Kubernetes (#18050, #18190)

      Upcoming Changes in dotCMS 5.3.0

      The dotCMS 5.3.0 release, currently planned for release in April 2020, will contain some important changes that may impact your system configuration and processes. Please review the changes listed below to be aware of these changes, and if necessary, begin preparing for them.

      • Removal of embedded Elasticsearch server
        • dotCMS 5.3.0 will no longer include an embedded Elasticsearch server.
        • This means that all customers upgrading to dotCMS 5.3.0 will need to use an external Elasticsearch server.
        • The dotCMS Docker reference containers are all designed to use a containerized Elasticsearch server out-of-the-box, so switching to a Docker deployment is a very good option for customers that want to upgrade to 5.3.0 with the minimum effort.

      dotCMS 5.2.7

      Available: Mar 9, 2020

      dotCMS 5.2.7 is a maintenance release which includes some minor upgrades, fixes, and improvements.

      New Features

      The following new features have been added in dotCMS 5.2.7:

      • New Asset Base Content Type enables creation of files and images in a repository without an explicit URL path
        • You can now create Content Types which contain files and images, but which are not located in a specific location within the site.
        • For more information, please see the Base Content Types documentation.

      Fixes

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

      • Fixed an issue preventing some Image and File field types from being displayed by GraphQL API (#18005)
      • Fixed an issue which could prevent Push Publishing of a Rule actively running on the receiver (#17930)
      • Fixed an issue which could prevent Worklow execution by a user without permissions to the Default site (#17876)

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

      Additional Changes and Improvements in dotCMS 5.2.7

      • Added support for Image Focal Points when using the /da image URL format with "shorty" Ids (#17965)
      • Added the ability to make Binary fields indexable and displayable using the Show in List field property (#17944, #18022)
        • Note: Only the first Binary field on a Content Type can be indexed and set to Show in List.

      dotCMS 5.2.6

      Available: Feb 21, 2020

      dotCMS 5.2.6 is a maintenance release which includes some minor upgrades, fixes, and improvements.

      New Features

      The following new features have been added in dotCMS 5.2.6:

      • New Reset Approvers Workflow Sub-Action allows Workflows relying on multiple approval to reset the list of approvers if the content is re-edited after previously being approved.
      • New Default Workflow Action settings are available in the Workflow Scheme properties screen.
        • You can now set Default Workflow Actions so that if standard operations on content (e.g. New, Save, Publish, Unpublish, etc.) are performed using a method that does not execute a Workflow Action, the operation will be automatically performed using a Workflow Action you specify.
        • For more information on the types of Default Workflow Actions that can be assigned, please see the documentation on Default Workflow Actions.

      Fixes

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

      • Fixed an issue preventing users from switching a WYSIWYG field to Text and back to WYSIWYG (#18018)
      • Fixed an issue which prevented URL map field values containing forward slashes from working properly (#18015)
      • Fixed an issue preventing unauthorized attempts to access pages from properly redirecting to the login page (#18010)
      • Fixed an issue preventing relationships on the Host Content Type from displaying in the Back-end (#17928)
      • Fixed an issue causing some types of navigation menus from displaying properly in the Page Editor in Edit mode (#17896)
      • Fixed an issue preventing selection of some filter combinations in the User Tool (#17895)
      • Fixed an issue which could cause some browsers to auto-fill new passwords on the change password screen (#17889)
      • Fixed an issue preventing Categories from being sorted properly via the Sort Order field (#17798)
      • Fixed an issue preventing file-based Containers from working properly when not located on the default Site (#17749)
      • Fixed an issue which could prevent relationships from being saved correctly in some cases when using "Relate New Content" (#17743)
      • Fixed an issue causing an incorrect URL to be displayed in the Task Detail screen (#17532)
      • Fixed an issue causing errors in the GraphQL API when Content Types have fields with specific variable names (#17515)
      • Fixed an issue which caused the Event popup to display incorrectly if the End Date field in the Event Content Type was moved before the Start date field (#17497)

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

      Additional Changes and Improvements in dotCMS 5.2.6

      • Upgraded the starter site included with the release distribution to a brand new, completely rebuilt site which demonstrates many of the newer and more sophisticated features of dotCMS.
        • Please perform a fresh installation of dotCMS 5.2.6 to a new location to have the new starter site installed for you.
        • Once the new starter site is installed, you can use Bundles to copy features from the new starter site to your existing site.
      • Improved the "Add to Bundle" functionality to remember the last Bundle name selected (#14066)
      • Added a new parameter to the Content REST API to return full Category information in results (#12739)
        • The includeCategoriesExtraInfo URL parameter can now be supplied (e.g. /includeCategoriesExtraInfo/true) to reutrn full Category information in the results.
      • Added the ability to create "pluggable" content field validations using OSGI plugins (#17773)
        • This allows you to add your own custom code to perform sophisticated and proprietary validations on the data users enter into your content fields.
      • Improved the Binary field to allow limiting of both file length and file type in all uploaded files (#17772)
        • You may use the allowedFileTypes Field Variable to specify which mime types may be uploaded, and the maxFileLength Field Variable to limit the size of all uploads.
        • Since these limitations are implemented as Field Variables, you may set different limits for different Binary fields, even within the same content type (to ensure, for example, that one Binary field is used to upload only videos, while another is used to upload only photos).

      dotCMS 5.2.5

      Available: Feb 7, 2020

      dotCMS 5.2.5 is a maintenance release which includes some minor upgrades, fixes, and improvements.

      New Features

      The following new features have been added in dotCMS 5.2.5:

      Fixes

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

      • Fixed an issue which could cause the Navtool Viewtool to return incorrect items in some circumstances (#16589)
      • Fixed an issue preventing Vanity URLs from properly redirecting to URL-mapped content (#16684)
      • Fixed an issue which could prevent the Time Machine from displaying individual future content in some circumstances (#17594)
      • Fixed an issue causing some valid folder names from being rejected (#17751)
      • Fixed an issue causing Archived content to be copied to a new Site as Unpublished (#17763)
      • Fixed an issue which could improperly prevent use of the Workflow API in some circumstances (#17794)
      • Fixed an issue with the Content Search tool when the Back-end UI language was set to Spanish (#17797)
      • Fixed an issue which could prevent pages on a non-default host from being found in the Page editor (#17803)
      • Fixed an issue causing duplicate Containers to appear when paging through Containers (#xxxxx)
      • Fixed an issue preventing the Site selector from refreshing properly in Chrome in some circumstances (#17828)
      • Fixed an issue preventing the "Send for Review" feature from working when viewing Workflow Task details (#17829)
      • Fixed an issue adding files with long names in the WYSIWYG field (#17833)
      • Fixed an issue preventing the user menu selections from displaying under certain conditions (#17855)
      • Fixed an issue preventing constant fields from being included in JSON responses (#17864)
      • Fixed an issue which could prevent the Image Editor from scrolling down on large images (#17940)

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

      Additional Changes and Improvements in dotCMS 5.2.5

      • Improved the REST API to allow Binary fields to be uploaded by specifying a remote URL (#16852)
        • Previously, files needed to be uploaded to dotCMS prior to adding them to Binary fields.
      • Simplified the Image Processing REST API to eliminate the need to explicitly specify which filters are used and in what order.
        • You may now simply supply the appropriate filter parameters, and the filter operations will be performed in the order the parameters appear.
        • You may also continue to explicitly specify the filters and the filter order (as in older versions), so older image URLs do not need to be modified in any way.
        • For more information, please sse the Image Resizing & Processing documentation.

      dotCMS 5.2.4

      Available: Jan 24, 2020

      dotCMS 5.2.4 is a maintenance release which includes some minor upgrades, fixes, and improvements, and an important security update.

      Important:

      dotCMS 5.2.4 includes an important fix for a critical security vulnerability. This vulnerability has already been mitigated for existing dotCMS Enterprise and dotCMS Cloud customers. However, if you are a Community Edition customer, it is strongly recommended that you upgrade to dotCMS 5.2.4 as soon as possible.

      Privacy and Security Updates

      The following changes in dotCMS 5.2.4 fix potential security or privacy issues which have been identified by dotCMS.

      • Fixed a critical security vulnerability reported in CVE-2020-6754
        • Fixes for this vulnerability have been generated for all affected dotCMS versions.
        • Fore more information, including mitigation measures and the link to the CVE alert, please see security issue SI-54.

      Fixes

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

      • Fixed an issue preventing the Redirect URL property from working with custom Page Content Types (#15427)
      • Fixed an issue causing CMSFilter to return a 404 for URLs containing a plus sign (#17261)
      • Fixed an issue preventing the Copy Site operation from properly copying Page contents to a new Site (#17541)
      • Fixed an issue which could sometimes cause Push Publishing conflicts when pushing Language Variables (#17596)
      • Fixed an issue which could prevent users from being able to edit Sites without View permission on the Default Site (#17612)
      • Fixed an issue preventing the Asset Backup tool from using the ASSET_REAL_PATH configuration (#17620)
      • Removed an old/invalid foreign key from some database upgrade scripts (#17647)
      • Fixed an issue causing WebDAV to force folder and file names to lowercase (#17698)
      • Fixed an issue causing GraphQL to return a null when no Content Types of a queried Base Type existed (#17717)
      • Fixed an issue which could prevent browsing beyond five sub-folder levels when adding a file to a WYSIWYG field (#17792)

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

      Additional Changes and Improvements in dotCMS 5.2.4

      • The Back-end Menu Navigation has been improved to allow the menu to remain collapsed continually.
      • Added the ability to set a security constraint on the assets folder in the web.xml file (#17835)
      • The REST Content Type API has been enhanced to allow specification of additional default Workflow Actions
        • Default Workflow Actions may now be specified for UNPUBLISH, ARCHIVE, UNARCHIVE, DELETE, and DESTROY, in addition to existing NEW, EDIT, and PUBLISH default actions.
      • Improved the content import and REST API save functions to accept remote URLs for the content of Binary Fields (#16852)
      • Prevented the copy of Workflow history when making a copy of a content item (#17550)

      dotCMS 5.2.3

      Available: Jan 3, 2020

      dotCMS 5.2.3 is a maintenance release which includes some minor upgrades, fixes, and improvements.

      New Features

      The following new features have been added in dotCMS 5.2.3:

      Fixes

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

      • Fixed an issue which could cause incorrect bundle audit information to generate noisy log messages (#17626)
      • Fixed an issue preventing the Bundles screen from refreshing after a Bundle was deleted (#17676)
      • Fixed an issue preventing Language Variables containing spaces from resolving correctly (#17679)
      • Fixed an issue which could prevent past Time Machine snapshots from being displayed (#17684)
      • Fixed an issue preventing images in WYSIWYG fields from being selected (#17731)

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

      Additional Changes and Improvements in dotCMS 5.2.3

      • The Page REST API (/api/v1/page) includes several new enhancements to support Single Page Applications (SPAs):
        • Information for all content contained in a Page is now rendered in results (#17665)
        • Content of URL Mapped pages is now rendered in results (#17666)
        • Languages passed via URL parameters can now be specified by language code (e.g. "en-US") as an alternative to language ID (e.g. "1") (#17700)
      • TinyMCE (used in the WYSIWYG field) has been upgraded from version 4.1.6 to version 4.9.6.

      dotCMS 5.2.2

      Available: Dec 13, 2019

      dotCMS 5.2.2 is a maintenance release which includes some minor upgrades, fixes, and improvements.

      New Features

      The following new features have been added in dotCMS 5.2.2:

      • New Delete All Versions Workflow Sub-Action
      • New Delete Push Publishing Bundles REST Endpoint

      Fixes

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

      • Fixed an issue preventing the Push Publish popup from displaying from the Tasks Tool (#17026)
      • Fixed an issue which could prevent proper batching of transaction when calling Quartz from code (#17591)
      • Fixed an issue preventing GraphQL from returning IDs for new languages (added after upgrade to dotCMS 5.1.0+) (#17615)
      • Fixed incorrect key when serializing the Visitor object (#17616)
      • Fixed an issue preventing Lucene date range queries from working (#17621)
      • Fixed an issue causing upgrades to dotCMS 5.2.1 to fail for systems with no URL Maps (#17642)
      • Fixed a javascript error when selecting a relationship from the relationship select popup (#17663)

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

      Additional Changes and Improvements in dotCMS 5.2.2

      • Folder name restrictions have been implemented at the API level, to ensure bad folder names can not be created through WebDAV and other means (#16715)
      • Changed deletion of Content Type fields to perform the deletion in the background (#16939)
      • To improve compatibility, the GraphQL implementation has been modified to remove Base Types as Interfaces, and no longer allow specification of individual fields for Base Type collections (#17560)
      • REST API calls which return related content were improved to respect supplied language parameters for both parent and related content (#16917)

      dotCMS 5.2.1

      Available: Nov 7, 2019

      dotCMS 5.2.1 is a major release which includes some significant upgrades and new features, performance and stability improvements, upgrades to a number of key components, and some significant changes to existing functionality.

      Fixes

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

      • Fixed an issue with the Forms preventing binary submits from working properly (#17468)
      • Fixed an incorrect default sort order on Custom Content Portlets (#17455)
      • Fixed an issue causing redirection to a blank page after adding a Menu Link (#17347)
      • Fixed an issue causing display of a blank page (instead of a license required message) when viewing Rules in Community Edition (#17512)
      • Fixed an issue preventing Forms from being added properly to personalized Pages (#17554)
      • Fixed an issue causing error messages in REST API calls to be incorrectly included in the response header (#16383)
      • Fixed an issue preventing the navigation cache from updating properly when a Page was copied (#17353)
      • Fixed an issue preventing proper display of some Container fields when changing the Max Contents field value (#16782)
      • Fixed an issue where the removed REST_API_CONTENT_ALLOW_FRONT_END_SAVING configuration property was still required in some circumstances (#17510)
      • Fixed an issue which could give anonymous users access to content when the Front-End User Role was explicitly given permissions to that content
      • Fixed issues preventing self-joined Relationship fields from working correctly in some REST API calls (#17477, #17492, #17529)
      • Fixed an issue preventing related content from displaying properly after a bundle containing related content is uploaded (#17528)
      • Fixed an issue preventing display of content with different live and working versions (#17451)
      • Fixed an issue allowing more than one content to be related on a Relationship field with One-to-One cardinality (#17524)
      • Fixed an issue which could cause content in a Container to be removed from the Page when the layout is changed under specific circumstances (#17435)
      • Fixed an issue which could cause a log exception and incorrect content display with an empty duplicate Container in a Page (#17553)
      • Fixed an issue which could cause the selected Site to change when copying and pasting a folder (#17113)
      • Fixed an issue which could allow content to be related to itself in certain circumstances (#17543)
      • Fixed an issue which could cause upload of new files via WebDAV to fail (#17506)
      • Fixed an issue which allowed only one user to see a Workflow Task with "Four Eyes Approval" in progress (#17250)

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

      Known Issues in dotCMS 5.2.1

      The following known issues in dotCMS 5.2.1 will be addressed in future dotCMS releases:

      • Translations for 2 newly added strings were not included in the release.
        • If you wish to include these translations in your 5.2.1 distribution, you can find the translations (with key names dot.common.press and dot.common.message.no.workflow.schemes) in the dotCMS Github repository, and manually add them to the language strings files in your distribution.

      Privacy and Security Updates

      The following changes in dotCMS 5.2.1 fix potential security or privacy issues which have been identified by dotCMS.

      It's important to understand that both security and privacy issues may have privacy implications for your existing dotCMS installation. Therefore we recommend that you review these changes, and if necessary modify any appropriate content, to ensure your site maintains compliance with any security and privacy standards and regulations you adhere to.

      • Fixed an issue which could allow anonymous users access to working versions of content when the Front-End User Role was explicitly given View permissions to that content (#17526)

      Additional Changes and Improvements in dotCMS 5.2.1

      • Added caching to 404 error results pages (#17377)
      • Improved performance by removing redundant Hibernate code (#17428)
      • Added language flags to relatable content on new Relationship fields (#16129)
      • Improved logging when content validation fails (#16165)
      • Added a message to indicate when there are no available Workflow Actions for content (#17533)
      • Improved responsiveness of Content Type field deletion (#16939)
      • Improved file access performance by caching file system metadata (#17269)
      • Improved File Container caching and performance (#16597)
      • Reduced unnecessary logging when a live version of content can not be found (#17551)
      • Geolocation information has been added to the Visitor object (#17495).

      dotCMS 5.2.0

      Available: Oct 7, 2019

      dotCMS 5.2.0 is a major release which includes some significant upgrades and new features, performance and stability improvements, upgrades to a number of key components, and some significant changes to existing functionality.

      This release includes a number of changes which may affect existing installations. We recommend that you read through this changelog in full before upgrading any existing installations.

      Important Changes

      A number of important changes in dotCMS 5.2.0 configuration may impact your performance when upgrading an existing site. Please read the documentation sections on all of these changes before upgrading from a previous release.

      Configuration Changes

      The following important changes have been made to configuration in dotCMS 5.2.0:

      • Explicit Front-end and Back-end User Configuration Has Been Added
        • To improve security and simplify administration, every User can now be explicitly assigned as a Front-end User, Back-end User, or both, in the Users tool.
        • When upgrading an existing installation, all users will automatically be assigned as Front-end Users.
          • In addition, existing Users will automatically also be assigned as Back-end Users if either of the following are true:
            • The User has any layouts assigned (meaning that the user is assigned at least one Role which has at least one Tool Group and Tool assigned to it), or
            • The User has at least one API Access Key assigned to them.
        • After upgrade, you may manually change the designation of Users as Front-end or Back-end Users via the Users tool.
        • For more information, please see below.
      • Configuration Properties Controlling Access to the REST API Have Beed Simplified
        • A new CONTENT_APIS_ALLOW_ANONYMOUS configuration property has been added which replaces all configuration properties which were previously used to control access to the REST API by non-authenticated and front-end users.
          • Valid values for this property are write, read, or none.
        • The following three configuration properties used in previous versions have been removed and no longer work:
          • REST_API_CONTENT_ALLOW_FRONT_END_SAVING
          • REST_API_FORCE_FRONT_END_SESSION_AUTH
          • REST_API_REJECT_WITH_NO_USER
        • If you have changed the any of these removed properties from their default values, you must add and set the CONTENT_APIS_ALLOW_ANONYMOUS property to an appropriate value to ensure your front-end forms and REST API access behave properly.
        • For more information, please see issue #17034 in the dotCMS Github repository.
      • The WYSIWYG Field configuration has changed.
        • The default TinyMCE configuration has been updated, removing a redundant menu bar and cleaning up some options in the WYSIWYG Field.
        • By default, the WYSIWYG Field will look for a css file named /application/wysiwyg/wysiwyg.css in the current site, and if that file is found, will apply that styling to the content in the WYSIWYG field.
          • The location of this CSS file can be overridden by setting a value for the WYSIWYG_CSS property in the dotmarketing-config.properties file.

      Changes to Default Behavior

      The following differences in default behavior in dotCMS 5.2.0 may change your expectations and require a review of your administration practices. Please review all of these changes before upgrading from a previous release.

        • Important: Due to changes in Elasticsearch (details below), you must perform a full reindex of both the main dotCMS index and any Site Search indexes after upgrading from an earlier version of dotCMS.
        • Elasticsearch Indexing has Been Upgraded
          • The Elasticsearch Text Analyzer Changed
            • In order to improve results and simplify queries, the Elasticsearch text analyzer has been changed from "Whitespace" to "Standard".
            • Although in most cases this will improve search results without the need for wildcards and complex queries, it means that existing queries may return additional results that they did not return in previous versions (especially queries that do not use wildcards).
            • It is recommended that you review all your Lucene and Elasticsearch queries to ensure the behavior has not changed.
          • Elasticsearch Queries Matching Multiple Values for the Same Field May Need to Be Updated.
            • Due to changes in Elasticsearch, queries which use a space as an "OR" between terms matching the same field may fail to match all expected content. To ensure these queries work properly, it is recommended that you review your queries that match multiple values for the same field, and ensure that one of the following is true:
              • The query uses an explicit "OR" operator instead of an implicit OR (via a space). Example: +field:(term1 OR term2)
              • Each term in the query explicitly specifies the field. Example: +(field:term1 field:term2)
              • All search terms are enclosed in quotes. Example: +field:("term1" "term2")
        • Queries of Related Content from Child Side Must Be Performed Using Relationship Methods
          • In order to improve performance and solve problems with certain queries, the way related content is indexed has been changed.
          • Because of this change, querying related parent content using Lucene query terms no longer work (e.g. $dotcontent.pull("+parentContentType.relationshipFieldVar:childId",...)).
          • If you are performing any queries of parent relations using a method other than the $dotcontent.pullRelated() or $dotcontent.pullRelatedField methods, you will need to convert the query to use one of these two methods.
        • "Default" Save and Publish Are Now Performed Using Default Workflow Actions
          • If content is saved or published using a method which does not explicitly call a Workflow (such as when using WebDAV or the Content API), the content will now be saved or published using the new Default Workflow Action specified in the Content Type (rather than the simple default save and publish used in previous versions).
          • For more information on Default Workflow Actions, please see below.
        • The Location of Content Has Changed for Content Types without a Site or Folder Field
          • In order to improve options for content security and management (especially in multi-tenant sites), content without a Site or Folder field is now stored in the same location as the Content Type (instead of on the System Host, as in previous versions).
          • Depending on the location of the Content Type and the specific query terms used, queries and other operations which may previously have included or excluded this content may return different results.
            • If you have any Content Types without a Site or Folder field that are not located on the System Host, you may restore the previous behavior by moving the Content Type to the System Host.
        • The Default Sort Order on the Content Search has Changed
          • By default, results in the Content Search screen are now sorted by relevance instead of by last modification date (e.g. the Elasticsearch score field instead of the modDate field).
          • To sort results by last modification date, you can select the "Last Modification Date" column header in the search results list.
        • Language Variables Added as Content Now Take Precedence
          • Language variables that are added as content in the system and called with $text.get("var") will now take precedence over the language strings in the global properties file.
        • REST API Endpoints Restricted to Back-End Users
          • In conjunction with the explicit designation of Front-end and Back-end Users, a number of REST API endpoints have been restricted to only allow access to Back-end Users (even for read-only access). The following endpoints will now only allow access by Back-end Users and User accounts with API Access Keys defined:
      /bundle /cluster /config /environment
      /license /osgi /role /ruleengine
      /ws/v1/system /v1/configuration /v1/esindex /v1/notification
      /v1/portlet /v1/roles /v1/sites/{siteId}/ruleengine /v1/system-status
      /v1/users /v2/users
        • Pushed Bundles are Now Automatically Deleted After Two Days
          • A cron job has been added to automatically delete old push publishing bundles, to prevent growth of the bundles folder from taking up too much disk space on the server.
          • You may control how long these bundles are retained on the server by modifying the bundles.delete.older.than.milliseconds property in the dotmarketing-config.properties file. For more information, please see the What to Know Before Push Publishing documentation.

        New Features

        In addition to the Important Changes listed above, the following additional new features have been added in dotCMS 5.2.0:

        • Content Personalization on Page or via API
          • Content on pages/routes can be personalized by persona and managed and previewed in Edit mode. Page rules have been surfaced, are accessable from edit mode can be combined with personas to deliver personalized experiences to targeted audiences regardless of how they are consuming the content.
        • New Form Builder
          • The Form builder has been replaced with a new Angular Form builder which allows easy creation of Forms and Form Content Types which work natively both the REST API and Workflows.
          • For more information on the new Form builder, please see the Form Builder documentation.
        • New Explicitly-Defined Front-end and Back-end User Roles
          • To improve security and simplify administration, every User can now be explicitly assigned as a Front-end User, Back-end User, or both, in the Users tool.
          • Users that are not assigned as Back-end Users will not be able to log into the dotCMS back-end (even if they are assigned Roles with layouts), and will not be able to access some REST APIs.
          • Users that are not assigned as Front-end Users will not be able to submit content using front-end forms (even if they are able to log into the Back-end).
          • Users which are assigned as neither Front-end Users nor Back-end Users will not be able to log into the dotCMS back-end, and will only be able to access a very limited set of REST APIs.
        • Temporary Resource for Multi-Part Uploads
          • A new REST API has been added allowing you to upload files as temporary resources, which can then be referenced from other REST APIs which add and update content.
        • Default Workflow Actions per Content Type
          • You may now specify default Workflow Actions for each Content Type.
          • The default Workflow Action is executed when content is saved or published using a method which does not explicitly call a Workflow (such as when using WebDAV or the Content API).
          • If content is saved without a Workflow Action, it will automatically be moved to the first Step of the first Workflow for the given Content Type.
        • WebP Image Format Support
        • New Tag Suggestions Endpoint
        • New Index Policy for REST API Endpoints
          • When saving content via the java ContentletAPI or a REST endpoint, you can now specify an indexPolicy of DEFER, WAIT_FOR, or FORCE. For more information, please see the Index Policy documentation.

        Fixes

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

        • Fixed an issue causing the "Default" label on a Site Search index to be removed when the dotCMS cache was flushed (#17046)
        • Fixed an incorrect error message generated when REST API call validation failed (#17164)
        • Fixed performance issue caused by permission API locks with a cold cache (#16963)
        • Fixed issues with Site permissions when more than one version of a Site exists (#16910)
        • Fixed an error when adding a Content Type with a name ending in a semicolon (#15147)
        • Fixed an error in the Page editor when a user did not have edit permissions to the Page being viewed (#16974)
        • Fixed an issue which could prevent some OSGI plugins from deploying automatically when dotCMS restarts (#16877)
        • Fixed an issue preventing the Page render endpoint from filtering content by Persona (#17073)
        • Fixed an issue preventing "Publish All" from working on a folder (#17140)
        • Fixed an issue preventing automatic reindex of an object after its permissions were reset (#16938)
        • Fixed an issue preventing content from rendering after deleting a Category that's being used by Content Types (#16838)
        • Fixed an issue which could cause errors re-importing a Site which had previously been deleted (#16990)
        • Fixed an issue which could cause conflicts between Content Types with names varying only by case (#17051)
        • Fixed an issue causing the "friendlyName" field to be duplicated in REST API results (#17052)
        • Fixed an issue which could prevent non-LDAP users from authenticating correctly on LDAP-enabled systems (#16996)
        • Fixed an issue which could cause incorrect GraphQL results after replacing the value in a Binary field in content (#16993)
        • Fixed an issue preventing the Push Publishing popup from displaying when using the Workflow Tasks tool (#15912)
        • Fixed an issue preventing raw output using the Velocity rendering REST API endpoint (#17022)
        • Fixed an issue preventing the Container toolbar from displaying when using the Blank Template (#13546)
        • Fixed an issue which could prevent newly related content from returning when pulling related content (#16563)
        • Fixed an issue which could cause fields in the Advanced search sidebar to get cut off (#17345)

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

        Deprecated Features

        The following features have been officially deprecated in dotCMS 5.2.0. These features have not been removed, and still work normally, but are no longer fully supported, and may be removed in a future dotCMS release.

        • WikiTool has been deprecated
        • The legacy Form builder is now fully deprecated.
          • The legacy Form builder has been officially deprecated since dotCMS version 5.0.0.
          • With this release, the legacy Form builder is fully deprecated, and is planned to be removed in a future dotCMS release.
          • It is therefore recommended that any Forms built with the legacy Form builder be migrated to the new Form builder as soon as possible.
        • The Legacy Content Type Tool (labeled "Content Types (Legacy)" in the Roles & Tools screen) has been deprecated.

        Additional Changes and Improvements in dotCMS 5.2.0

        • Improved Handling of Language Parameters with Related Content
          • When submitting a REST API call, the language of the results can be limited via a URL parameter (e.g. ?languageId=3) or query term (e.g. +contentType:contentTypeVar +languageId:3).
          • Handling has been made consistent so that when a language parameter is used, the language will be respected for both parent and related content, but when language is supplied as a query term, the language will restrict the parent content but not the children (for example when using the ?depth=2 parameter).
        • Replaced Apache Struts v1.2.4 with the alternative Struts 1 Forever package, which fixes all known security issues and which is continually maintained and patched (#16879).
          Important Note:
          • In earlier dotCMS versions, all struts 1 critical CVEs were patched or mitigated by the use of Beanutils 1.9.3 and the SuppressPropertiesBeanIntrospector.class.
          • The switch to Struts 1 Forever was made not to address security issues (since they had already been addressed), but to simplify vulnerability assessment and mitigation for both customers and our development staff moving forward.
        • Improved performance when moving or updating Content Type fields (#16907)
        • Improved logging and handling of database transactions (#16827)

        dotCMS 5.1.6

        Available: Jun 6, 2019

        dotCMS 5.1.6 is a maintenance release which includes fixes for several issues which affected some customers running the 5.1.0 and 5.1.5 releases.

        Important Changes

        Important changes in dotCMS 5.1.6 configuration may impact your configuration and system behavior when upgrading an existing site. Please read the documentation sections on all of these changes before upgrading from a previous release.

        Changes to Default Behavior

        The following differences in default behavior in dotCMS 5.1.6 may change your expectations and require a review of your administration practices. Please review all of these changes before upgrading from a previous release.

        • XSS Prevention Filter
          • In order to minimize XSS and CSRF vunerabilities, dotCMS now will block direct access to all files under the /html and /dotAdmin directories unless dotCMS is sent a valid referer or Origin header.
          • This new behavior is enabled by default, but can be turned off (allowing requests without a valid referrer or Origin to access these folders) by adding the following property to the dotmarketing-config.properties file:
            XSS_PROTECTION_ENABLED=false
          • For more information, please see the Security Best Practices documentation.

        Improvements

        The following improvements have been added in dotCMS 5.1.6:

        Fixes

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

        • Fixed an issue preventing Key/Value fields from being added to the index (#16313)
        • Fixed an issue which could cause a push of an entire site to fail (#16481, #16623)
        • Fixed an issue which could cause pagination in the back-end to fail when running under HTTPS (#16502)
        • Fixed an issue which caused a reindex of the File Asset Content Type to cause a full reindex (#16545)
        • Translated some back-end strings which were not translated in all supported languages (#16584, #16660)
        • Fixed an issue preventing the "All" Content Type selection from working with Custom Content Tools (#16587)
        • Fixed an issue which prevented limited users without access to the Content Tool from viewing Workflow Tasks (#16590)
        • Fixed an issue which prevented limited users from being able to logout properly (#16591)
        • Fixed an issue which prevented content from being removed from the index performing "Delete then Reindex" (#16592)
        • Fixed an issue preventing the /api/content/publish endpoint from working with multipart form data (FileAssets) (#16600)
        • Fixed an issue which caused static publishing to AWS S3 to fail when dotCMS was used in a Docker environment (#16612)
        • Fixed an issue preventing cache flush of individual Content Types from working (#16626)
        • Fixed an issue which could prevent deleted content from being cleared during a full reindex (#16664)
        • Fixed an issue preventing display of a front-end URL mapped page when logged into the back end (#16671)

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


        dotCMS 5.1.5

        Available: May 9, 2019

        dotCMS 5.1.5 is an intermediate release which includes some minor improvements and features, and some significant performance improvements, specifically for customers with large content repositories.

        Important Changes

        A number of important changes in dotCMS 5.1.5 configuration may impact your performance when upgrading an existing site. Please read the documentation sections on all of these changes before upgrading from a previous release.

        Important: The Minimum Java Version Has Changed

        dotCMS 5.1.5 will only work with version 1.8.0_162 or later of Java.

        • Earlier versions of Java will not work, even for systems which were upgraded from earlier dotCMS releases.
        • If the java version cannot be updated, you must install the Unlimited Strength Jurisdiction Policy Files (available at here).
          • Not having this support will result in an "InvalidKeyException" when attempting to use 192 or 256 bit keys.

        New Features

        In addition to the Important Changes listed above, the following additional new features have been added in dotCMS 5.1.5:

        • Reindex performance has been greatly improved, especially for large content stores.
        • Added the ability to generate stateless API Access Tokens using JWT, which can be used for authentication by applications, and which can be issued and revoked from the back-end UI.
        • Page Layouts can now include custom CSS classes for specific Rows and Containers in the Layout.
        • You can now create Custom Content Tools which display only the Content Types you wish.
          • These behave the same as the existing Content Search screen, but display only a limited set of Content Types you define. For example, you can create a Tool which displays only Blog content, only News content, or a combination of Blogs and News.
          • For more information, please see the Custom Tool Groups documentation.
        • The DotAjaxDirector API now take both JSON and API tokens.
          • This allows you, for example, to add and push Bundles using an API method.
          • For more information, please see the DotAjaxDirector API documentation.
        • The Workflow "fire" REST API endpoint has been improved.
          • The fire endpoint now accepts binary (multipart) content and new Relationships fields.
            • The fire endpoint now provides full equivalence with the legacy /api/content endpoint.
            • It is recommended that all new development use the Workflow fire endpoint instead of the legacy /api/content endpoint.
          • The fire endpoint now accepts specification of Workflow Actions by the Action Name or ID.
        • Added additional logging to the Push Publishing feature (#16197)
        • The back-end login screen has been redesigned for simplicity and greater ease-of-use.
        • A new "post" method was added to the JSONTool which allows you to send a request to the remote server using an HTTP POST.
          • For more information, please see the JSONTool documentation.

        Fixes

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

        • Fixed an issue which could cause a compliation error when importing some OSGI packages (#16377)
        • Enabled the use of "text/*" types with the content REST API (#15934)
        • Removed a limitation of REST API calls that prevented them from respecting LoggedInUser permissions (#16135)
        • Fixed an issue that caused file-based Containers to render incorrectly in Page edit mode (#16263)
        • Fixed an issue where an incorrect error code was returned when using an invalid identifier with the /vtl REST API (#15799)
        • Removed an inactive button from the Community Edition Content Search screen (#16270)
        • Fixed an issue which could prevent content from being published when the Tag field was Required (#16026)
        • Fixed problems that resulted when using the word "content" as a key in a Key/Value field (#16046)
        • Fixed an issue causing a Javascript error when a zero content Container was displayed in the Page editor (#16329)
        • Fixed an issue which could cause incorrect content to be displayed from the cache when pushing content using a shorty ID (#16310)
        • Fixed an issue which could display an empty popup when displaying health for a single index (#16331)
        • Fixed an issue which could prevent content saves during switch-over to a new index (#15421)
        • Fixed an issue which could prevent saving of existing content after changing a field to Required (#16376)
        • Fixed an issue that could data corruption with self-reltaed content if the order of Relationships fields was changed (#16420)
        • Made several improvements to Vanity URL caching (#16333, #16337, #16413)
        • Fixed an issue which could cause display artifacts when an invalid icon was set for a Tool Group (#16246)

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

        Deprecated Features

        The following features have been officially deprecated in dotCMS 5.1.5. These features have not been removed, and still work normally, but are no longer fully supported, and may be removed in a future dotCMS release.

        • Version 2 of the FieldResource REST API has been replaced with a new version (version 3), and version 2 is now deprecated.


        dotCMS 5.1.1

        Available: Mar 26, 2019

        dotCMS 5.1.1 is a maintenance release to fix one specific issue which affected some customers with the dotCMS 5.1.0 release.

        It is recommended that all customers running the 5.1.0 release upgrade to dotCMS 5.1.1 as soon as possible.

        Fixes

        • Navigation problems could be encountered in the Page editor under some circumstances (#16221)

        To view more information on this issue, please visit the dotCMS Github repository.


        dotCMS 5.1.0

        Available: Mar 14, 2019

        dotCMS 5.1.0 is a major release which includes some major upgrades and new features, performance and stability improvements, upgrades to a number of key components, and some significant changes to existing functionality.

        This release includes a number of changes which may affect existing installations. We recommend that you read through this changelog in full before upgrading any existing installations.

        Important Changes

        A number of important changes in dotCMS 5.1.0 configuration may impact your performance when upgrading an existing site. Please read the documentation sections on all of these changes before upgrading from a previous release.

        Changes to Default Behavior

        The following differences in default behavior in dotCMS 5.1.0 may change your expectations and require a review of your administration practices. Please review all of these changes before upgrading from a previous release.

        • Permissions required to create new Content Types has increased.
          • The authority level required to create new Content Types has been increased from EDIT to PUBLISH (#15285)
          • This change will not have any effect on any existing Content Types.
            • However if you have users who need to be able to create new Content Types, you will need to ensure that these users have PUBLISH permissions for Content Types in all locations where they will be creating new Content Types.
          • Users with EDIT authority will still be able to modify Content Types, but will not be able to create new ones.

        New Features

        In addition to the Important Changes listed above, the following additional new features have been added in dotCMS 5.1.0:

        • New Relationships Fields
          • A new type of Relationship field has been added, offering significant improvements over the legacy Relationships from older versions.
          • You may now create Relationships by adding Relationships to Content Types as fields which are created and displayed separately for each side of the Relationship.
          • This change provides more flexibility in the types of Relationships you can create, allowing you to now create both One-to-One Relationships and Relationships which are visible from only one side of the Relationship.
          • These new Relationships also allow you to access related content directly via Lucene and Elasticsearch queries, treating related content as a field of the content, rather than requiring dedicated methods (such as $dotcontent.PullRelated()) to retrieve related content.
          • Using the new Relationship fields, you may also now search for related content from the Content Search screen.
          • Legacy Relationships and Legacy Relationships fields are both still supported for backward compatibility.
            • You may mix new Relationships fields and Legacy Relationships fields in the same Content Type.
            • You can choose to convert Legacy Relationships to new Relationships fields, but to ensure backward compatibility, conversion will not be done automatically.
            • A "Relationships" tab in Content Types will still be displayed if you have Legacy Relationships on a Content Type and have not added a Legacy Relationship field to the Content Type.
            • However the "Relationships" tab is now built as a regular Tab-Divider field followed by a Legacy Relationships field in the Content Type, and any new Relationship fields will not display in the Legacy Relationships field.
          • For information on how to upgrade your existing Relationships to the new Relationships fields, please see the Migrating Legacy Relationships documentation.
          • For more information, please see the Relationships documentation.
        • Containers as Files
          • You may now create and manage Containers completely via files.
          • These files may be managed via WebDAV and other file management operations, easing integration of dotCMS with your CI/CD operations.
          • As part of this change, some Containers in the dotCMS Starter site were converted to File Containers.
          • For more information, please see the File Based Containers documentation.
        • Custom REST Endpoints
          • You may now easily create custom REST endpoints using Velocity files.
          • All HTTP Methods for RESTful services are supported, including GET, POST, PUT, PATCH, and DELETE.
          • Velocity methods have been added which simplify the generation of output in JSON and XML formats for your custom endpoints.
          • A /vtl/dynamic REST endpoint has been added which allows you to render output from HTML and Velocity code dynamically.
          • For more information, please see the Scripted Custom Endpoints documentation.
        • GraphQL REST API
          • A REST API has been added that supports the GraphQL dynamic query language for retrieving content.
          • GraphQL allows you to selectively retrieve and arrange the content and fields you retrieve, enabling you to reduce the size of responses and insulate your applications from future changes to your dotCMS content and Content Types.
          • For more information, please see the GraphQL documentation.
        • Field Variables for Content Type Fields
          • You may now add "Field Variables" to fields in your Content Types.
          • These Field Variables can be used to distinguish and handle fields of the same field type differently, either within the same Content Type or among different Content Types.
          • The Field Variables for a Content Type field may be accessed from both Velocity code and Plugins.
          • These field variables are now used to allow customization of the WYSIWYG field, and are intended to be expanded to allow customization of other Content Type fields in the future.
        • WYSIWYG Field Customization on a per-Content Type and per-Field Basis
          • You may use the new Field Variables feature to specify tinyMCE customizations for each WYSIWYG field individually by specifyin a Field Variable named tinyMCEProps, which will be used to initialize the WYSIWYG field editor.
          • For more information, please see the WYSIWYG Field documentation.
        • CORS Header Configuration
          • You can now configure headers to send with CORS requests.
          • Headers can be configured as global defaults, and can be overridden for specific endpoints.
          • For more information, please see the CORS Header Configuration documentation.

        Fixes

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

        • Fixed an issue that could cause a Null Pointer Exception during Push Publishing under some conditions (#9110)
        • Fixed an incorrect message when incorrect values were entered while adding a new Language (#13168)
        • Fixed an issue which prevented the site selector list from being updated when using Login As (#14116)
        • Fixed an issue preventing the site selector from updating when using the Login As feature (#14116)
        • Fixed an issue which could cause different language versions of the same content to be saved separately (#14966)
        • Fixed an issue preventing a limited user from creating a new Content Type under certain conditions (#15285,#15308)
        • Fixed an issue which could cause an error on a Page if a Container on the Page was archived (#15331)
        • Fixed an issue causing Push Publish to fail in specific circumstances after adding a new Language (#15359)
        • Fixed an issue preventing the History and Permissions tabs on Events from being refreshed on save (#15439)
        • Fixed an issue preventing limited users from using the Device Preview feature (#15474)
        • Fixed an issue which could cause a new Site Search to fail (#15475)
        • Fixed an issue preventing Pages at the root of the site from being selectable as URL Map Detail pages (#15482)
        • Corrected some widget sorting issues in the Page Editor (#15486)
        • Fixed an issue which could cause an error when trying to rearrange or un-check the Required property on a Category field (#15504)
        • Fixed an issue which could prevent a limited user from navigating public pages in the back-end (#15506)
        • Fixed some issues which could cause Elasticsearch indexing to fail to complete (#15512)
        • Fixed an issue which could cause content save to freeze with a custom list of Languages (#15624)
        • Fixed an issue which could cause the Page Editor to render incorrectly when Velocity errors exist on the Page (#15640)
        • Fixed an issue which caused Push Publishing errors when Tags contained single quotes (#15792)
        • Removed the server name and port from generated URLs, to support containerization and applications behind proxies (#15833)
        • Synchronized the properties returned by the Page API /json and /render methods (#15928)

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

        Deprecated Features

        The following features have been officially deprecated in dotCMS 5.1.0. These features have not been removed, and still work normally, but are no longer fully supported, and may be removed in a future dotCMS release.

        • Legacy Relationships and Legacy Relationship fields
          • Legacy Relationships and Legacy Relationship fields on Content Types are both officially deprecated.
          • You may migrate all Legacy Relationships to the new Relationship Fields at any time.
          • Legacy Relationships, Legacy Relationship fields, and Velocity methods referencing Relationship name rather than Content Type field name will all continue to supported for a period of time.
            • However Legacy Relationships and code should be converted to new Relationship fields as soon as possible, to ensure forward compatibility with future releases.
        • CommentActions class
          • The CommentActions class has been deprecated and is no longer shipped with the dotCMS distribution. Customers with legacy code that relies on this class should add the class using a plugin.

        Additional Changes and Improvements in dotCMS 5.1.0

        • Updated the Push Publish Workflow sub-Action dialog to allow Push Delete with Workflows.
        • Added navigation crumbtrails to the back-end user interface.
        • Made several improvements to the content search listing in the Page Editor.
        • Improved indexing performance when saving and publishing content.
        • Added "/servlet/" to the list of paths for the DefaultBackEndLoginRequiredWebInterceptor (#15548)
        • Added the hostName to the results in the /es/search REST endpoint (#15574)
        • Added a titleImage property to all content, allowing easy access to images on different Content Types (#15575)
        • Added additional logging for Push Publishing (#15595)
        • Improved error handling when a new Page is created with a URL that is already in use (#15951)
        • Added the ability for the /es/search REST API to return working as well as live content (#15982)
        • Upgraded the contentlet API to return related content for retrieved content items (#9411)
        • For source code distributions, the default path for functional tests was changed from /servlet/test to /dotTest (#15548)
        • Angular has been upgraded from version 4.4.6 to version 7.2.0.
        • PrimeNG has been upgraded from version 4.3.0 to version 7.0.3.
          • There were no UI changes in relation to this upgrade; the upgrade was made to maintain currency and compatibility only.

        dotCMS 5.0.3

        Available: Nov 15, 2018

        dotCMS 5.0.3 is a maintenance release to fix several issues which affected some customers with the dotCMS 5.0.2 release.

        It is recommended that all customers running the 5.0.0, 5.0.1, or 5.0.2 releases upgrade to dotCMS 5.0.3 as soon as possible.

        Fixes

        • Site selector did not update to show appropriate sites when using the Login As feature (#14116)
        • Push publishing a file or page could fail after push removing the parent folder (#15022)
        • In some circumstances, Categories referenced by a content type were not pushed by dependency with the content (#15172)
        • The Elasticsearch transport port and http port configuration settings were not honored when using auto-wire clusters (#15277)
        • The list of Widget Types was not sorted when adding a Widget to a Page (#15290)
        • In the Content Type editor, Category fields could not be renamed without also changing other field parameters (#15309)
        • Static publish to an Amazon S3 bucket of pages using Sass could fail to render correctly (#15310)
        • Archiving a container which was used on a Page could cause an error when the Page was accessed on the front-end (#15331)
        • Image, Textarea and WYSIWYG fields on existing content could not be completely cleared in the content editing screen (#15340, #15353)
        • Some OSGi plugins placed in the felix/load directory were not loaded properly when dotCMS was started (#15358)
        • The Base Types list in the Content Types tool was not ordered correctly (#15382)
        • In some cases, not all appropriate Bulk Workflow Actions were displayed for a limited user (#15385)
        • Applying "Cascade Permissions" to a Site from the Roles & Tools screen did not update child permissions (#15389)
        • The NavResource REST API did not return a nested JSON object (#15390)
        • In the Page ditor, when any Container included Velocity code with errors, an error was displayed for the whole Page instead of for just the problem Container (#15395)
        • If the Template set for a Page did not exist, the template for the Page could not be changed (#15401)
        • The Host Content Type was incorrectly allowed to be moved from the SYSTEM HOST (#15410)
        • If a Content Type had a detail page that did not exist, the content would fail to index properly (#15423)
        • When a user session expired, the automatic redirect to the Login page did not work correctly (#15437)
        • Limited user was unable to reorder menus in the Page editor when any Page was locked by another user (#15450)
        • Device preview could fail for some users in some browsers (#15474)
        • Running a new Site Search job could fail in some circumstances (#15475)
        • When setting the Detail Page for a Content Type, pages on the root of the site could not be selected (#15482)
        • The PersonaTool.getPersonas() method did not work for unauthenticated (front-end) users (#15484)
        • Reorder of fields in a Content Type could fail in some circumstances (#15504)
        • Within the Page editor, Navigation on the Page sometimes did not work properly for limited users (#15506)
        • In some conditions, an Elasticsearch reindex could get stuck (#15512)
        • In some cases limited users could not view content which was permissioned to be viewable by unauthenticated users (CMS Anonymous) (#15523)

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

        Deprecated Features

        The following features have been officially deprecated in dotCMS 5.0.3. These features have not been removed, and still work normally, but are no longer fully supported, and may be removed in a future dotCMS release.

        • H2 database is deprecated.
          • The H2 database was previously fully supported for development only.
          • With the release of dotCMS 5.0.3, the H2 database is now officially deprecated, even for development.
          • The H2 database will be replaced in a future version with a dotCMS Docker image which uses a Postgres database.

        dotCMS 5.0.2

        Available: Sep 20, 2018

        dotCMS 5.0.2 is a maintenance release to fix several issues which affected some customers with the dotCMS 5.0.1 release, and to address two newly identified security issues.

        It is recommended that all customers running the 5.0.0 and dotCMS 5.0.1 releases upgrade to dotCMS 5.0.2 as soon as possible.

        Fixes

        • Added a check to the startup process to ensure that existing assets are not deleted if the configuration of the existing site is not correct (#14819).
        • Fixed an issue preventing sorting of content by Workflow Step if any content item was set as [Not Assigned] (#14897).
        • Fixed an issue which caused an error when attempting to push remove a Site (#15013).
        • Added the ability to specify a Default Template which is used by default when creating a new Page (#15031).
        • Fixed an issue could cause content to be saved twice when the content API was used to trigger a Workflow Action (#15053).
        • Fixed an issue which prevented the options from updating after folder permissions were changed (#15055).
        • Fixed an issue which could prevent relative paths in stylesheet links from working properly (#15141).
        • Fixed an issue which could cause loss of a binary field value in certain circumstances on a content with a required relationship (#15157).
        • Fixed an issue which could prevent proper import or export of Categories containing non-Latin characters (#15174).
        • Fixed an issue which could prevent push publishing of copied sites (#15175).
        • Fixed an issue which could cause zero length files when doing a static push without a language variable in the bucket name (#15176).
        • Fixed an issue which could cause an unnecessary close confirmation prompt when content was not edited (#15177).
        • Fixed an issue which could cause a Workflow Action popup to display incorrectly in some circumstances (#15184).
        • Fixed an issue which could sometimes prevent Workflow Tasks from displaying in the task portlet (#15186).
        • Fixed an issue which could prevent a content from being updated properly via the Workflow REST API in some circumstances (#15192).
        • Fixed an issue causing the wrong Content Type to initially display when editing a content item (#15198).
        • Fixed an issue causing incorrect display of content changes when a value for a Required field was not supplied (#15199).
        • Fixed an issue which could prevent widget pre-execute code from displaying in some circumstances #15202).
        • Fixed an issue preventing the Detail Page of a Content Type from displaying properly when using a Community license (#15217, #15195).
        • Fixed an issue which could cause display errors when certain pre-defined names were used for Velocity variables (#15219).
        • Improved Sass performance when using the LibSass compiler by using fully minified (compressed) CSS (#15222).
        • Changed the priority in which Vanity URLs resolve paths, to prevent potential issues in some circumstances (#15223).
        • Fixed an issue which could prevent the NavTool from working properly when a Page was viewed in edit mode (#15229, #15162).
        • Fixed an issue which could cause Elasticsearch operations to become stuck (#15230).
        • Fixed an issue preventing the LoginAs feature from working properly with some Role configurations (#15237).
        • Fixed an issue preventing viewing of content in a custom workflow if the dotCMS instance did not have a valid license (#15238).
        • Removed an unnecessary message regarding Workflow Actions when viewing a Site (#15272).
        • Fixed an issue which could make a widget incorrectly appear to have not been updated after an edit (#15283).
        • Fixed an issue which could cause an error when a specific method is called under certain circumstances within a plugin (#15297).

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

        Security and Privacy Updates

        For more information on security issues resolved in this release, please see the Known Security Issues documentation.

        Details of the two security issues fixed in this release are currently being withheld, but will be added to the Known Security Issues documentation as soon as affected customers have been notified and have had an opportunity to upgrade or mitigate the issues.


        dotCMS 5.0.1

        Available: Aug 21, 2018

        dotCMS 5.0.1 is a maintenance release to fix several issues which affected some customers with the dotCMS 5.0.0 release.

        Fixes

        • Improved messages when an attempt is made to create a new Language with the wrong values (#13168).
        • Restored previous behavior auto-selecting a recently edited Content Type in the Content Search window (#13719).
        • Fixed incorrectly displayed actions when using the Workflow "Who can use" filter (#14534).
        • Improved feedback to the user when the user does have permissions to edit a Content Type (#14999).
        • Fixed an issue which could cause the Default Host to be lost after a push under certain conditions (#15020).
        • Fixed an issue preventing futre Time Machine snapshots from showing the correct content in some circumstances (#15014).
        • Fixed a minor issue with the Content Search listing after editing content (#15064).
        • Fixed an issue preventing the deletion of Content Types in dotCMS Community Edition (#15090).
        • Fixed an issue with the XMLTool Viewtool (#15091).
        • Fixed an issue with the Page edit screen when running dotCMS on Windows Server (#15097).
        • Fixed an issue preventing the addition of files to some custom File Content Types (#15105).
        • Fixed an error which could prevent the creation of new tags when adding tags using double-byte languages (#15107).
        • Fixed an issue which caused errors in the Containers screen under certain conditions (#15114).
        • Fixed an issue which could cause errors in the Content Types Tool after a push (#15124).
        • Fixed an issue preventing the Save Draft Workflow sub-action from working properly with some Content Types (#15129).
        • Fixed an issue preventing servlet OSGI plugins from being added properly (#15145).
        • Fixed an issue which could prevent the creation of subcategories under multilingual Category names (#15148).

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


        dotCMS 5.0.0

        Available: Aug 8, 2018

        dotCMS 5.0.0 is a major release which includes some major upgrades and new features, performance and stability improvements, and upgrades to a number of key components.

        Important Changes

        A number of important changes in dotCMS 5.0.0 configuration may impact your performance when upgrading an existing site. Please read the documentation sections on all of these changes before upgrading from a previous release.

        Features No Longer Supported

        Support for a number of previously deprecated features has been removed in dotCMS 5.0.0. These include, but are not limited to: Internet Explorer 11 access to the dotCMS back-end, and CMIS.

        • These features no longer function, and libraries associated with these features have been removed from the dotCMS distribution.
        • For additional details on libraries which are no longer included with dotCMS, please see the Features and Dependencies Removed from dotCMS 5.0.0 section below.

        Configuration Changes

        The following important changes have been made to configuration in dotCMS 5.0.0:

        • The default logging configuration has changed to log all messages to the Tomcat catalina.out file, in addition to the dotCMS logs.
          • This logging configuration makes it easier to monitor and debug development and staging environments, but is not recommended in production as the catalina.out file may grow very large.
          • For production, we suggest replacing default log4j.xml with the production example in the dotCMS Github Repository.
        • Elasticsearch configuration has been moved to the standard elasticsearch.yml file, which is located in the "/dotserver/tomcat-8.5.32/webapps/ROOT/WEB-INF/elasticsearch/config" folder within the dotCMS distribution.
          • If you have made changes to your Elasticsearch configuration, including changing the location of the Elasticsearch indexes or creating custom mappings, you must edit the elasticsearch.yml file to reflect these changes.
        • JWT signature keys have changed, and may be updated automatically.
        • The default database configuration now uses DBCP1 (Tomcat connection pooling).
          • It is recommended that you review your database pool configuration to ensure it is correct.
          • If you configure your database by modifying the default context.xml file shipped with dotCMS, please see the Tomcat JDBC Pooling documentation for information on how to configure your database pool.
        • OSGI Default Behaviors have Changed
          • dotCMS no longer attempts to expose/export all internal libraries by default.
            • If you have an OSGI plugin that relies on dotCMS internal libraries, then either you must modify your plugin to provide its own versions of the libraries, or you must expose the internal libraries you need via a fragment or in the osgi-extras.conf file.
          • Tomcat context reloading is now set to false by default.
            • If you wish to add REST endpoints via OSGI, you will need to change this property to true in your context.xml file.

        Changes to Default Behavior

        In addition, the following differences in default behavior in dotCMS 5.0.0 may change your expectations and require a review of your administration practices. Please review all of these changes before upgrading from a previous release.

        • Workflow Changes
          • Workflows have been significantly upgraded, and all existing content types and workflow schemes will be upgraded to use the new Workflow features automatically.
          • As part of this upgrade, the following changes will be made to all existing Content Types:
            • Default content actions have been replaced with a new System Workflow.
              • All Content Types which previously used a non-mandatory Workflow scheme will be assigned to both the existing Workflow scheme and the new System Workflow (which duplicates the previous default content actions).
              • However Workflows now behave differently, so "default actions" which were previously available when using non-Mandatory workflows may not be available in all the Workflow steps they were previously available in, and you may need to modify your custom Workflows to ensure all required actions are still available to the appropriate users.
              • For information on how to modify your Workflows to ensure that all previously available default actions are still available, please see the Upgrading to dotCMS 5.0 documentation.
            • Mandatory workflows have been replaced with new functionality.
              • You may now assign multiple Workflows to the same Content Type. The previous Mandatory Workflow functionality is now provided by simply assigning a single Workflow to a Content Type.
              • Therefore all Content Types which previously used a Mandatory Workflow scheme will remain assigned only to the same Workflow scheme they were previously assigned (the mandatory Workflow), but the Workflow itself will no longer be identified as Mandatory. Content Types previously assigned a Mandatory Workflow scheme will not be assigned to the new System Workflow, and so will mimic the behavior of Mandatory workflows.
          • As part of this upgrade, the following changes will be made to all existing Workflow Schemes:
            • The Mandatory option has been replaced with new functionality. Workflow schemes previously configured as Mandatory Workflows will no longer be explicitly designated as Mandatory. Instead, since each Content Type may be assigned multiple Workflow Schemes, you will provide the same functionality as a Mandatory Workflow by only assigning a single Workflow Scheme to a Content Type.
            • The Requires Lock option has been removed. All existing Workflow actions configured with the Requires Lock option will have a new "Save content" workflow sub-action added to them, which performs the same function as the previous Requires Lock option.
        • Elasticsearch Changes
          • Elasticsearch has been upgraded from version 1.7.3 to version 6.1.3
          • As a result of this change, your existing Lucene and Elasticsearch queries may need to be modified to work properly in dotCMS 5.0.
            • It is strongly recommend that you test all your queries and content pulls after upgrading to dotCMS 5.0.0.
          • For details on required changes, please see the Upgrading to dotCMS 5.0 documentation.
        • REST API Changes
          • Elasticsearch Index API Endpoint Changed
            • The URL to access the esindex endpoint has changed from /api/esindex to /api/v1/esindex.
            • The previous endpoint has been deprecated.
            • For more information, please see the REST API to Manage Indexes documentation.
        • Changes to Relationship Editing
          • Once a relationship has been established between two different Content Types, the relationship between the two content types may no longer be switched (though the Relationship parameters may be changed)
          • For more information, please see Github issue #14296 and the Relationships documentation.

        New Features

        In addition to the Important Changes listed above, the following additional new features have been added in dotCMS 5.0.0:

        • New Edit Mode
          • Customizable Per-page Layouts
          • Drag-and-drop Page Editing
        • New Workflows
          • Drag-and-drop Workflow builder
          • Workflow Action filter to display actions available to specific users and Roles
          • Multiple Workflow Schemes may be assigned to a single Content Type
          • The same Workflow Action can be assigned to multiple Workflow Steps
          • Workflow Actions can be visible based on the state of the content
          • Workflow Action permissions can be assigned based content permissions
            • For example, you can now allow a Workflow Action to be used by all users who have Publish permissions on the content.
          • Workflow Schemes can now be copied and deleted
          • Workflow Scheme names are no longer unique, so you may create multiple Workflow Schemes with the same name
          • Workflows Tasks and actions now respect content language
          • New "Save Draft" Workflow sub-action
          • The "System Workflow" (the default Workflow for all content types) is now editable (but always resettable)
          • Workflow Batch Actions enable you to easily perform appropriate bulk actions on any selected group of content, for any Workflow
            • Note that Workflow Batch Actions are only available on dotCMS Enterprise editions
          • New Workflow REST API endpoint
        • New Drag-and-drop Content Type Editor
          • A new Content Type editor allows drag-and-drop creation and management of Content Type fields.
          • The previous Content Type editor is still supported, and customers who upgrade from a previous version of dotCMS will continue to see the old Content Type editor by default.
          • If you would like to access the new Content Type editor, you must add the Tool to the appropriate Roles on your dotCMS instance (via the System -> Roles & Tools screen).
        • New Embedded Google Analytics Reporting

        Fixes

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

        Features and Dependencies Removed from dotCMS 5.0.0

        A number of previously-deprecated features and dependencies have been removed from dotCMS 5.0.0.

        For customers which only use the standard dotCMS distribution, these changes will likely have no impact. However for customers which build dotCMS from source or who use custom plugins, these changes may impact your build process. If you do build dotCMS or custom plugins, please review the below list to identify any dependencies which may affect your build process.

        Removed Libraries

        • Apache Solr
          • Lucene is fully supported by Elasticsearch 6.1, so Solr is no longer required.
        • CMIS support
        • Drools
        • Groovy
        • Hadoop
        • Jasper Reports
        • Jboss Rules / Legacy JBoss Cache
        • Captcha tools
        • Tika (now shipped as an osgi jar)

        Removed Dependencies

        All of the following libraries have been removed from the dependencies.gradle file used to build dotCMS, and these libraries are no longer shipped with the dotCMS distribution:

        • Abdera (dot.abdera-**)
        • mapdb (org.mapdb)
        • Antlr (dot.antlr)
        • Apache Solr (dot.apache-solr-**)
        • OpenCMIS (dot.chemistry-commons and dot.chemistry-opencmis-**)
        • Drools (dot.drools-**)
        • Groovy (dot.groovy-all)
        • Hadoop (dot.hadoop-dev-**)
        • Jasper Reports (dot.jasperreports)
        • Jboss Rules / Legacy JBoss Cache and dependent libraries (dot.jboss-common-core, dot.jbosscache-core, and dot.jboss-logging)
        • Captcha (dot.jcaptcha-mod and dot.simplecaptcha)
        • Internal dotCMS Lucene-related libraries (dot.lucene-**)
        • nekohtml (dot.nekohtml)
        • Verisign (dot.Verisign)
        • xalan (dot.xalan)
        • Tika (dot.tika-app)
        • Batik Animation (batik-anim)
          • Note: Only the batik-anim jar was removed. Other batik jars, including imageio-batik and batik-rasterizer, were not removed.

        Privacy and Security Updates

        The following changes in dotCMS 5.0.0 may have privacy implications for your existing dotCMS installation. We recommend that you review these changes, and if necessary modify any appropriate content, to ensure your site maintains compliance with any privacy standards and regulations you adhere to.

        • JWT signature keys have changed, and may be updated automatically.
          • If you have not explicitly changed your JWT signature key in dotCMS 4.x, your JWT signature key will change when you upgrade to dotCMS 5.0.0.
            • On initial startup, dotCMS will check your JWT signature key, and if has not been changed from the default key, dotCMS will generate a new random secret signing key.
          • Your JWT secret signing key will now be stored in the file "/assets/server/jwt_secret.dat" within the dotCMS distribution.
        • Permissions required to create and edit Content Types have changed.
          • In order to create a new Content Type, a user must now have both ADD CHILDREN rights on the Site and EDIT PERMISSIONS rights on both the Site and the Content Type.
          • In order to edit or delete an existing Content Type, a user must now have EDIT_PERMISSIONS rights on the Content Type.
        • The default expiration time for API Tokens has been increased to ten years.
          • The expiration for these tokens can be changed by setting json.web.token.max.allowed.expiration.days property in the dotmarketing-config.properties file.

        Deprecated Features

        The following features have been officially deprecated in dotCMS 5.0.0. These features have not been removed, and still work normally, but are no longer fully supported, and may be removed in a future dotCMS release.

        • Spring libraries and classes are deprecated for use "out of the box".
          • Spring support in general is NOT deprecated, so use of Spring packages is still supported.
          • However it is now expected that you include any Spring packages/classes you need via any plugin that uses Spring and/or Spring MVC.
        • The current (Page-level) "What's New" feature is officially deprecated.
          • It is planned for this feature to be replaced by an improved What's Changed feature in a future release.

        Additional Changes and Improvements in dotCMS 5.0.0

        • Colors displayed in the back-end UI can now be changed in the System -> Configuration Tool.
        • Postgress 10 is now supported (#14372)
        • Containers may now be included multiple times in the same Template.
        • There is a new Containers REST API.
          • This API provides a number of new endpoints, including an endpoint which allows you to render individual content items via a Container without placing the content inside a Container on a Page.
        • Elasticsearch has been upgraded from version 1.7.3 to version 6.1.3
          • Please note that this was a major upgrade, and some changes may be needed to existing Elasticsearch queries in order to work properly in dotCMS 5.0. Please see the Upgrading to dotCMS 5.0 documentation for more information.
          • The Elasticsearch cache may now be flushed from the System -> Maintenance screen.
        • Tomcat included in the dotCMS distribution has been upgraded to version 8.5.32.
        • Log4j has been upgraded to version 2.8.2.
          • This new version supports low object allocation logging, improving memory use and performance.
        • The OSGI felix library has been upgraded to version 5.6.10.
        • Hazelcast libraries (used with the Hazelcast cache provider) have been upgraded to version 3.9.2.
        • Amazon Web Services libraries (used with Static Publishing) have been upgraded to version 1.11.66.
        • The "Content Types" and "Dashboard" tools have been replaced with new versions.
          • The previous versions of both tools are still included, but have been renamed to include "(Legacy)" to distinguish them from the new versions of the tools.
          • The legacy versions of both these tools are officially deprecated.
        • Sass files no longer require the /DOTASS prefix when references within a theme.
          • Sass files may now alternately be referenced using a .dotsass file extension, which allows them to be referenced using a relative path (e.g. /application/themes/ski-resort/sass/main.dotsass).
        • The LanguageAPI viewtool has been renamed LanguageViewtool.
          • This should not affect users unless they were calling the viewtool in java code
        • Tika has been upgraded to version 1.17 and moved to a built-in OSGI service.
        • Tika (which is used for full text and metadata extraction of pdfs, word docs and other binary file types) is now provided as a built in OSGI service rather than integrated into the dotCMS core product.
          • Making Tika an OSGI service enables encapsulation and segregation of a large number of libraries (which Tika is dependent on) from the dotCMS classpath. This enables future upgrades to Tika and its dependent libraries to be made without impacting other functionality in the system.
        • Velocity Java Code has been Repackaged
          • All dotCMS velocity Java code has been repackaged and is now contained in the com.dotcms.rendering.velocity.* jars.

        dotCMS 4.3.3

        Available: Apr 20, 2018

        dotCMS 4.3.3 is a maintenance release to fix some important issues which affected some customers with the dotCMS 4.3.x releases. It is recommended that all customers running 4.3.x series releases upgrade to release 4.3.3 as there are important fixes in this release.

        Fixes

        The 4.3.3 release includes fixes for the following reported issues introduced in the dotCMS 4.3.x series:

        • Resolved an issue which could prevent images from being retrieved via Velocity code from non-default language versions of content (#12820).
        • Resolved an issue which could cause the Integrity Checker to fail in specific circumstances with mismatching Roles on the sender and receiver (#13067).
        • Resolved an issue which could allow the working version of content to be retrieved incorrectly via the REST API (#13131).
        • Resolved an issue preventing old versions of content from being deleted when a specific language version of the content was deleted (#13682).
        • Resolved an issue which could cause the push of Categories to fail in certain circumstances (#13722).
        • Improved the handling of database connections to prevent the potential premature connection closure (#13792).
        • Increased the space used to display related content in the Relationships tab to enable the full title to be viewed (#14060).
        • Resolved an issue preventing limited users from adding Containers they have permission to when editing a Template (#14134).
        • Resolved an issue which could cause the Fix Assets Inconsistencies tool to fail in some circumstances (#14141).
        • Resolved an issue which could cause the "Four Eyes" Workflow action to move content to the next step prematurely (#14144).

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