Magnolia 5.5 reached end of life on November 15, 2019. This branch is no longer supported, see End-of-life policy.
Magnolia CORE 5.5.2 delivers the following changes and improvements:
Actions such as adding nodes and properties in trees and editing property values in-place caused the tree to scroll back to the top. The user lost focus and had to scroll back to the item they were editing. This erratic scrolling behavior is now fixed. The tree now maintains position when an action is completed.
The scrolling issues affected recent versions of Chrome, Opera and Firefox 49+.
Page and component personalization are no longer mutually exclusive. You can now personalize a page and its components at the same time to create detailed personalization scenarios. The feature is disabled by default but you can enable it in personalization-components
module configuration. Component personalization is an EE Pro feature.
The new Report an issue subapp in the About Magnolia app allows developers to report JIRA issues directly from Magnolia.
The default browser cache policy introduced in the previous release now applies only to the developer mode in the author instance, which improves the overall user experience.
In App launcher layout configuration, you can now define a default group for new apps. You can also specify which apps you don't want to appear in the App launcher.
URIPrefix
properties in /server/URI2RepositoryMapping/mappings/
now all come with a trailing slash, for example /contacts/
instead of just /contacts
, to prevent URI mapping conflicts for root-level pages having the same name as the URI prefix. CNTCTSAPP-98, MGNLPN-252, MGNLGS-120Fixed an issue where double-clicking the Edit icon on the component or area bar in the Page editor opened two instances of the Edit dialog. If you are using a custom implementation for /modules/pages/apps/pages/subApps/detail/actions/editElement
, be aware that the content change event also has to be sent on the Cancel action of the dialog. PAGES-116
visitorCookies
are httpOnly
by default and can be made even more secure by adding the secure
property in the VisitorDetectorFilter
. MGNLPN-250This release also comes with a number of bug fixes and security improvements. An aggregated changelog for 5.5.2 contains all the changes.
This release is a recommended update for all users of Magnolia 5.
This release includes the following new module versions:
magnolia.repositories.jackrabbit.config
property in the magnolia.properties
file set to the database you used before updating. For example, for Derby set the property as follows: magnolia.repositories.jackrabbit.config=WEB-INF/config/repo-conf/jackrabbit-bundle-derby-search.xml
Generally, follow the standard update procedure.
The following changes apply only to the users running Magnolia 5.4 (major release) and maintenance releases 5.4.1 to 5.4.3.
CE and EE users
Add the following lines in your magnolia.properties
file. They configure a directory for loading file system resources and the file types Magnolia should observe in the classpath and reload on-change:
magnolia.resources.dir=${magnolia.home} magnolia.resources.classpath.observation.pattern=.*\\.(ftl|yaml)$
If you had EE Pro 5.4.x or previous and are installing EE Pro 5.5.2
Due to component personalization bringing in new features to the page editor, you must replace the widgetset in the magnolia.properties
file. Either replace or add (depending on the update path):
magnolia.ui.vaadin.widgetset=info.magnolia.widgetset.MagnoliaProWidgetSet
If you used a previous version of Magnolia with an Apache Derby database, make sure you keep your magnolia.repositories.jackrabbit.config
setting in your magnolia.properties
file.
Magnolia bundles now ship with the following default setting:
magnolia.repositories.jackrabbit.config=WEB-INF/config/repo-conf/jackrabbit-bundle-h2-search.xml
If you continue to work with STK, use the new magnolia-enterprise-pro-stk-bundle
as a basis for your project. It includes Enterprise Pro, STK and the old demo project. You get all STK functionality out of the box. Exclude the demo-project if it's in your way.
In order to enable getting an HTML excerpt in a query result, you should update the configuration files of your Jackrabbit instances. Add the two <param/>
directives within your <SearchIndex>
block.
<SearchIndex> <!-- more params here --> <!-- needed to highlight the searched term --> <param name="supportHighlighting" value="true"/> <!-- custom provider for getting an HTML excerpt in a query result with rep:excerpt() --> <param name="excerptProviderClass" value="info.magnolia.jackrabbit.lucene.SearchHTMLExcerpt"/> </SearchIndex>
Add the log configuration for org.reflections
... <category name="org.apache.jackrabbit"> <priority value="WARN" /> </category> <!-- Reflections library spoils logs with hundreds of harmless warnings; tries to look into native libs but none of its DefaultUrlTypes can handle them. --> <category name="org.reflections"> <priority value="ERROR" /> </category> <category name="com"> <priority value="WARN" /> </category> ...
To update your project, follow the standard update procedure, then make the following changes:
Using the content connector.
Updating configuration of availability rules and default rule classes
Updating selected action definitions with node-type based availability
DamManager
with AssetProviderRegistry
.info.magnolia.module.workflow.jbpm.JbpmWorkflowManager#completeWorkItem
method, checking for present parameters is obsolete and refers to publication related workitems. The method is no longer used for completing a workitem in the new human task context. It is still valid in the context of completing service tasks, however.Stop using the info.magnolia.module.workflow.jbpm.JbpmWorkflowManager#getWorkItem
method. It was used to complete a work item for human tasks. Furthermore, the wrapper we initialize only holds the mgnlData
map.
The previously hardcoded mgnlData
parameter is now configurable in /modules/workflow/commands/workflow/activate/activate/parameterMapName
.
info.magnolia.widgetset.MagnoliaWidgetSet
.magnolia.properties
file.Are you running on Magnolia 4.5 or earlier? It’s time to move to 5. Contact us for migration support and look at the migration process.
In 5.5.1 we removed a fallback mechanism checking if the handle prefix had been prepended incorrectly in a request with the complete path to the item (MAGNOLIA-6882). This however entails that on production instances running under registered domain names, not on a test or development server accessible via localhost, such handle prefixes can no longer form a part of the toURI
parameter in a module's virtualURIMapping
setting. On a production instance please be sure to have the prefixes removed from the parameter.
This unfortunately affects also the travel demo in our 5.5.1 and 5.5.2 bundles. With handle prefixes travel
and sportstation
present in the toURI
parameter, the links to the tours in the travel demo are inaccessible on demo.magnolia-cms.com or any other registered domain, and the following changes are necessary:
forward:/travel/tour?tour=$1
> forward:/tour?tour=$1
forward:/sportstation/tour?tour=$1
> forward:/tour?tour=$1
A development deployment under localhost is not affected. MGNLDEMO-204.
When selecting properties in a definition that are actually extended from another node in the config workspace, opening the definition in the Configuartion app will not work correctly, as the underlying node/property doesn't exist. For example,
/.magnolia/admincentral#app:definitions-app:;app~site@subApps/browser/actions/addFolder/icon:treeview
points to config:/modules/site-app/apps/site/subApps/browser/actions/addFolder/icon
but all the actions are inherited from /modules/ui-admincentral/apps/configuration/subApps/browser
via extends.
Magnolia 5.5.2 ee-bundle may require you to allocate more memory the Java Virtual Machine (JVM). If you see a java.lang.OutOfMemoryError
in the startup log or the system stops responding during installation, increase the Java heap size. The default maximum heap size is 512M. Try a higher amount such as 1024M. We are working on uncovering the root cause for the increased memory need.
See: Java out of memory
The Magnolia team would also like to thank everyone who reported issues, contributed patches, or simply commented on issues for this release. Your continued interest helps us make Magnolia better. Special thanks go to: Vikas Attiguppa, Mariusz Chruscielewski, Shubha Gowda, Michiel Meeuwissen, Teresa Miyar, Matteo Pelucco, Frank Sommer and Tom Wespi.