Magnolia 4.5 reached end of life on June 30, 2016. This branch is no longer supported, see End-of-life policy.

Page tree
Skip to end of metadata
Go to start of metadata

What has changed since Magnolia 3.5.8

Magnolia 3.6 CE delivers improvements in two main areas :

  • Performance and memory usage: by removing unnecessary versioning of nodes, performance is generally improved. The size of repositories is also notably reduced by this. A number of memory issues have been fixed, which now allows large activations to be executed smoothly.
  • Caching: a completely new caching API has been designed to support complex caching situations. It allows pluggable strategies and multiple levels of caching.

In addition, the Enterprise Edition of Magnolia 3.6 brings :

  • Advanced caching strategies.
  • Transactional activation.
  • Backup tool.

Other notable changes

  • Moving a node doesn't deactivate it automatically anymore. See MAGNOLIA-2173 for details.
  • When activating a moved node, it is now correctly activated under its new path. See MAGNOLIA-1899 for details.
  • Activation now displays a comment dialog, giving authors a chance to comment on their changes.
  • We now ship with Jackrabbit 1.4. The default persistence manager is now of the "bundle" family, still using Derby.
  • Sample users have changed. We now have "eve", "patrick" and "david". See MAGNOLIA-2165 for details.
  • FckEditor was updated to version 2.6.2 (which amongst other brings Safari compatibility), and our integration module was renamed to magnolia-module-fckeditor for consistency. (MAGNOLIA-2194)
  • Templating: inheritance is now supported for nodes as well as for properties. See MAGNOLIA-2128 for details.
  • The default behaviour of the cmsu:simpleSearch tag has changed since Magnolia 3.5.5, and should provide better results. It is possible to revert to the original behaviour by setting its useSimpleJcrQuery attribute to false. See MAGNOLIA-2068 for details.

A whole lot of bugs have also been fixed. As usual, the complete list of changes can be found on our Jira.

Known issues

Repository issues after upgrade

The version of Magnolia Tools bundled with Magnolia 3.6 and 3.6.1 has been updated. Please download the latest version (1.0.2) of Magnolia Tools from our download area, which includes fixes for MGNLTOOLS-21, MGNLTOOLS-22 and MGNLDATA-43.

Leopard

Leopard's firewall behaves significantly differently than the firewall shipped with OSX 10.4. The symptoms are that Tomcat seems unreachable ("kCFErrorDomainCFNetwork:302"), but unfortunately no message is clearly logged about the issue.

Please see the list of known issues in the administration section for more details.

How to update from Magnolia 3.5.x

  1. Stop your application server.
  2. Unpack the bundle corresponding to your current installation of Magnolia.
  3. Replace all jars found under the WEB-INF/lib directory of your Magnolia instance(s) by the new ones found in the bundle you just unpacked. Make sure you remove any module you had previously removed from your 3.5 instance(s) and re-add any extra module you might have added as well.
  4. Update the nodetypes definitions: execute the updatenodetypes or updatenodetypes.bat script from the add-ons/magnolia-tools/bin folder. On a typical setup, you'll only need to pass it the -webapp argument, like for example: ./updatenodetypes -webapp /Applications/Magnolia/apache-tomcat-5.5.25/webapps/magnoliaAuthor/ - Do this for all your instances.
  5. Update the content: execute the update35to36 or update35to36.bat script from the add-ons/magnolia-tools/bin folder. On a typical setup, you'll only need to pass it the -webapp argument, like for example: ./update35to36 -webapp /Applications/Magnolia/apache-tomcat-5.5.25/webapps/magnoliaAuthor/ - Do this for all your instances.
  6. Optionally, you might want to delete all the indexes to give them a little boost: delete the index folder under each workspace directory: repositories/magnolia/workspaces/config/index, repositories/magnolia/workspaces/website/index, and so on. Indexes will get recreated on startup, which might take a while, depending on the size of your repository.
  7. If you customized any of the magnolia.properties files, please compare the changes you made with the new corresponding file. Specifically, the magnolia.root.sysproperty and magnolia.server.id have been removed and are not in use anymore, and the magnolia.develop property should be set to false; it used to be true by default in previous version of Magnolia, but if this is not intentional on your part, you might want to set it back to false for better performance.
  8. If you customized the log4j configuration, you might want to make sure the net.sf.ehcache category has a threshold of WARN, otherwise you'll quickly see your log files flooded with TRACE messages from ehcache. If you didn't customize the log4j configuration, you can simply replace your current file with the corresponding file in 3.6. (/WEB-INF/config/default/log4j.xml)
  9. Restart your application server.
  10. Using your browser, go to your Magnolia instance(s) and follow the instructions given by the install/update wizard.
  • The update35to36script is currently only available for licensed users of Magnolia Enterprise Edition using Jackrabbit. If you have no license, you'll have to:
    • Export all your data, from all workspaces. Check the backup scripts provided on the wiki for a convenient way of performing this. (Do not forget to customize the scripts to add other workspaces if needed)
    • Import it in a fresh 3.6 instance.
    • Restart the webapp in order to have the update mechanism applied on your configuration.
  • If you are not using Jackrabbit, please read the technical notes below and contact your support channel if necessary.
  • The version of Magnolia Tools bundled with Magnolia 3.6 and 3.6.1 has been updated. Please download the latest version (1.0.2) of Magnolia Tools from our download area, which includes fixes for MGNLTOOLS-21, MGNLTOOLS-22 and MGNLDATA-43.

How to update from an earlier version of Magnolia

We recommended you first update to Magnolia 3.5.8. Please refer to the  release notes for Magnolia 3.5.8. Once you successfully updated to Magnolia 3.5.8, follow the procedure above.

If you need to activate content from a Magnolia 3.0.x instance, please follow the workaround described on MAGNOLIA-2049.

Technical details about nodetypes modifications

If you can not use the updatenodetypes and/or update35to36 scripts, here are some details on how to achieve similar functionality:

Nodetypes definitions

The Magnolia node types have changed: mgnl:content, mgnl:contentNode, mgnl:metaData and other module specific node types now have mix:referenceable has a supertype (along with nt:hierarchyNode as before); mgnl:metaData should not have mix:versionable as a supertype anymore.

Existing nodes

Since Magnolia was adding the mix:versionable mixin by code, existing nodes have that mixin, and it should be removed for optimal performance; accordingly, versioning properties should be removed from these nodes. The mgnlVersion workspace should also be cleaned up from unnecessary version information.