ChangeLogs

Last Updated: Apr 7, 2022
documentation for the dotCMS Content Management System
            Older Versions →

LTS dotCMS releases

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

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

Version Release Date End of Life Date
v22.03.1 LTS May 11, 2022 Apr 11, 2024
v21.06.7 LTS Mar 9, 2022 Jul 13, 2023
v5.3.8.10 LTS Mar 8, 2022 Jul 2, 2023

Agile dotCMS 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.

Version Release Date End of Life Date
v22.05 May 5, 2022 May 5, 2023
v22.03 Mar 14, 2022 Mar 14, 2023
v22.02 Feb 9, 2022 Feb 9, 2023
v22.01 Jan 10, 2022 Jan 10, 2023
v21.11 Nov 15, 2021 Nov 15, 2022
v21.10 Oct 11, 2021 Oct 11, 2022
v21.09 Sep 7, 2021 Sep 7, 2022
v21.08 Aug 4, 2021 Aug 4, 2022
v21.06 Jul 5, 2021 Jul 5, 2022
v21.05.1 Jun 8, 2021 Jun 8, 2022

dotCMS 22.03.1 LTS

Available: May 11, 2022

22.03.1 updates the recent 22.03.0 LTS release. Its changes are primarily backports from this month's 22.05 agile release.

Bugfixes:

  • Database connections now release properly in accordance with DB_MIN_IDLE environmental variable.
  • Fixed error preventing undeployment of OSGi plugins.
  • Pages built with URL Mapped content are now correctly created on a full-site Static Push.
    • URL Mapped content likewise shows up properly in site search indices when including folders.
  • Fixed a case where specific conditions could cause drafted content to fail to Push Publish.

Content:

  • Removed limit on number of widgets or forms displayed in Content Selector popup.
  • Unique fields on global Content Types can now be specified as unique globally or unique per site.

dotCMS 22.05

Available: May 5, 2022

As the flagship feature of version 22.05, we unveil our new Block Editor, a JSON-based WYSIWYG editor.

Inspired by such interfaces as WordPress's Gutenberg Editor, the Block Editor is an easy-to-use, feature-rich interface for creating and editing content — whether text, images, or any other custom content defined through dotCMS. We hope you'll enjoy it!

Our demo site has been updated to feature the Block Editor on blog posts. Test it out for yourself with email address admin@dotcms.com, password admin.

Bugfixes:

  • Resolved Javascript console errors that resulted from adding a pre-existing widget to a page.
  • Fixed Enterprise Edition license check misfiring on some page edits.
  • Fixed bundle errors when reimporting a previously imported folder that has been renamed.
  • Fixed the Show Archive checkbox in the Templates section.
  • Pages built with URL Mapped content are now correctly created on a full-site Static Push.
  • Fixed a case where specific conditions could cause drafted content to fail to Push Publish.

Visual fixes:

  • Fixed cases of contextual menus cutting off at the bottom of their parent display pane.
  • Improved display for “Add Row” button in the Content Type creation interface.
  • License info renders more cleanly on Create Content modal dialog.

Content:

  • New Block Editor (see above).
  • Added ability to copy Content Types.
  • Replaced Vanity URL base content type's Site field with a Host Folder field.
  • Removed limit on number of widgets or forms displayed in Content Selector popup.
  • Page titles now update to display the name of content being edited; multitab without fear!
  • Unique fields on global Content Types can now be specified as unique globally or unique per site.
  • Optimized saving procedures to improve performance.
  • Improved clickability when relating content — click anywhere in the list's rows to toggle!
  • Implemented storage of content info as JSON for MSSQL databases — as previously implemented for PostgreSQL.

Plugins:

  • Improved OSGi plugin loading in server-cluster context.
  • Fixed error preventing OSGi plugin undeployment.
  • Fixed ability to upload multiple OSGi assets at once.

Enhancements & Adjustments:

  • Changed folder handling to enforce knowable & consistent folder ID behavior.
  • Added ability to create a whitelist of acceptable keys for Key/Value fields.
  • Reinstated Publishing options in Template editor.
  • JSON handling: Removed GSON dependency in favor of Jackson.
  • Added integration tests for Integrity Checker.
  • Edit Mode Anywhere app no longer sends the page.rendered property on POST unless enabled in the app.
  • Optimized routines for bulk adjustment of permissions.

dotCMS 22.03.0 LTS

Available: Apr 11, 2022

(This changelog represents all changes since 21.06, spanning nine months of agile builds.)

Content Management

  • Content now stored as JSON, removing limits on the number of fields.
  • All dates in the system are now stored with time zone information.
  • Enabled search and aggregation on key-value pairs.
  • Added “bulk move” workflow action.
  • Added a library of icons for Content Types.
  • Added a tool for visually comparing different versions of content; access it via the History tab.
  • Added a new “what's changed” library in support of the comparison tool.
  • Introduced Headless Widgets: A single widget can now produce HTML or JSON depending on the rendering context.
  • Added default paths for image or file fields, helping editors quickly find files without digging through a file tree.
  • Bulk actions now display job progress.
  • Added thumbnails to content search listings.
  • Improved SVG handling.
  • Rules can now be used to rewrite URLs.

Page Building

  • Added a slick new Template designer; building a layout has never been simpler.
  • Content palette now allows for simple, click-and-drag content reuse.
  • You can now drag and drop local images or files into pages.

System Management

  • Added support for Bash scripts for CI/CD. You can bootstrap environments with:
    • Sites
    • Languages
    • Content Types
    • Folders
    • Files
    • Templates
    • Containers
  • Consistent identifiers: Most dotCMS unique identifiers are now assigned based on their paths or unique values. For example, if you create the file demo.dotcms.com/my-first-image.jpg on any dotCMS instance, it will have the same identifier.
  • dotCMS can now generate secure passwords for back-end users.
  • You can now download your entire installation — including assets and a full SQL dump — from the back end. Access this feature on the admin panel under System > Maintenance > Tools.
  • Default Language can now be changed from the back end
  • Enabled users to configure most aspects of dotCMS via environment variables, including database configuration, mail configuration, and more.
  • Updated Docker image and configuration.

Apps / Integrations

  • dotCDN is now built in; view usage stats and manage your cache under the admin panel's Dev Tools.
  • App secrets can now be imported and exported.
  • New app available for Prerender integration.

Performance

  • Reimplemented Redis Cache and Redis Pub/Sub.
  • Garbage collection is now in the capable and “pauseless” hands of Shenandoah GC. This change can be overridden by passing other options to the JVM.
  • Image filters are more performant — especially with large images.
  • Sped things up by removing Sync Block from BlockPageCache.
  • GZIP now enabled by default.
  • $dotcontent.find($identifier) now relies on cache rather than elasticsearch.
  • Velocity rendering now uses cached binary metadata, requiring fewer file system calls.

Push Publishing and Bundles

  • Added Bundle Manifests: See exactly what was pushed and why in any given bundle!
  • Added a push-publishing listener, which fires from the receiver when push publishing is complete.
  • Enabled bundle delete and cleanup.
  • Large bundles are more performant: faster and more stable!

OSGi Plugins

  • Reconfigured to rely on OSGi Extras; fragments are no longer needed, though still supported.
  • SAML startup does not conflict with other OSGi plugins.

GraphQL

  • Static GraphQL cache can rebuild lazily and will return stale data as the cache is refreshed in the background.
  • Now supports dotAssets for file or image fields.

Breaking Changes

  • Requires Java 11 to run.
  • Only PostgreSQL and MSSQL are supported.
  • Hazelcast cache transport layer has been removed by default. We recommend relying on a PubSub provider — either Redis or PostgreSQL — to wire your clusters. If you are running with PostgreSQL as your primary DB, there is no need to do anything. If you are running against MSSQL, we suggest running a lightweight PostgreSQL or Redis instance to provide network cache invalidations. If required, Hazelcast cache transport can be re-enabled by mounting a custom hazelcast-config into your docker image. This is the last major LTS version that will support Hazelcast as a cache transport.
  • Installations using Docker will need to update their configuration options, as they have changed.
  • Docker now runs dotCMS with the user:group 65001:65001. You will need to chown any file shares that you have mounted in in order for docker to be able to read/write assets.
  • $jsontool and $xmltool calls to localhost will be blocked by default. This behavior can be changed through a config variable.
  • Hostnames for sites are now supposed to be immutable and should not be changed once set. The hostname field for sites will now only accept DNS-valid characters.
  • /api/v2/users was incorporated into /api/v1/users. Any calls to /api/v2/users should be redirected to /api/v1/users.

dotCMS 22.03

Available: Mar 14, 2022

dotCMS 22.03 is made up of 44 fixes, improvements and new features. For more detail, the whole list of issues included in dotCMS 22.03 can be found on GitHub.

New Features and Enhancements

  • Moved to Shenandoah Garbage Collector. Shenandoah is a “pauseless” garbage collector that also has the benifit of quickly returing unused memory back to the underlying operating system, rather than greedly holding on to it. Operationally, this results in dotCMS needing/using less memory over time, which is very important for density when running dotCMS in orchestrators. This change in the default garbage collection can be overridden by passing other options to the JVM.
  • Better FS Caching. Binary file properties that are referenced in Velocity, e.g. $content.image1.width now rely on the assetMetadataCache to return things like size and image dimensions, rather than relying on slower operations that use the filesystem and often traverse the network with NFS.
  • Legacy Data Model Improvements. Folders no longer rely on hiberate object mapping to persist data.
  • Docker Image now uses Amazon's Corretto OpenJDK 11 under the covers. This change was made because Amazon's OpenJDK is supported over a long term and also contains a backported version of the Shenandoah Garbage Collector, which dotCMS (docker) now uses by default. This change should not affect how dotCMS is launched or run.
  • It is now possible to disable drag and drop image upload from the WYSIWYG field. To do this, you need to add a field variable dragAndDrop with the value set to false.

Security

  • When writing tmp files for newly uploaded files, the filenames are now scanned and rejected if they contain directory escaping characters, e.g. ../.

Changes/Improvements

  • Ticked up our versions of Angular to 13.1.3 and PrimeNg to v13.1.0.
  • CalendarEvents content type can now be deleted without causing a system error.
  • Elasticsearch Client was upgraded to v7.10.2.
  • Users with both backend and frontend roles can now preview/edit pages.
  • Langauge Keys for backend i18n are now stored using the dotCMS version as the key, and will be automatically refreshed when the dotCMS version updates.
  • The background is pleasingly blurred when a modal window is popped up in the backend.

Breaking Change


dotCMS 21.06.7 LTS

Available: Mar 9, 2022

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

Fixes

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

Issue Github Link
[Site Copy] : Copying a Site randomly fails #21204
db passwords with characters (specifically @ and possibly others) will break pub/sub due to the connection string #21363
Add the ability to stop/abort a workflow on velocity script actionlet #21252
Past Time Machine not working #21097
SAML - Allow expression substitution from SAML roles mapped to dotCMS roles by role key #20773
Unable to push publish user #20805
We need to obfuscate some environmental variables #20757
Sanitizing file name #21791
Large Bundles make the viewing publishing queue slow #20971
[Push Publishing] : Single quote in content's title breaks JavaScript code in the portlet #21699

dotCMS 5.3.8.10 LTS

Available: Mar 8, 2022

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

Fixes

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

Issue Github Link
Obfuscate Environmental Variables System Info Portlet #20757
SAML - Allow expression substitution from SAML roles mapped to dotCMS roles by role key #20773
Unable to push publish user #20805
Past Time Machine not working #21097
[Site Copy] : Copying a Site randomly fails #21204
Add the ability to stop/abort a workflow on velocity script actionlet #21252
[Push Publishing] : Single quote in content's title breaks JavaScript code in the portlet #21699
Sanitizing file name #21791

dotCMS 22.02

Available: Feb 9, 2022

dotCMS 22.02 is a fairly large release that consists of 89 fixes, improvements and new features. For more detail, the whole list of issues included in dotCMS 22.02 can be found on github.

New Features

  • Content Editors rejoice - the Content Pallet now allows for simple, click and drag content reuse.
  • GraphQL now supports dotAssets (in addition to normal FileAssets) on File and Image fields
  • Download a full sql dump and asset backup via api/Admin Screen (Postgres/Docker only).
  • See job progress when running Bulk Actions across large numbers of contents.
  • New Host Integrity Checker to ensure that the hostnames/id match across push publishing environments.
  • Updated Docker Image, removed legacy configuration process and removed “special” docker environmental variables that were used only in dotCMS docker, unifing them with the variables that the dotCMS binary expects.
  • Moving forward, environmental variables should be used to configure (almost) everything. If you need to configure something outside of what can be done via environmental variables, you should be prepared to either build a custom dotCMS docker image or mount in an override file.
  • GZIP enabled by default in tomcat and is configurable via environmental variables.
  • SMTP server now supports SMTPS and STARTTLS and should be configured via environmental variables.
  • HTTP Responses now include a header x-dot-server that identifies which server in a cluster is responding. This can be disabled if needed.
  • New velocity script actionlet can be used to abort an in-flight content workflow.

Changes/Improvements

  • Site selector type searches uses wildcards, which is very helpful when searching/switching sites in multi-tenanted environments.
  • Forms no longer require CSP “unsafe-eval” to be used.
  • “What's changed” diff takes place on the client side and no longer uses outdated XML java libraries.
  • Robustification - now the backend relies more on db than Elasticsearch. Previously, if the Elasticsearch index was down or broken, dotCMS could not render front end pages, navigation, templates or the site browser. Now these work. Github issues: #21284, #21283, #21385, #21360.
  • Changed to FILE_SYSTEM for metadata storage by default. This changes from the previous incorrect default of storing the metadata in the db and prevents runaway DB load when cold starting a dotcms cluster.
  • Fixed race condition when copying host.
  • Removed noisy log when using edit mode.
  • Removed unnecessary SAML logging.
  • Allow dotCMS docker image to be build using GID=0, helpful when building a dotCMS image for openshift.
  • Added “Bring Back” button to the new content compare screen.
  • Removed a number of old/unused dotmarketing-config.properties that caused confusion.

Breaking Changes

  • Installations using the dotCMS docker image will need to update their configurations and supply different environmental variables to configure dotCMS properly. Please see the “Docker Image Configuration Options” page on how to properly configure the dotCMS docker image.
  • Hazelcast config removed from docker image. If you need to configure hazelcast, you will need to specifiy it as a cache provider and mount in a custom hazelcast-config.xml.

dotCMS 5.3.8.9 LTS

Available: Jan 18, 2022

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

Fixes

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

Issue Github Link
[Static Publishing] : Problem with multi-language contents #21537

dotCMS 5.3.8.8 LTS

Available: Jan 13, 2022

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

Fixes

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

Issue Github Link
Revert bad commit #19842

dotCMS 5.3.8.7 LTS

Available: Jan 11, 2022

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

Fixes

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

Issue Github Link
Update log4j to 2.17 #21441
Content Export tool is not exporting relationships correctly #20746
Push publishing sometimes changes the order of contentlets in the multi-tree table on multilingual pages #21313
200 redirects to external links are not rendering properly #21198
Large Bundles make the viewing publishing queue slow #20971
Delete All Bundles does not really delete all bundles #20812
Contentlets with future publish date prevent it from being Push Published #20765
[Reindex] : Perform Site check before Folder check #20722
"Login As" Data Constraints #20721
NPE on tags via graphql if no tags present #20719
[Vanity URL] : Missing parameters in Vanity URL cause problems in API #20685
IndexPolicy do not respected on wf toolview #20649
Tika failing to init, hanging dotCMS startup #20640
Container displays Add button twice under specific situations #20623
Button for Navigation Reorder is not working correctly #20616
Class in rows are lost when you remove a row #20519
Error retrieving content references in multilingual setup #20494
Concurrency Issues with loadPermission #20464
Unable to load very large images #20446
[Content] : Many to One relationship not displaying in Content Search #20399
Large bundles can take too long for load balancers #19321

dotCMS 22.01

Available: Jan 10, 2022

New Features

  • Unlimited fields on content / content stored as JSON. Currently available in Postgres with plans on targeting MSSQL next.
  • New content version compare screen shows a field by field comparison of what's changed on any give content.
  • Widgets can render both markup and as json, allowing widgets to be used in headfull and headless implementations simultaneously.
  • New Redis Pub/Sub and Cache Provider. Uses the Lettuce library under the covers, allows a cluster wide 2nd level cache to improve cold startup performance on large sites. The new Redis implementation also allows the pub/sub cache invalidation mechanism to be used when primary datastore is not Postgres.
  • Default folders can now be set for image/file fields, rather than always having to browse from the site root, giving a better end user experience.

Changes/Improvements

  • Site “Host Name” is renamed “Site Key” and once set, users are discouraged from changing site keys. The “Site Key” should be treated and understood as immutable and should not be changed over the lifecycle of a site.
  • Site Key (hostnames) can only accept characters that are valid for server/DNS names.
  • ContentTypeAPI can now filter content type results by site/host.
  • SAML authentication now correctly stores the last ip for the authenticated user
  • $dotcontent.find("{id}") no longer uses elasticsearch to pull proper lang/version resulting in better performance and less log spamming from velocity.

Security Fixes

  • Updated Log4j2 to 2.17.1, added {nolookups} to log4j2.xml config file, start java with -Dlog4j2.formatMsgNoLookups=true github #21485, #21393. See
  • Prevent XMLTool from fetching remote entities github #21415
  • Remote Calls - XMLTool, JSONTool and VanityUrl Proxy calls are now blocked for localhost and private networks by default. This is best practices as per OWASP security standards. This behavior can be disabled using configuration properties. github #21415
  • TempFileAPI will only import by URL if user is an admin github #21400
  • User.userId is now immutable once initialized github #21392

Breaking Changes

  • UID/GID in our docker image has changed to 65001:65001. Previously, it was 1000000000:1000000000. In order to run the new dotCMS docker image, you will need to make sure that the user on your host has the proper uid/gid and that your shared assets folder that map into docker have the proper ownership. As an example:
    usermod -u 65001 dotcms
    groupmod -g 65001 dotcms
    chown -R dotcms.dotcms /assets/folder/root
    
  • In Postgres implementations, content is now stored as JSON. This means if there is custom code that is directly queuing the contentlet table in the db (tisk, tisk, as this is bad practice), these queries will no longer work.
  • Remote Calls - XML, JSONTool and VanityUrl Proxy calls are blocked for localhost and private networks by default. This is best practices as per OWASP security standards. If your implementation makes local calls using these tools, you can change/configure the network blacklist by setting a config variable.
  • Site.hostname field can only accept characters that are valid for server/DNS names (via the ui).

More Information

For more detail on what is included in 22.01 release, please see the tagged github issues


dotCMS 5.3.8.6.2 LTS

Available: Dec 13, 2021

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

Fixes

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

Issue Conditions Github Link
Log4j2 zero day exploit https://nvd.nist.gov/vuln/detail/CVE-2021-44228. #21393
Make userId immutable. Once a user object has been created/inited, you should not be able to edit the userId.. #21392
Upgrade log4j version to permit JsonLayout custom key-value pairs. Allows key-value pairs in Json for k8s and docker. #20792

dotCMS 21.06.4 LTS

Available: Dec 13, 2021

dotCMS 21.06.4 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.4

  • 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)
  • Additional GraphQL logging was added. (#20764)

Fixes

The 21.06.4 release includes fixes for the following reported issues.
For a list of issues addressed in dotCMS 21.06.4, 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.11

Available: Nov 15, 2021

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

Improvements in dotCMS 21.11

  • Added multiple improvements to the import action in the Apps module. (#19747)
  • Added improved messaging about how to add Apps. (#18707)
  • Added a static cache to GraphQL to help with heavy queries.(#19981)
  • Added the ability to change the default language in the UI.(#20887)
  • Added the ability to generate secure passwords for users. (#20915)
  • Combined Default Content View was added in Content Search. It includes the thumbnail and details. (#21014)
  • Improvements were added to improve the handling of SVG images.(#21051)
  • We have removed the repackaged xbill DNS jar that contained classes under com.dotcms.repackage.org.xbill.DNS.*. Customers should instead reference these classes here: org.xbill.DNS.*.(#20940)

Fixes

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

Issue Conditions Github Link
A search in Content Search was sometimes returning zero results . Only occurred when a date from advanced search was used. #20667
Instances created with a different default language then the current default language sometime broke after an upgrade. Only occured if upgrading to a version past 20.10. #20786
Some bundles were taking a long time to load on the publishing queue screen. Issue occurred when pushing on bundling a bundle with over 10,000 pieces of content. #20971
In page edit mode contents sometimes moved around.. Issue only occurred when preparing to drag and drop contents. #21047
Content were not always being updated. Only occurred when a search was filtered then the user switched to the other view type (card or list). #21153
An error sometimes occured when trying to drag and drop content in edit mode. Only occurred when clicking on the middle of the content to drag instead of the draggable frame. #21180
Error would sometimes occur when trying to see the bundles in the history tab. Only occurred when bundles were just uploaded to the server. #21202
Bundle status sometimes failed to update. Only occurred after retrying the push of a bundle. #21124
Not all map properties were returned in some instances. Only occurred after content was saved. #20948

dotCMS 21.10

Available: Oct 11, 2021

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

Improvements in dotCMS 21.10

  • Improved how we save timezone information.(#20899)
  • Improved logging for rules. (#20880)
  • Improved Reindex log messages. (#20821)
  • New dotCMS endpoint /v1/system-status/alive to check if the server is up.(#20827)
  • Batik dependency was removed.(#20847)
  • dotCMS now releases licenses on shutdown. (#20856)
  • Type selector will no longer show when searching in a portlet with only one type. Like the image portlet. (#20861)
  • Replaced Moment.js library with the date-fns library.(#19784)
  • Warning log messages were updated when the user is lacking permissions to view a catagory associated with the contentlet.(#20801)
  • Improved error message for when an invalid shard is entered in the creation of a site search index. (#17569)

Fixes

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

Issue Conditions Github Link
Hooks were sometimes prevented from being registered when certain changes where made to the MANIFEST.MF. Only occurred when the plugin version was modified in MANIFEST.MF. #17959
Users sometimes recieved a Java Script error when trying to use certain buttons in the maintenance portlet. Occurred when the user tried to use the Update System Logging and Refresh buttons on the log files tab. #18908
The enter key was not also recognized as submit. Issue occurred when creating a bundle and enter was pressed after typing a bundle name. #19042
It was sometimes possible to add empty tags in certain areas causing errors. Issue only occurred in the rules portlet. #19909
Many to one relationships where not always displayed correctly. Only occurred when a user seached for many to one relationships in the content search. #20399
Some users were able to start ES queries that they did not have permission to run causing errors. Only occurred in multitenant ES environments. #20596
A contentlet was sometimes prevented from being published . Only occurred when the contentlet had a future publish date. #20765
Some emails were sometimes seen as spam by mail services. Only occurred for emails sent from workflow actions which were sent from hard-coded email addresses with non-existent domains. #20777
A piece of content was sometimes in the wrong workflow set. Only occurred on the reciever side after a push publish. #20718
The Host select box was not displaying on the theme paginator in certain circumstances.. Only occurred when there were multiple cloned sites. #20781
The page API was sometimes returning the wrong publish date in its JSON. Only occurred when the page contained a contentlet with the publish date field. #20791
Icons in grid view were not showing properly in the upload fields modal in certain circumstances. Only occurred when trying to attach an image from the WYSIWYG fields or the task list. #20817
When a Site/Folder field was removed from a content type all the contents sometimes moved to System_Host Only occurred when the content type lived somewhere other then System Host. #20850
In certain areas timezone searchs were only matching against the first characters. Only occurred in the company portlet. #20888
Retry bundle wasn't always working. Occurred on the status popup and the listing screen. #20974, #20878
Time machine did not always work. The issue only occurred after creating a new snapshot. #21097
Multiple issues occurred with Oracle. Including inability to start dotCMS with an Oracle DB, and issues occurred with Oracle licenses as well. #21128, #21119

dotCMS 5.3.8.6.1 LTS

Available: Oct 7, 2021

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

Improvements in dotCMS 5.3.8.6.1

  • Improved error message for deleting a container used by a template. (#20277)
  • Added the option to choose what fields are shown in a relationship field's overview. (#19215)
  • Added automatic deletion of old inactive Elastic Search indices to prevent performance slowdowns. (#19931)
  • Added header identifying what vanity URL directed the user to the page to help simplify debugging. (#20416)
  • Improved how external caches and the dotCMS internal cache interact. (#20412)
  • Improved error messages for WorkflowAPIImpl. (#20636)
  • Edit Mode Anywhere now always expects UTF8. (#20629)
  • Improve concurrency issues.(#20507)
  • dotCMS is now fully ARM supported. (#19192)
  • The cache is now flushed when the push publishing filter files are changed. (#19152)
  • Additional GraphQL logging was added. (#20764)
  • Warning log messages were updated when the user is lacking permissions to view a catagory associated with the contentlet.(#20801)
  • The ability to customize TinyMCE and set it systemwide is now part of dotCMS. (#19651)

Fixes

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

Issue Conditions Github Link
Workflow modal failed to open in certain circumstances. Only occured when selecting available workflow actions for all content in the content search for the content type, date, with more than 40 results. #19677
Subfolders in the site browser were not in alphabetical order in certain circumstances. Only occured when a folder's name was changed. #20104
An infinite loop sometimes happened for specific vanity URLs. Only occured when the vanity url had a 301/302 HTTP redirect from a URL with a trailing slash to the same url with no trailing slash. #20280
Unexpected behavior was happening when statically pushing some file assets. Only occured when the file asset name had spaces in it. #20295
Workflow could not be copied in certain circumstances. Only occurred when the Notify Assigned action was included in the workflow. #20501
URL field values were not included in pages in certain situations. The URL field values were not included when the page was exported from Content->Search. #20405
Error sometimes occured when deleting or moving a field in a Content Type. Only occured for some fields when they were related to another field. #20342
Copy workflow button sometimes resulted in incorrect next steps. Only occurred sporadically. #18111
An error would sometimes occur for sites with lots of cookies. Only occured when either of the following properties were set as shown below: COOKIES_HTTP_ONLY=TRUE or COOKIES_SECURE_FLAG=always/https. #20334
User with frontend permissions was sometimes seeing blank pages in certain situations. Only occurred the user also had backend permissions. #20452
The page API was sometimes returning the wrong publish date in its JSON. Only occurred when the page contained a contentlet with the publish date field. #20791
Problems trying to login from a PC.. Only occured when MSSQL as the DB #20499
IPUtils was sometimes returning false incorrectly. Only occurred when a specific IP utilizing a was passed in. #20578
Settings were sometimes not respected when an image was inserted into the WYSIWYG. Only occurred when WYSIWYG_IMAGE_URL_PATTERN was set on the image. #20642
The User Resources endpoint wasn't parsing some parameters correctly. Occured when the parameters includeAnonymous and includeDefault parameters were not being respected. #20450
A Workflow Scheme was not always able to be imported. The issue only occured when the next assign or permission role did not exist. #20488
Elastic search was sometimes getting overwhelmed with index requests. Only occured in clustered environments when doing a full reindex, bulk repermissioning or unding the definition of a major content type. #20568
The "Site or Folder" field dropdown sporadically disappeared. Only occured for some content types in edit mode. #20270
dotCDN was not invalidating the correct information on prod ion certain situations. Issue occurred when push publishing data that had been invalidated on auth. #20690
Date was sometimes parsed incorrectly in certain situations. Issue occurred when a bundle was being created.. #20766
Users would sometimes see a multilingual site in the wrong language. Occurred when the site was static and the default language was selected. #20469
Hanginging on the front end was sometimes experienced. The error only occurred when a user was creating multiple independent SCSS files that were compiled separately using a build in compiler. #18301

dotCMS 21.09

Available: Sep 7, 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
Hanginging on the front end was sometimes experienced. The error only occurred when a user was creating multiple independent SCSS files that were compiled separately using a build in compiler. #18301

dotCMS 21.08

Available: Aug 4, 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 5, 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
    Elastic search was sometimes getting overwhelmed with index requests. Only occured in clustered environments when doing a full reindex, bulk repermissioning or unding the definition of a major content type. #20568

    dotCMS 21.05.1

    Available: Jun 8, 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.

    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

    On this page