Previous ChangeLogs - Documentation topics on: change logs,old docs,older versions,old versions,release notes,.

This documentation is a static copy for this version. For current documentation, see: http://dotcms.com/docs/latest

Previous ChangeLogs

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

Version   Release Date
dotCMS 3.2.4     Aug 17, 2015
dotCMS 3.2.3     Jul 20, 2015
dotCMS 3.2.2     Jun 30, 2015
dotCMS 3.2.1     Jun 8, 2015
dotCMS 3.2     Apr 21, 2015
dotCMS 3.1     Mar 16, 2015
dotCMS 3.0.1     Dec 22, 2014
dotCMS 2.5.7     Dec 18, 2014
dotCMS 3.0     Nov 17, 2014
dotCMS 2.5.6     Jul 19, 2014
dotCMS 2.5.5     Jul 14, 2014
dotCMS 2.5.4     Mar 6, 2014
dotCMS 2.5.3     Feb 13, 2014
dotCMS 2.5.2     Dec 19, 2013
dotCMS 2.5.1     Oct 21, 2013
dotCMS 2.5     Sep 23, 2013
dotCMS 2.3.2     Jun 16, 2013
dotCMS autoupdater_3.0.1     May 14, 2013
dotCMS autoupdater_2.5     May 14, 2013
dotCMS 2.3.1     May 10, 2013

For information on more recent releases, please see the ChangeLogs documentation.

dotCMS 3.2.4

Available: Aug 17, 2015

Fixes

  • Added ability to add files without extensions via webdav
  • Improved 1.9 to 3.2.4 upgrade
  • Improved logging for the Migrate to Content functionality
  • Cut/Paste fixed on Legacy Pages
  • Added config to sleep during Reindex logic
  • Improved the performance for File Assets when getting their dimensions 

Issue Tracker


dotCMS 3.2.3

Available: Jul 20, 2015

Improvements

  • Improvements to Reindex Logic on Failures in ElasticSearch 

Issue Tracker


dotCMS 3.2.2

Available: Jun 30, 2015

Fixes

  • Fixed issues with What's Changed functionality in Edit Mode 
  • Fixed some issues with Publishing content in multiple languages 
  • Fixed some major performance issues with legacy pages meaning pages that are not content

Things to Know

Issue Tracker


dotCMS 3.2.1

Available: Jun 8, 2015

Improvements

  • Updated Spring OSGi example plugin from Spring 3 to Spring 4.
  • Made multiple performance improvements.
  • Sessions are no longer required and load balancer stickiness is not longer mandatory for front end site delivery in a cluster (the admin functionality and multilingual sites where languages can be toggled still require sessions).  By default, dotCMS still creates sessions for clickstream tracking.  You can turn off automatic session cookie creation by setting ENABLE_CLICKSTREAM_TRACKING to false in your dotmarketing-config.properties.

Fixes

  • Fixed the key value field losing data after rendering in the UI.
  • Fixed the DB pooling parameters. The context.xml shipped with 3.2 still used Tomcat 7 specific properties which no longer work with Tomcat 8, specifically the maxActive configuration option has been renamed to maxTotal and the maxWait configuration option has been renamed to maxWaitMillis.
  • Fixed issues with images in a multi-lingual site
  • Fixed static plugin compiling issues with Java 7 and 8
  • Fixed multiple issues with the Navtool Viewtool and Multiple Languages on Pages as Content

Things to Know

  • dotCMS will no longer be supporting or providing the autoupdater. dotCMS 3.2.1 will be the last release that can be updated to using it.  Moving forward, clients should follow the straightforward upgrade steps found here : http://dotcms.com/docs/latest/upgrade-dotcms
  • Everyone running stock dotCMS (meaning running in Tomcat not running as a WAR) and upgrading to 3.2.1 should copy the 3.2.1 context.xml to your Config plugin and replace your connection settings with the new, tomcat 8 specific settings. It has the updated Tomcat 8 datasource properties.
  • JbossRulesFilter has been commented out in the web.xml by default.

Issue Tracker


dotCMS 3.2

Available: Apr 21, 2015

Improvements

  • Ships with updated Tomcat 8.0.18
  • Java 8 now supported. You can still run Java 7 if needed
  • Added 3 new out of the box Actionlets for Custom Workflows (Email, Auto Set Value, and an Auto Push)

Fixes

  • Fixed the random sort on pull contents
  • Fixed some issues with Weblogic
  • Fixed 3.x issue where the history code fields in containers was not saved

Things to Know

  • If using the Autoupdater you will need to alter any plugins that reference Tomcat as the directory is different with the new Tomcat version. ie.. server.xml, ROOT.xml or context.xml

Issue Tracker


dotCMS 3.1

Available: Mar 16, 2015

New Features

  • HTML Pages are now Content
    • As content, HTML Pages enjoys all of the features of content.  i.e. workflow, versioning, multilingual support, pessimistic locking etc.
    • To support all the new functionality Edit Mode has been improved on the left side controls when editing an HTML Page as Content including Workflow Controls
  • Pages can now exist on the root of a host. This means that if you have a page on the root of your site you no longer need the Virtual Link to map your home page
  • Pages no longer require a file extension
  • Pages can have UTF-8 URIs.
  • Added a more secure Viewtool to query the dotCMS DB directly. The new tool is mapped to com.dotmarketing.viewtools.SQLResultsViewTool@12107146. The old method in the CMSMacro Viewtool has been deprecated.
  • All Enterprise versions have added the ability to pass Elasticsearch queries directly into dotCMS. This allows greater flexibility. The queries can be passed in via REST, directly to our APIs in Java, or from Velocity via a Viewtool
    • There is a REST example of this using Geolocalization on the new starter site
    • This opens the possibilities to using functionality like suggestion, facets, geolocalization etc…
    • There is a new portlet that can be used to test queries

Overview of Fixes/Improvements

  • Fixed front end issue where some special characters would use excess CPU cycles
  • A number of security improvements have been made regarding how dotCMS manages cookies
  • Timemachine will now copy dotAsset files
  • The Activity Logger is now logging more events on content modifications
  • Fixed an issue where the back end session would time out while logged in
  • The CSV Content importer now accepts more date formats
  • Updated to the latest ElasticSearch (v1.4.2).  This will necessitate a reindex on upgrade
  • Front end forms have much improved multilingual support
  • JGroups library was upgraded which should prevent a small potential memory leak when running a cluster
  • Many fixes to the Integrity Checker and Push Publishing infrastructure
  • Improved the SASS/LESS infrastructure.  There is still an issue with SASS on Windows which is still not working. https://github.com/dotCMS/core/issues/7236
  • Improved the REST Portlet infrastructure for those creating portlets in the backend
  • Fixed plugins broken from previous TinyMCE upgrade
  • LDAP and WebDAV work properly now
  • Date ranges are now supported from the Content Search Manager
  • Worked with partner to allow them to run with Azure MSSQL database though Azure is not an officially supported dotCMS stack component

Things to Know

  • Over 200 fixes have been made between 3.0 and 3.1
  • This is the last release that targets Java 7.  3.1 will NOT work in Java 8.
  • You can use the Autoupdater to update from 3.x to 3.1 but you cannot use it to update from any pre 3.0 release
  • Because of the ElasticSearch upgrade, it is recommended that you run a full index after you upgrade dotCMS
  • There is a new property in the dotmarketing-config.properties files named. CMS_INDEX_PAGE.  This setting controls what page is returned when the client requests a folder. (i.e. URL ends with “/”)  Its default setting in this release is “index” without extension.  If you are upgrading from a previous version, you should either change this to be “index.html” or you will need to change the name of the default file in every folder on every host.
  • There is now a property named DEFAULT_PAGE_TO_DEFAULT_LANGUAGE which defaults to true. Because pages can now exist in many languages it is possible to hit a Page URI in a language that doesn’t exist. By default the dotCMS will return the page in the default language but render the content in the appropriate language. This mimics the functionality of pages and multilingual support in all dotCMS versions prior to 3.1.  If you set this to false then the dotCMS will return a 404 if the page doesn’t exist in the visitor’s language.
  • ESAPI Filter is now turned off by default.

Issue Tracker


dotCMS 3.0.1

Available: Dec 22, 2014

Fixes

  • Fixed some typos in the backend
  • Updated some missing files in the WYSIWYG editor that was causing issues with both workflows and front end content submission
  • Addressed a leak from a possible closed connection while requesting a file
  • Updated the helloworld plugin for 3.0
  • Improved the logic when running a full reindex.  Helps with those who run a reindex that never finishes

Things to Know

  • 3.0 doesn't have support for the Autoupdater yet so users of 3.0 will have to manually update

Issue Tracker


dotCMS 2.5.7

Available: Dec 18, 2014

Improvements

Fixes

  • Number of fixes to the Integrity Checker and Push Publishing
  • Navtool cache fix prevents unnecessary DB queries
  • Reindex Process made more robust and fault tolerant.

Things to Note

  • If you have a plugin that configs TinyMCE, you will need to review the config to ensure that it is compatible with TinyMCE version 4.x
  • The security improvements noted above can be turned on or off (or set to https only) in the dotmarketing-config.properties file.

Issue Tracker


dotCMS 3.0

Available: Nov 17, 2014


New Features

SASS/LESS

  • Both SASS and LESS files will compile server side as you upload the source files.
  • The SASS/LESS files are cached server side so they only have to compile the first time they are hit.

Autoscale Clustering

  • Attaching 2 different dotCMS installs to the same DB and Assets will cause the 2 installs to cluster with zero config.

Network Configuration Tab

  • Network and Clustering config can now be done from the Configuration Manager in the Backend UI.

License Management

  • The License Management Tab in the UI is redone and improved.
  • In the new my.dotcms.com Support Portal you can get a License Pack which allows you to Autoscale.
  • Your ServerID and License Info is fully manageable in the License Manager.

XML Sitemap

  • The XML Sitemap plugin is now included.

Ace Text Editor

  • The Ace Editor is now used for all code textareas.

Multiple Type Containers

  • Code can now be added to a container for every structure. This allows a container to display content from multiple structures.

Indexing Code Upgraded

  • The index libraries have all been upgraded providing much improved indexing performance.

Simplified WAR Deployment

  • Getting a WAR file can now be obtained from the normal dotCMS download.
  • A shell and batch script to produce a WAR is included in the bin directory.

Added JSONP to the REST API

Enhanced dotCMS Logging

  • Many areas of the system such as Push Publishing have had been improved with better logging to help diagnose issues.
  • A notification framework has been implemented complete with APIs to allow system wide communication and notifications.
  • The User Activity Logger is much improved and logs many more dotCMS user actions.

All Libraries Repackaged

  • Third Party Jars now have unique packaging to avoid conflicts with plugins and app servers.

H2 DB Added for Testing and POCs

  • The dotCMS distribution can now be run without any config with the internal H2 DB.
  • H2DB is not intended for production use.

Overview of Fixes/Improvements

  • Over 100 Push Publishing Fixes and Improvements.
  • TinyMCE has been upgraded and should work in all modern browsers.
  • Site Search Highlighting has been fixed and improved.
  • Continued XSS Security Improvements.
  • CMIS code updated so that the latest workbench will connect and work.

Things to Know

  • Over 700 Bugs and Fixes have been made between 2.5.6 and 3.0
  • If you are an Enterprise Client you will need to get a new license from the my.dotcms.com portal.
  • If you checkout from source you will need to deploy to get the libraries to pull from our Gradle/Maven Repository
  • If upgrading and you have plugins please note that the folder structure of dotCMS has changed and all libraries have been repackaged.
  • Many macros have been deprecated. For a list of all deprecated macros, please search the dotCMS documentation.
  • dotCMS now requires JDK 7
  • To see a full list of the issues worked on, please see the dotCMS 3.0 issues on GitHub


dotCMS 2.5.6

Available: Jul 19, 2014

Fixes

  • Addressed issue with saving containers after upgrade to 2.5.5. This was the only thing addressed in 2.5.6


dotCMS 2.5.5

Available: Jul 14, 2014

Improvements

  • Integrity Checker & Conflict Resolver - This is a new feature in the Publishing Environments tab (system/configuration/publishing environments) that allows users to check for and resolve conflicts that that may exist between servers. Prior to this there were some conflicts which Push Publishing was unable to handle
  • Improved the Job Scheduler’s ability to handle errors and delete jobs which no longer exist
  • To help developers build workflows, ActionID is now displayed for reference on the Workflow screen
  • Significant improvement to the logging of errors while Push Publishing to help with troubleshooting
  • Improved performance and stability of the Reindex process
  • Improved issues with the Tag Manager when working in other languages
  • Improved support for Unicode characters with File Assets

Fixes

  • Fixed multiple bugs in the DB layer which caused breakdowns when saving especially during Push Publishing
  • Fixed issue when adding comments that would occasionally mess up the comments count
  • Fixed absolute URLs in vanity URLs when referencing a dotcms host
  • Fixed issue where limited user couldn’t create a page using layout templates
  • Fixed the help screen when logged in via HTTPS
  • Fixed issues with multi lingual content and Push Publishing where titles wouldn’t show
  • Fixed the reorder menu issue (impacted version 2.5.4 only)
  • Fixed ability to reassign workflow directly from the Edit Content Screen
  • Fixed Push Publishing issue when Pushing content that didn’t have a version in the default language
  • Fixed multiple issues when using the Site Search Highlighter on a cluster
  • Cleaned up duplicate references in the web.xml which prevented deploy on some app servers
  • Fixed issues related to the compare method in later versions of Java

Things to Note

  • The Navigation Cache would clear on startup but this doesn’t happen anymore
  • If you run the integrity checker your DB Config needs a user which can add/delete FKs on dotcms DB Tables

Changelog


dotCMS 2.5.4

Available: Mar 6, 2014

Fixes

  • Made forgotten password process more secure - now emails token for password reset.
  • Increased security algorithm for generation of passwords.
  • Fixed issue in Edit Mode which could resulting a 404 when clicking on a Menu Link.
  • By default you cannot redirect to an external referrer. To change this default behavior, set DISABLE_EXTERNAL_REFERERS=false in dotmarketing-config.properties file of your configuration plugin.
  • Increased security for comments functionality.
  • Increased security to prevent header injection.
  • Improved XSS prevention algorithms.
  • Fixed live site caching issue when updating files.
  • Fixed CSV import when importing to a host.
  • Increased security of AjaxFileUploadServlet.
  • Improved security for system user.
  • Locked down multiple security issues.
  • Turned off autocompletion of password fields.

Changelog


dotCMS 2.5.3

Available: Feb 13, 2014

Fixes

  • Fixed multiple IE issues in the backend
  • Fixed multiple errors in the browser's console in the backend
  • Improved some system performance when running under load and during site search indexing
  • Fixed a few Push Publishing Issues
  • Fixed multiple issues for WebSphere 8
  • Fixed the Auto Login Checkbox
  • OSGi can now be disabled
  • Tags will now be imported properly when loading users from a CSV file

Changelog


dotCMS 2.5.2

Available: Dec 19, 2013

Fixes

  • Fixed concurrency issues with the dotcms cache under load
  • OSGi Examples all use Gradle now for building. This makes deploying and building plugins much easier
  • Fixed the issue where modifying files in a theme could cause the theme to disappear
  • Improved the Upgrade from dotcms 1.9 to 2.5.2+
  • Fixed over 20 Push Publishing Issues

Things to know

  • If you delete your osgi-extra file the system will try to generate a new one for you. It will do nothing if you leave it alone

Changelog


dotCMS 2.5.1

Available: Oct 21, 2013

Improvements

  • Workflows will now Push Publish when Pushing a Structure
  • When Content is Pushed the Workflow will be maintained meaning you will be in the same step on the Receiving server
  • When Pushing Structures the Field Variable name is now used for Fields which is important when the inodes are different but the Field Variable is the same

Fixes

  • Fixed multiple issues when using the Push Publish Actionlet associated with Workflow
  • The User-Agent is now set properly in the header when using dotCMS functionality like Site-Search, Timemachine etc..
  • Fixed an issue when adding binary imagines to Events
  • Fixed Push Publishing a Page when it contains a Working version of Content but no Live version
  • Fixed multiple JS Script Errors on Content Search Manager
  • Fixed issues when retrying a failed Bundle
  • Improved dotcms logic on flushing the cache which will improve the performance of the system
  • Fixed an issue when binary fields weren't being copied over when creating a new language of an existing content
  • A number of stability and performance tweaks mostly surrounding Push Publishing

Things to know

  • There is a small DB change that will happen on Upgrade. We do not typically do this in a patch release but needed to on this one

Changelog


dotCMS 2.5

Available: Sep 23, 2013


New Features

Push Publishing for the following objects

  • Hosts
  • Folders
  • Files
  • Menu Links
  • HTML Pages
  • Templates
  • Containers
  • OSGI Bundles
  • Categories
  • Structures
  • Users
  • Push Publishing will figure out your dependencies. ie.. Folders,files etc.. under your host
  • You can build Bundles in the UI as your browse around the dotCMS. These Bundles can be uploaded into other dotCMS installs
  • For more info see http://dotcms.com/docs/latest/PushPublishing

Overview of Fixes/Improvements

  • The Content REST API is much improved with new examples see http://dotcms.com/docs/latest/RESTSaveContent
  • Content Search Manager UI/XP Improvements. Now includes a simple search over all content
  • Edit Mode now will keep the session alive after long periods of inactivity
  • Company Tooling is now a Configuration Tool. In the future this will be used for dotCMS Configuration in the UI
  • Updated our Twitter tooling so the newer authentication works
  • Improved the Authentication methods for the REST APIs. Can now use Header, BASIC, Form and Session authentication
  • Site Search now respects content on the System Host(All Hosts) see https://github.com/dotCMS/dotCMS/issues/3123
  • XSS Viewtool added see https://github.com/dotCMS/dotCMS/issues/3064
  • Special Characters not import better when importing Content. See https://github.com/dotCMS/dotCMS/issues/3327
  • User Agents are now set when the dotCMS is rendering its own pages for its interal tooling. The possible agents match their functionality. The possible values are DOTCMS-SITESEARCH, DOTCMS-CMIS, DOTCMS-HTMLPAGEDIFF, DOTCMS-TIMEMACHINE, DOTCMS-BROWSER

Things to Know

  • Over 300 Bugs and Fixes have been made between 2.3 and 2.5
  • Lots of IE9 and IE10 issues addressed
  • Added a new configuration CONTENT_ESCAPE_HTML_TEXT which controls the escaping of special UTF8 characters when importing content and in the WYSIWYG Tool
  • If you have been running 2.5 master you may need to delete the data from the push
  • The Email Campaign manager and functionality has been deprecated and will be removed in a future release.
  • Using filters instead of queries for performance (off by default).  You can set the property ELASTICSEARCH_USE_FILTERS_FOR_SEARCHING to true. This should improve the speed of searching for content (at times up to 60%). In 2.3 defaults to false but will be set to true in later versions
  • When using IE versions less then 9 with the dotCMS back end now requires the Google Chrome Frame
  • The new Javadoc is located at http://dotcms.com/docs/latest/javadocs/index.html
  • To see a full list of the 590+ issues worked on, please on visit our issues on GitHub


dotCMS 2.3.2

Available: Jun 16, 2013


Overview of Fixes/Improvements

  • Addressed issues with pre 2.0 files in dotCMS
  • Addressed the issue where pages could be lost from CMS Maintenance Tooling
  • Addressed IE8 issues on login screen
  • Addressed Full Reindex issues where dotCMS wouldn't switch to the new index even though no content was left to index
  • Fixed the Random Sort in the ContentTool

Security Fixes

  • Removed some test JSPs http://dotcms.com/security/SI-11
  • Locked down dotCMS Scripts under the JSP directory
  • Removed XSS from Login Screen http://dotcms.com/security/SI-14
  • Addressed issues with DWR being too open
  • Fixed SQL Injection Issue http://dotcms.com/security/SI-8

Notes

  • Changed the default for Clickstream. dotCMS now ships with it on by default


dotCMS autoupdater_3.0.1

Available: May 14, 2013

dotCMS autoupdater_2.5

Available: May 14, 2013

dotCMS 2.3.1

Available: May 10, 2013


Overview of Fixes/Improvements

  • Fixed the Windows issue when Downloading Data/Assets
  • Fixed an issue with Webdav where files could overwrite other files with like filenames