From 6.6.1 to 6.6.2

Published May 18, 2020

The Jahia upgrade to the consists now of 1 unique easy step, please read it carefully before proceeding.


  • Stop the user requests / traffic to the server (either on the front-end Apache HTTPD server or firewall/router)
  • Stop Jahia before backing up and running the fix applier
  • Backup your Jahia installation before running the fix applier 
  • Run a pre-production test first


In the current release we have fixed a security issue on tokenized form for allowing a token to be submitted only once so tokens are not reusable anymore. In order to be able to reuse token as it was before the release, we provided a property to set in the tokenizedForm tag: <template:tokenizedform allowsmultiplesubmits="true">. If you have already used this tag in your modules please review your implementation.

Step 1:Jahia Core & Modules Migration

The first step of the migration is to copy the fix applier Jahia6.6_6.6.1.0_r43343_to_6.6.2.0_r47118.jar on your production server.

At this stage, a list of all the files you have customized in your installation will help you to go through the upgrade and decide more easily if you want to merge, keep or overwrite the files.

For all the files impacted, the fix applier will create a backup in the following folder:

$USER_HOME/.fixapplier/backup/ and a detailed log is also available in your <Jahia_installation>/tomcat/webapps/ROOT/META-INF/updates/history/fixes/Jahia6.6_6.6.1.0_r43343_to_6.6.2.0_r47118.log or if you didn't use the default ROOT context in your <Jahia_installation>/tomcat/webapps/<your context>/META-INF/updates/history/fixes/Jahia6.6_6.6.1.0_r43343_to_6.6.2.0_r47118.log

If the fix creator detects that a file has been modified it will try to automatically merge it. If the merge fails you will be able to overwrite the files or skip it installing the modification.
If the merge fails or you decide to skip it, a diff file <file_name>.patch will be available in the destination folder, please make sure that you don't forget to manually apply the changes.

1. Stop Jahia

2. Open a terminal in the JAHIA_INSTALLATION/tomcat/webapps/ROOT or JAHIA_INSTALLATION/tomcat/webapps/<your context> if you didn't use the default ROOT context  and type the following command:

java -jar <PATH-TO-FIX-APPLIER>/Jahia6.6_6.6.1.0_r43343_to_6.6.2.0_r47118.jar

The fix applier will manage the upgrade of your platform by deleting, updating and merging all the necessary files. It will now handles the migration of Jahia Core and all the additional Jahia modules installed on your platform.

In case you have externalized your configuration (jar file or folder), you will need to apply the modification relative to and manually at the appropriate place.


Please review your log before starting the next step to ensure you haven't missed a file that needs to be manually merged.



3. Clean the following Tomcat folder


The fix applier now handles the cleaning of the tomcat folders automatically but depending on the OS and some permissions you may need to clean it manually.

Remove the content of your folders JAHIA_INSTALLATION/tomcat/temp and <JAHIA_INSTALLATION>/tomcat/work


4. Clean the ressource folder


Remove the content of your folder  <JAHIA_INSTALLATION>/tomcat/webapps/ROOT/resources or <JAHIA_INSTALLATION>/tomcat/webapps/<your context>/resources if you didn't use the default ROOT context.


5. Start JAHIA

Your upgrade to Jahia is now completed

With Jahia the embedded Tomcat has been upgraded from 6.0.35 to 6.0.37. This standard upgrade package doesn't handle Tomcat's upgrade and Jahia is still compatible with tomcat 6.0.35