Changelogs

Last Updated: Jun 17, 2024
documentation for the dotCMS Content Management System

Current dotCMS Releases

Below, you'll find dotCMS's Current releases. To instead find a Long-Term Supported (LTS) release, please use the tab above.

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
v24.08.27 Aug 28, 2024 Aug 28, 2025
v24.08.20 Aug 21, 2024 Aug 21, 2025
v24.08.05 Aug 6, 2024 Aug 6, 2025
v24.07.30 Jul 31, 2024 Jul 31, 2025
v24.07.19 Jul 22, 2024 Jul 22, 2025
v24.07.12 Jul 15, 2024 Jul 15, 2025
v24.07.05 Jul 9, 2024 Jul 9, 2025
v24.06.27 Jun 27, 2024 Jun 27, 2025
v24.06.26 Jun 26, 2024 Jun 26, 2025
v24.06.21 Jun 24, 2024 Jun 24, 2025
v24.06.19 Jun 20, 2024 Jun 20, 2025
v24.06.17 Jun 17, 2024 Jun 17, 2025
v24.06.06 Jun 7, 2024 Jun 7, 2025
v24.05.31 Jun 4, 2024 Jun 4, 2025
v24.05.20 May 21, 2024 May 21, 2025
v24.05.13 May 13, 2024 May 13, 2025
v24.04.24 Apr 24, 2024 Apr 24, 2025
v24.04.23 Apr 23, 2024 Apr 23, 2025
v24.04.16 Apr 17, 2024 Apr 17, 2025
v24.04.05 Apr 5, 2024 Apr 5, 2025

dotCMS 24.08.27

Available: Aug 28, 2024 Demo starter image: 20240807
Empty starter image: 20240719

dotCMS 24.08.27 has useful new documentary elements, new dotParse functionality, more control over AI workflow operations, and more.

This release also introduces two small but significant — and, of course, necessary — breaking changes. We break to build, not vice versa, but growing pains are inevitable. These we soothe with the balm of an assortment of bugfixes.

To break with one hand and mend with another: Is this not the destiny of all humanity?

Enhancements & Adjustments

  • The half of the Workflow API endpoints have been documented in the API Playground; second half soon to follow! [#29189]
  • API Playground documentation added for Authentication endpoints. [#29616]
  • Removed automatic Save and Publish operations from artificial intelligence actionlets; better to leave those decisions to the user. [#29387]
  • API endpoints now support invalid Java locales when performing operations on system languages. [#28682]
  • Enhanced the VTL parsing directive to take a TTL as a second argument; this will automatically treat the parsed data as if enclosed in a block cache. [#29144]

Interface

  • Fixed a styling issue causing an unsightly bar to the left of the main window of the admin panel on Firefox. [#29577]
  • Corrected the position of the user-account corner menu dropdown — home of the beloved Login As function. [#29534]
  • Adjusted the colors on the calendar selector in Experiments. [#29472]
  • Cache TTL field on page properties now specifies unit (seconds). [#23074]

Fixes

  • Repaired Copy URL button on UVE. [#29570]
  • Fixed issue that could sometimes cause content to be deleted from a page after editing page properties. [#29569]
  • Tag lengths now validate correctly in the content editor. [#29559]
  • Page tools on the UVE now function as expected in both traditional and headless paradigms. [#29206]
  • The Template dropdown now reflects custom templates in the correct fashion. [#29034]
  • Push publishing content no longer fails in the case where system-host content uses a tag on another host and attempts to push to a receiver that lacks this tag — rectifying what might be thought of as a lateral blind spot. [#29397]
  • Images no longer disappear from a page when a retrieved as related content in the same Page API call. [#29259]
  • Host lookups now cache their results even if no site is found. [#27366]

Development Improvements

  • Fixed Docker Compose example for push-publishing environments. [#25595]

Breaking Changes

  • Created a global log4j configuration in Tomcat. This may cause conflicts with existing custom logging behaviors; in the worst case can cause a server to fail to start. Using the default logging configuration is recommended when upgrading. [#23631]
  • Page API's returned image property now includes the entire image object, rather than just an identifier string. [#29259]

dotCMS 24.08.20

Available: Aug 21, 2024 Demo starter image: 20240807
Empty starter image: 20240719

dotCMS 24.08.20 boasts a lot. We keep telling it, “nobody likes a braggart,” but this headstrong scamp will regale you all day with its many deeds and talents. “Improved UVE functionality,” it says, “and dotAI, too!” And don't even get this one started on the dotCLI; fixes aplenty, I'll warrant, but need it be so forward about it?

The API Playground, you'll hear, is enjoying a documentarian push: the Content Type API endpoints are now fully documented within the interface, and rumor has it the Workflow API is close behind. Is there no end to to the immodesty?

And look at that, the dashing rogue has gone so far as to carve its doings into the wall below. See for yourself:

Enhancements & Adjustments

  • Universal Visual Editor refreshes the page, and provides visual feedback indicating such, after saving changes to a contentlet on the page. [#29426]
  • UVE now remembers custom queries used to render a page, which may differ from the standard Page API return. This enables a more consistent user experience. [#29263]
  • Added documentation to Content Type API endpoints in the API Playground. [#29037]
  • Implemented several enhancements to the dotAI code — behind-the-scenes stuff to improve reliability, better document errors, and smooth the debugging process. Also removed some unnecessary asynchronous functionality. [#29587] [#29381]
  • The Categories API categories/children endpoint now additionally returns a list of parent categories when showChildrenCount: true is included in the request. [#29315]
  • Refactored the Block Editor to use newer Angular syntax. [#29448]

Interface

  • Restored visibility of the Delete button for content types on the community edition. [#29473]
  • UVE workflow wizard dialog now appears in front of the content editor, instead of behind it. It won't do to have a wizard if they're just going to sulk in the background. [#28177]
  • Improved persona tag tag-length validation and truncation when adding personas to a page. [#26081]
  • Rules permission checkbox is now visible, as it really should have been the whole time. [#28814]

Fixes

  • Previous serialization updates caused a regression on a previous menu error; we've set that back in order. [#29524]
  • GraphQL now gracefully handles errors related to bad or corrupted data related to content types, complete with useful messaging. [#29289]
  • Added more informative GraphQL error messaging for unauthorized page requests. [#29270]
  • GraphQL no longer creates unnecessary duplications in its schema when performing collection queries. [#29269]
  • GraphQL queries now support pagination fields: limit, offset, total, hasNextPage, and hasPreviousPage. [#29117]
  • Universal Visual Editor is now able to edit pages generated by GraphQL. [#29045]
  • Fixed looping behavior in UVE Next.js example project caused by experiment environment variables. [#29235]
  • dotCLI now automatically creates a simple layout structure for fields within a content type, if none is present. [#29087]
  • Solved dotCLI issue that could alter the sort order when saving content type fields. [#29086]
  • Added a validation check to dotCLI, matching a similar one in the user interface, that limits the total number of columns in a content type to four. [#29084]
  • Removed unnecessary layout attribute from the content type descriptor in dotCLI. [#29083]
  • Fixed error preventing dotCLI's --watch option from working when paired with path specified inline. [#28593]
  • Pushing sites with a global push from within the sites folder no longer causes a dotCLI error. [#28473]
  • Templates now restore properly to previous versions. [#28417]
  • GraphQL schemata still generate correctly after arbitrary editing of a page asset. [#28114]
  • Recurrence and re-fix: Layout changes in the Template Designer will no longer alter content organization. And we mean it! [#27689]
  • Fixed content editor functionality in Community Edition. [#29578]
  • Restored operation to telemetry plugin, which had halted in a recent update. [#29222]
  • Starting a file asset name with certain character sequences will no longer cause it to be treated as an image via Image Processor confusion. [#29321]
  • Changing the path of a folder to a different case — upper or lower — no longer causes errors. [#29293]
  • Fixed a source of out-of-bounds error on the Site Search tool when a default index is deleted. [#28779]

Dependencies, Components, Etc.

  • Added @ngrx/signalStore to perform state-management duties in the Universal Visual Editor. [#28947]

dotCMS 24.08.05

Available: Aug 6, 2024 Demo starter image: 20240729
Empty starter image: 20240719

Compact but strong, dotCMS 24.08.05 includes a few interface fixes, an important plugin-related patch, and a new workflow distinction to render some actionlets as “batch only.” For an update roughly the size of a bon-bon, it's rather filling.

Enhancements & Adjustments

  • Added “batch-only” quality to some actionlets; when a workflow action contains such a sub-action, it will not allow the “Show on Edit” box to be checked. Instead, the task will only display on content search window, usable by the Available Workflow Actions button or the right-click context menu. [#29207]

Interface

  • The Content Search tool no longer imprisons its own name in an unsightly box of scrollbars. Yes, yes — the title is out. [#29399]
  • Addressed some minor misalignments in the “Read More” section of the Page Editor's SEO cards within the toolbar. [#26497]
  • Also realigned the “Welcome” screen's header. [#26100]
  • Corrected dimensions Preview Device selector from “Height x Width” to “Width x Height. [#28517]

Fixes

  • Corrected the URL supplied when exporting a file asset. [#29209]
  • “Show Preview” button in the Page Editor now respects and reflects the selected language. [#28620]
  • Universal Visual Editor now correctly permits inline editing when using Angular in a cross-domain context. [#29311]
  • Plugins that include their own tool window in the back end are now once again able to deploy correctly. [#29276]

dotCMS 24.07.30

Available: Jul 31, 2024 Demo starter image: 20240729
Empty starter image: 20240719

Piloting a barge out of the cave of Hypnos, dotCMS 24.07.30, offers succor and rest to the worried and weary. This boatload of fixes has goods aplenty to shush and shoo the bads; whether touching up the UI or mending function, we aim for our current-edition users to rest easy.

Stability and clean operation isn't just for the LTS crowd, after all.

Enhancements & Adjustments

  • Added onReload back to DotcmsLayout after its previous removal; it is still considered deprecated. [#29338]
  • Added new configuration property: Though defaulting to true, AUTOPOPULATE_FOLDER_NAME_FIELD can be set to false through environment variable or the system table. This will prevent folders from automatically copying title field to the name field when setting the former. [#20424]

Interface

  • Improved styling and display of thumbnails in the content search screen. [#29098]
  • Separated the pencil icon from the context menu's “Edit” label after the latter nearly put its eye out. [#27599]
  • Page editor's SEO tools now signal truncated text with good old-fashioned ellipses — almost as if it's hiding something… [#26531]
  • Improved persona tag truncation when adding personas to a page; this prevents long tag text from breaking out of containing elements. [#26081]
  • Restored proper colors to buttons on binary fields. [#29316]
  • Artificial intelligence image generation dialogs now scale to a better proportion on larger and/or taller screens. [#29301]
    • Also fixed a small “jump” as the AI image generator dialog settles into frame. [#29173]

Fixes

  • Fixed bug preventing VTL files from being saved on edit. [#29309]
  • The UVE can now display more than ten personas in its dropdown. [#29161]
  • The GraphQL playground now loads schemas properly. [#29109]
  • The integrity checker has been brought up to speed with more recent database changes, and updates content columns in more robust fashion; this prevents a case where it could inadvertently break the ability to retrieve content JSON data by identifier. [#29059]
  • dotCLI no longer improperly merges artifacts and thereby becomes corrupted; we decided this behavior works better as a Tolkien plot than a build result. [#28917]
  • Binary field's info dialog now populates correctly. [#29283]
  • Binary fields now thoroughly sanitize filenames to avoid unsightly character-encoding outcomes. [#28462]
  • Adjusted the method that copies a contentlet for editing on a single page to ensure it does not throw errors on encountering legacy relationships. [#29234]
  • Resolved issue whereby moving containers within a layout sometimes would not cause content to be appropriately repositioned. [#29158]
  • Added language keys to ensure the “Add to Bundle” dialog displays properly in supported languages. [#29064]
  • Improved error handling on dotAI; invalid responses on embeddings operations now log and express the errors in expected fashion. [#28990]
  • Fixed link to content type in the contentlet editor when accessed within the page editor. [#27902]
  • Moving containers inside the layout of an experiment variant can no longer cause a change in the default version of the page. [#28655]
  • Importing file assets via CSV no longer throws undue errors proclaiming a file asset is required; the info is right there, after all. [#29079]
  • Enabled better logging for Page API endpoints using the getPageByPath method. [#26546]

Dependencies, Components, Etc.

  • Added uber jar to assist in dependency management during dotCLI build processes. [#28916]

dotCMS 24.07.19

Available: Jul 22, 2024 Demo starter image: 20240719
Empty starter image: 20240719

dotCMS 24.07.19 offers some new and improved REST API functionality, the ability to generate images with dotAI directly from binary fields, better syntax highlighting, and the usual assortment of fixes.

It also contains our first breaking change in a while. We had quite a streak going — more than a year without! But alas, every once in a while they're just so called for.

Enhancements & Adjustments

  • Updated the /v1/categories/children REST API endpoint to allow a search of the entire tree, starting from the specified inode. [#28896]
  • Added v1/categories/hierarchy endpoint that takes a list of category keys and returns for each a list of parent categories. [#28894]
  • Added the ability to use dotAI to generate images directly from binary fields. [#27458]

Interface

  • VTL files now receive HTML syntax highlighting in the file editor. [#28084]

Fixes

  • UVE Angular headless implementation authorizes across all modes properly. [#28949]
  • The Workflow API no longer throws errors when operating on content that contains a Key/Value field. [#28930]

    Note: This originally appeared in 24.07.05, but was found to require more work.

  • Fixed bug causing Kubernetes probe methods, under some conditions, to return erroneous 503 codes. [#28163]
  • Changed default property to ensure upgrade procedures halt when any upgrade task fails. [#29240]
  • Images uploaded in a non-default language now inherit permissions properly. [#28366]

Dependencies, Components, Etc.

  • dotCLI now uses the highest available version of Quarkus capable of supporting both Java 11 and Java 21. [#28744]

Development Improvements

  • Re-added procedure for deploying dotCMS instance using a custom database, such as from a database dump. [#28678]

Breaking Changes

  • The poorly named access_token cookie has been renamed rme, as its only purpose is to establish a “remember me” login flow. rme cannot be used as a Bearer token in the header, and concerns itself exclusively with full login procedures that update the user's “last login” date. [#28747]

dotCMS 24.07.12

Available: Jul 15, 2024 Demo starter image: 20240709
Empty starter image: 20240531

dotCMS 24.07.12 is a handy soul, bearing useful fixes for the command-line interface and more. That clicking sound you hear is another tumbler falling into place, as its deft hands move one step closer to unlocking the Java 21 transition…

Sorry about those gratuitous ellipses, by the way; we had to find somewhere to store them after yanking them out of the Publishing Queue.

Fixes

  • dotCLI no longer truncates error messages. [#29072]
  • dotCLI push commands no longer throw errors when using relative workspace paths. [#28847]
  • dotCLI version is included with headers to allow compatibility validation. [#28594]
  • Universal Visual Editor's Page API responses no longer include the additional layer of a containing entity property. [#28962]
  • Fixed null pointer error when copying sites. [#28339]
  • Select All checkbox now works properly in the Tags tool for Firefox users. [#25758]
  • GraphQL page queries no longer throw errors when fetching the titleImage field that points to a dotAsset. [#28706]

    Note: This item originally appeared under 24.07.05, but required further QA work.

  • Content search screen now automatically updates when AI content generation completes via workflow. [#28168]
  • Child permissions within categories now load properly. [#28838]
  • Removed ellipses from the end of bundle identifiers in the publishing queue; the identifiers weren't even being truncated. [#28509]
  • Added a search field to the publishing queue to allow filtering for whole or partial bundle identifiers. [#28508]

Security

  • Patched one medium security issue.

Dependencies, Components, Etc.

  • Updated CLI native build options in preparation for Java 21 update. [#29110]

Development Improvements

  • Fixed some Postman tests previously set to “ignore” for erroneous results. [#26676]

dotCMS 24.07.05

Available: Jul 9, 2024 Demo starter image: 20240611
Empty starter image: 20240531

It's the midseason harvest, and dotCMS 24.07.05 is ripe and bountiful — rich in features and lean on bugs.

This crop goes with just about everything; a dev with the wherewithal could render the same page across two, even ten environments, if'n they wanted. And to haul it all to market, dotCLI is growing into a real beast of burden under that shell; give it an instruction, and it'll keep hauling in the background. Heck, you might spy one out yonder, plowin' RESTful fields so fertile, you can toss a UUID at the ground and watch a workflow sprout.

You say you ain't never seen a workflow sprout? Friend, that's a shame we aim to remedy!

Enhancements & Adjustments

  • The Universal Visual Editor config now accommodates a allowedDevURLs parameter, which contains an array of URLs. These URLs will be allowed for use with the URL query parameter clientHost, which permits rendering of the same page content across different headless environments. [#28858]
  • Added --watch [n] option to all dotCLI push commands, whether global or specific to a subcommand. This option allows dotCLI to passively scan every n seconds for changes in the specified workspace, and push them automatically when detected. [#28593]
  • When saving content types through dotCLI, it is now easier to add workflows; just include a workflows property that contains an array of either workflow identifiers or names, and the system will replace the array of strings with an array of fully populated workflow objects. [#28265]
  • Updating content types through dotCLI does not require identifiers; a variable name will suffice. [#28264]
  • A Host column now appears in the References tab of the content editor, to better track content used on multiple hosts. [#28365]
  • New REST API endpoints have been added allowing the creation of push publishing environments. [#28578]

Interface

  • When previewing social media cards on traditional pages in the UVE, the status bar no longer cuts off early on the right-hand side. [#28959]
  • The button to add a new device to the editor's Preview Devices now uses the “edit” pencil icon. [#28455]
  • Updated checkmarks in category dialog dropdown menu to be visually consistent with current designs. [#29020]

Fixes

  • In projects, DOTCMS_HOST URLs now support optional trailing / characters. [#28932]
  • Direction parameter in dotCLI sorting commands now accepts case-insensitive directions — ASC or asc, DESC or desc. [#28143]
  • Fixed error preventing the use of the dotCMS library as a plugin dependency. [#25836]
  • Binary fields remain properly visible when creating new content. [#29127]
  • Fields converted from WYSIWYG to Block Editor now render correctly; procedures expecting a JSONfly no longer prematurely open the cocoon before the markupillar is ready to emerge. [#28943]
  • Suppressed a log error down to a warning when a user successfully signs in but lacks access to the default host. [#27069]
  • Newly created file assets will respect the language selected on creation, rather than shifting to the default language. [#28489]

Development Improvements

  • Split the default Postman collection into separate similarly portioned collections, to cut down on testing time. [#28423]

dotCMS 24.06.27

Available: Jun 27, 2024 Demo starter image: 20240611
Empty starter image: 20240531

dotCMS 24.06.27 is a tiny pill that contains several essential nutrients. In the future, perhaps all meals will be taken in this form; for now, though, think of this as a sort of vitamin supplement.

Fixes

  • UVE no longer crashes on an attempt to edit a contentlet outside of a container element. [#28928]
  • Some dotCLI resources used at runtime were being deemed unnecessary by the compiling process, which would lead to errors in execution; these resources have been made explicitly necessary to build operations. [#28915]
  • Content API now hits a cache instead of the database when determining whether a UUID passed is an identifier or an inode. [#28897]

dotCMS 24.06.26

Available: Jun 26, 2024 Demo starter image: 20240611
Empty starter image: 20240531

Trumpets announce dotCMS 24.06.26, and a herald reads the decree: The kingdom recognizes the headless adventurers who thanklessly quest across the frontiers, wielding the esoteric arts inherited from the whispered land of OSGi. To these brave heroes, we offer succor, solace, and REST — that is, a whole new slew of REST API endpoints to administer plugins!

Gnomish caravans bring other goods: a variety of useful and important fixes, updated SDK examples, and more. What dragon would dare stand against your party, now?

(Roll for initiative!)

Enhancements & Adjustments

  • Next.js and Angular library examples now include out-of-the-box support for custom 404 pages. [#28817]
  • Improved error handling on the JavaScript SDK's client libary. [#28816]
  • Expanded OSGi plugin REST API resources, to take over for previous OSGIAjax procedures; a full suite of plugin behaviors (deploying, undeploying, and more) is available via api/v1/osgi endpoints. [#27874]

Fixes

  • UVE controls show properly when switching between preview and editor views. [#28960]
  • Fetching of language identifiers now properly refers to cache, rather than calling the database every time. [#28890]
  • Embedded contentlets in Block Editor fields are now stored by reference rather than by replicating the entire contentlet, and further limit relationship depth to 2 to prevent circularities. [#28659]
  • API responses now return expected data for fields labeled description. [#28785]
  • OSGi plugin fragments are discarded after processing, and system messaging now better reflects their addition to the exported packages list. [#26518]

Dependencies, Components, Etc.

  • Redis implementation now supports ACL authentication via usernames and passwords. [#28863]

Development Improvements


dotCMS 24.06.21

Available: Jun 24, 2024 Demo starter image: 20240611
Empty starter image: 20240531

dotCMS 24.06.21 hauls, in the foreground, a couple of high-priority fixes and a dependency update. In the background, many other, less obvious changes have also occurred — steady construction toward future features.

Fixes

  • Unified API responses for binaries to prevent type errors when fetching related content. [#28857]
  • Fixed bug causing pages not to save template selections correctly when editing via the contentlet editor. [#28846]
  • Fixed the EmbeddingContentListener, which means pushing or removing a piece of content will appropriately update embedding indexes in both sending and receiving servers. [#28770]

Dependencies, Components, Etc.

  • Updated GraphQL to 17.5. [#28420]

dotCMS 24.06.19

Available: Jun 20, 2024 Demo starter image: 20240611
Empty starter image: 20240531

dotCMS 24.06.19 mostly hauls up a slew of fixes — some directly relating to the release two days prior, all useful. Use them in good health!

Enhancements & Adjustments

Fixes

  • The Block Editor's bubble menu now behaves correctly. [#28839]
  • The JavaScript SDK's getCollection method now properly returns default values for live and languageId properties. [#28830]
  • Fixed bug causing default-language fall-throughs to fail. [#28769]
  • When pushing a page that does not exist in the default language, the system will now properly evaluate its template. [#28760]

    Note: This issue formerly appeared in the release notes for dotCMS 24.06.17, but was revisited immediately thereafter.

  • PATCH endpoint of /workflow/actions/fire API no longer throws a null pointer error when a content map is not included. [#28580]
  • dotCLI no longer requires a page identifier for a url-mapped detail page in content type descriptor file; a path will suffice. [#28262]

    Note: This issue formerly appeared in the release notes for dotCMS 24.06.17, but was revisited immediately thereafter.

  • Fixed regular expression governing password validation to behave more consistently with special characters at different points in the string, etc. [#23292]
  • Universal Visual Editor's “Add Form” option is now hidden for non-licensed users. [#28900]

dotCMS 24.06.17

Available: Jun 17, 2024 Demo starter image: 20240611
Empty starter image: 20230525

dotCMS 24.06.17 comes equipped with some hustle, some bustle, and no gristle. New embedded-contentlet editing through the Block Editor's trestle, growing the SDK's castle, more bugs defeated in a wrestle, et al. It's enough to make one whistle!

Enhancements & Adjustments

Fixes

  • Updated update task (a second-order update!) to fix the way it addresses the month of March with regard to Daylight Savings Time. [#28695]
  • Removed ability to alter sort order from the Site Browser; changes to menu order require changes to the Sort Order field. [#27820]
  • Push Publishing no longer has a 10,000-item limit. [#23131]

Development Improvements

  • QA using new test case management system. [#28791]
  • Added Postman tests for generative AI endpoints. [#28719]
  • We added some Slack notifications to the dotCLI release workflow. This one's just for us, really. Still, now you know it; unknowing it will be the work of time and diligent focus on everything in life but this extremely minor fact. [#28673]

dotCMS 24.06.06

Available: Jun 7, 2024 Demo starter image: 20240531
Empty starter image: 20240531

dotCMS 24.06.06 gazes down at 24.05.31. If the latter's show of force made an impression, the newcomer's eyes don't register it.

“'Fewer than ten business days,'” it intones.

Searing air casts a lone tumbleweed between the two, like a plea from the fates — a scraggly olive branch dipped in the Lethe, bent into inexorable flight. It bounces once, then fades from the world.

When next the challenger speaks, sight lines bend to converge or fall away in perfect tunnel vision; the winner has already been decided.

“…Try four.”

In this update, the dotAI Tool sits high in the saddle, no longer requiring any special setup; we've set a lookout over the gulch via improved security logging on Apps; the town padre, Page API, says a benediction over vanity URLs; and our saddlebags are packed with fixes.

Giddyup.

Enhancements & Adjustments

Interface

  • Adjusted card list styling; first row no longer appears larger than subsequent rows. [#28725]

Fixes

  • Copy URL button in page editor now copies URL to clipboard as expected. [#28627]
  • Reverted page editor behavior: making layout changes from a page will always result in a custom page layout, and will never adjust a shared template — even if that page is the sole user of that template. [#28758]
  • Updated MultiTreeCache to exhibit cluster-aware behavior for experiment variants. [#28588]
  • System now properly evaluates and includes templates when push-publishing a page that does not exist in the system default language. [#28760]
  • Fixed importation of page assets via export file. [#28306]
  • Content types now properly display in the content search when the system property is true. [#28284]

Development Improvements

  • WireMock server added to supplement Postman tests. [#28739]

dotCMS 24.05.31

Available: Jun 4, 2024 Demo starter image: 20240531
Empty starter image: 20240531

dotCMS 24.05.31 is a modest release, as they go, comprising a handful of changes made over the span of fewer than ten business days. Still, there's more under the surface — chunks of work put toward other, larger ends still under construction. So this release is something of a codeberg. It's been a while since any kind of berg has made a lasting impression. I'll come right out and say it: Bergs are due a moment.

This one folds the asynchronous email actionlet into the core; allows automatic Time Machine backup pruning; and adds endpoints both of the immediate variety — such as the user updater mentioned below — and in support of forthcoming features, such as a localization revamp.

Enhancements & Adjustments

  • Updating a Content Type via the CLI can proceed either via Content Type id or variable name. [#28263]
  • The workflow actionlet to send an email asynchronously, formerly available as a plugin, has become a core functionality. [#28360]
  • Added PUT api/v1/users/{id} endpoint for updating users via REST API. [#27794]
  • Added job to prune old Time Machine backups; the PRUNE_TIMEMACHINE_OLDER_THAN_DAYS property has a default value of 90 (days), but can be manually configured. [#22033]

Fixes

  • Fixed checks to prevent already-known language codes from being created; these checks now properly reference language codes instead of country codes. [#28640]
  • Fixed “flickering” visual effect due to redirects on experiment variants. [#28291]
  • Updated dotZapier integration plugin to address compilation error. [#28589]

Security

  • Patched one medium security issue.

dotCMS 24.05.20

Available: May 21, 2024 Demo starter image: 20240213
Empty starter image: 20240201

dotCMS 24.05.20 comes with a wealth of changes deep under the hood, many of which concern dependencies and the evolution of our own developmental workflows and automations; others pertain to larger efforts still in development. But that doesn't mean we've forgotten to include some goodies for you, the user!

We've added a new query-builder syntax intended for use with our JavaScript SDK, an important part of the forthcoming implementation of the Content API in the SDK's client library. We're also providing the usual assortment of fixes, including a pretty important one that makes the $ai viewtool work. This is key because, as Aristotle would no doubt observe, “working correctly” is an important quality determining the goodness of a tool in securing its telos as the object of human will — which is elevated in turn.

And, as it happens, we do seek to elevate this human project.

Enhancements & Adjustments

  • Added new REST endpoint to access language variables stored as content; this is intended to support forthcoming localization changes. [#27979]
  • Added query-builder syntax to allow JavaScript SDK users to build Content API queries. Wearing these gilded gloves, one need never make skin contact with the Lucene query syntax. [#28537]

Interface

  • Implemented tertiary, icon-only button style into graphical system. [#28535]

Fixes

  • Resolved several JavaScript-based dependency vulnerabilities:
    • Addressed JSON5 prototype pollution via parse method. [#28442]
    • Resolved unauthenticated denial of service via the octokit/webhooks library. [#28440]
    • Path traversal through webpack-dev-middleware? We think not! [#28437]
  • The venerable # character is now decoded correctly when called upon in rules and vanity URLs. [#28089]
  • Workflow selections are now mandatory when performing the import content job, to avoid system confusion when importing content that typically uses a custom workflow. [#28171]
  • Changed the message that appears when exceeding a 100-character length on user name or email fields; dotCMS now tells you, in plain language, that a length has been exceeded, rather than pitching a SQL-flavored tantrum and evoking secondhand embarrassment in you, the one witnessing the spectacle. [#27725]

    Note: The above bullet originally appeared on 24.05.13's release notes, but was in fact delayed to this release for QA considerations.

  • Squashed bug bedeviling the $ai viewtool's general functionality; the tool now works as intended. [#28571]

Dependencies, Components, Etc.

  • Updating Junit and Mockito to address Java 21's restrictions on internal APIs. Mockito also obviates the need for Powermock; fare thee well, Powermock. [#27995]
  • Upgrading Apache Commons Compress to 1.26.0. [#28445]
  • Upgrading org.apache.xmlgraphics:batik-transcoder from 1.16 to 1.17. [#25873]

Development Improvements.

  • The old vulnerability-scan GitHub workflow, long disabled, has been removed from our codebase. [#28609]
  • continue-on-error property added to workflow to ensure the integration processes complete even when encountering a failure, while Artifactory changes are underway. [#28535]
  • Built a generic artifact deployment GitHub action in support of CLI release process. [#28226]
  • New CLI jars are now generated automatically on merges. [#27286]
  • Integration tests added for AI viewtool. [#27959]

dotCMS 24.05.13

Available: May 13, 2024 Demo starter image: 20240213
Empty starter image: 20240201

dotCMS 24.05.13 arrives on scene, the latest standard bearer of all that is new and improved. In the course of events, and the relentless march of time, the former will cease to be true; however, it will always be the case that 24.05.13 is improved over its predecessors.

Improved how? Our command-line interface grows mightier, for one thing. We've also got under-the-hood work from plugin endpoints to Java class refactorings; useful fixes, ever the crowd pleaser; and quite a lot more not even listed here — loads of work on features soon to see the light of day.

So, as the newness grows already old, pause to appreciate this moment — it passes, as do all moments, and surely won't be back. But when you're getting better with every new release, that's not a bad thing at all.

Enhancements & Adjustments

  • When pushing or pulling hosts via dotCLI, site variables can now be included. [#28059]
  • The CLI generates less log spam. [#28031]
  • dotCLI log file has been scooted into the to .dotcms folder. [#27809]
  • dotCLI no longer depends upon dot-service.yml; the addition of a --dotcms-url option allows its entire configuration to be encapsulated in commands, for more flexibility in one-off or programmatic use cases. [#27799]
  • Updated Plugins tool with new OSGi endpoints. [#28320]
  • Refactored OpenAI-using classes (such as in dotAI) to allow dependency injection for easier testing. [#28209]
  • Added a job to prune old indexes. [#26069]

Interface

  • Implemented new designs for tables in the admin panel. [#27940]

Fixes

  • Apps configurations can now be properly imported from older versions. [#28427]
  • Removed several CollectionUtils methods that are already handled natively on Java 11. [#28192]
  • Introduced safeguards against system objects being push published. [#28173]
  • Removing content boxes from the Template Designer can no longer break pages. [#27646]
  • $dotcontent viewtool is now permissioned appropriately for the user when utilized in the Send email Workflow sub-action. [#28352]
  • Previous versions of templates can now be properly rendered. [#23366]
  • Flaky-tested and fixed unexpected RECEIVED_BUNDLE status in synchronous bundle-endpoint operations. [#28380]

Dependencies, Components, Etc.

  • Updated GraalVM to prevent errors on native-imge generation for the CLI. [#28391]
  • SnakeYAML update for dotCMS and dotCLI. [#24850] [#28325]
  • Adjustments to Babel and tschaub gh-pages implementations to avoid vulnerabilities. [#28441] [#28436]

Development Improvements.

  • Restricted approval of GitHub Workflows to a secretive tribunal of our wisest and most otherworldly shamans. [#28293]

dotCMS 24.04.24

Available: Apr 24, 2024 Demo starter image: 20240213
Empty starter image: 20240201

dotCMS 24.04.24 is a next-day quickie. It has a minor tweak behind the scenes, but otherwise just the one tangible shift:

Interface & UX

  • The Page Editor's “Open in New Tab” link now reads “Open Published Version” — clarifying that the user will view a live, rather than draft, version. [#28347]

dotCMS 24.04.23

Available: Apr 23, 2024 Demo starter image: 20240213
Empty starter image: 20240201

dotCMS 24.04.23 is back from the code mines, hauling a rich new vein of improvements. A new endpoint can provide content reports that can better inform deletion decisions, streamlining licensing and JSON both, and friendly modals give AI-generated content a tidy staging area.

And as for the rest, you know us: Stuff gets fixed.

Enhancements & Adjustments

  • Added /api/v1/contentReport endpoint, capable of providing a list of Content Types and any existing contentlets of each type that live under a given Site or folder entity. This is helpful when making structural decisions, such as the placement or deletion of those entities. [#27755]
  • Language JSON files used by dotCLI now only require dotCMSObjectType and isoCode properties; other pertinent data is generated on the fly. [#27448]
  • In line with changes in license distribution methods, we've removed the ability to copy and paste licenses into dotCMS from Settings -> Configuration -> Licensing; licenses are now applied exclusively via the Upload option. [#27891]

Interface & UX

  • AI Blocks in the Block Editor initially generate their content in a modal dialog, for added clarity and conceptual separation of generated content. The modal likewise includes previews of generated images. [#27633] [#27632]
    • A “Cancel” button has been added to AI content modals, because humanity ought to have veto power over our synthetic-brained scions for at least a little while longer. [#28172]

Fixes

  • “Open in New Tab” option in Page Editor now correctly displays the published version of of the page. [#28278]
  • Restored file hyperlinks to the Binary Field info modal. [#28115]
  • Updating a template that uses the same container in multiple boxes will no longer result in displaced content among pages using that template. [#27816]
  • Fixed “Download DB Dump” functionality under Settings -> Maintenance -> Tools. [#27537]
  • Deleting the parent page of an experiment no longer causes certain underlying Experiments API calls to fail. [#28238]
  • Fixed a conflict in the analytics infrastructure causing errors at startup. [#28305]
  • Binary field now correctly shows thumbnail previews of uploaded PDF files. [#28105]

dotCMS 24.04.16

Available: Apr 17, 2024 Demo starter image: 20240213
Empty starter image: 20240201

dotCMS 24.04.16 boasts new options for Apps configurations, a few fixes, and quite a few other changes that it simply won't do to discuss here, yet — mainly work on new features in development, still awaiting release. Rowdy ones, at that: Some already demand to be seen!

“If patience were easy,” we remind them, “it wouldn't be a virtue.” That buys us a short reprieve, always briefer than the last.

Enhancements & Adjustments

  • Apps configurations can now be overridden via environment variable, with options to show or hide altogether any values so overridden. This presents a clean, hierarchical method of App configuration in cloud or multitenant settings. [#25953]

Fixes

  • Resolved discrepancies in representations of limited permissions with the dotCMS CLI; dotCLI now throws the correct errors (i.e., the authorization sort) on file pull operations for limited users. [#27386]
  • dotAI tools now insert content into Block Editor interfaces in a more natural manner: as a set of separate blocks, as if pasting from another source, rather than a single, condensed block. [#28201]
  • When duplicating content with certain relationship types — one-to-one, many-to-one — the copy will be created without duplicating those relationships, to prevent cardinality violations. [#26283]

dotCMS 24.04.05

Available: Apr 5, 2024 Demo starter image: 20240213
Empty starter image: 20240201

As you may have noticed, dotCMS releases have had a faster cadence recently. While the typical release might not stretch into the mammoth manifests of yesteryear, there's still always something exciting in the works; dotCMS 24.04.05 is no exception.

Today, we're pleased to announce the official release of the dotCMS Command Line Interface, or dotCLI for short. This tool opens up new horizons for CI/CD operations and general automation of dotCMS instances or clusters. Everybody loves a good command line, and you can bet that we're already using this little wonder for our own sites.

Aside from that, we've begun the work of folding the dotAI Plugin into our main codebase, leaving the work of integration testing and activation. We also added new handholds to edit custom content tools, and bopped a solid bouquet of bugs — a little spate of spring cleaning.

Features

Enhancements & Adjustments

  • The dotAI Plugin code has been migrated into the dotCMS core, the first step toward turning it into a permanent core feature. [#27972]

    Important Note: If the dotAI Plugin was already deployed and running, some actions need to be performed both before and after upgrading:

    • Before upgrading to this version the plugin needs to be stopped and undeployed from the Plugins portlet.
    • After upgrading to this version the dotAI portlet needs to be added back via Roles and tools. There is a GitHub card to add the portlet automatically after the migration so this would not be needed in the future.
  • Added API methods to update and fetch custom content tools. [#27920]

Fixes

  • Pages with an active Experiment now also refer to the Site, and not just the path, when determining whether a redirect is necessary. [#27906]
  • Thumbnails now display correctly in the Block Editor's Contentlet blocks. [#28055]
  • Deleting a Site that contains Content Types and content items no longer silently fails, and now provides an extra prompt to warn of the deletion of such items. [#27862]
  • The Secrets Viewtool can now properly parse the inode from URLs. This is important to ensure that it can properly check code's last editor to ensure they have permission to call on the secret. [#27516]
  • Fixed error where, when push-publishing to two different environments — one static, one dynamic — the normally untracked entry for the static push would appear in the pushed assets table with a null endpoint. [#27928]
  • Fixed Google Maps feature when setting rules related to visitor location. [#27531]
  • Key/Value fields no longer perform HTML encodings on inappropriate characters (commas and colons) when returning HTML-encoded values. [#25903]

On this page

×

We Dig Feedback

Selected excerpt:

×