Magnolia 5.6 reached end of life on June 25, 2020. This branch is no longer supported, see End-of-life policy.
...
The default JCR persistency layer in Magnolia 5.6 is the H2 database, which is reflected in the following setting of the magnolia.repositories.jackrabbit.config
property in the magnolia.properties
file:
...
The Standard Templating Kit (STK) was deprecated on September 15, 2017, reaching the end of life on December 31, 2018. The replacement for STK is the Magnolia Templating Kit (MTK), first released with Magnolia with Magnolia 5.4 on 4 on July 3, 2015. MTK is quicker to learn than STK and requires fewer skills.
...
magnolia-publishing-parent
to (See Publishing module) to your bundle, either manually as pre-built jars or as dependencies.magnolia-publishing-transactional-parent
(See Publishing Transactional module) reactor. subscribers
were correctly migrated from /server/activation
to /modules/publishing-core/config/receivers
....
../WEB-INF/lib
folders of your author and public instances. Add the activation JAR files in their place.Exclude the publishing dependencies from the POM and add the old activation dependencies.
See also Publishing and activation.
The introduction of content tagging in Magnolia 5.6 has had an effect on node type and workspace names:
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
<dependency>
<groupId>info.magnolia.eebundle</groupId>
<artifactId>magnolia-enterprise-pro-demo-webapp</artifactId>
<version>${magnoliaBundleVersion}</version>
<type>pom</type>
<!-- declare the exclusions here -->
<exclusions>
<exclusion>
<groupId>info.magnolia.publishing</groupId>
<artifactId>magnolia-publishing-core</artifactId>
</exclusion>
<exclusion>
<groupId>info.magnolia.publishing</groupId>
<artifactId>magnolia-publishing-transactional-core</artifactId>
</exclusion>
<exclusion>
<groupId>info.magnolia.publishing</groupId>
<artifactId>magnolia-publishing-sender</artifactId>
</exclusion>
<exclusion>
<groupId>info.magnolia.publishing</groupId>
<artifactId>magnolia-publishing-transactional-sender</artifactId>
</exclusion>
<exclusion>
<groupId>info.magnolia.publishing</groupId>
<artifactId>magnolia-publishing-receiver</artifactId>
</exclusion>
<exclusion>
<groupId>info.magnolia.publishing</groupId>
<artifactId>magnolia-publishing-transactional-receiver</artifactId>
</exclusion>
<exclusion>
<groupId>info.magnolia.publishing</groupId>
<artifactId>magnolia-publishing-app</artifactId>
</exclusion>
<exclusion>
<groupId>info.magnolia.publishing</groupId>
<artifactId>magnolia-publishing-transactional-app</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>info.magnolia.activation</groupId>
<artifactId>magnolia-module-activation</artifactId>
</dependency>
<dependency>
<groupId>info.magnolia</groupId>
<artifactId>magnolia-module-exchange-transactional</artifactId>
</dependency> |
See also Publishing and activation.
The introduction of content tagging in Magnolia 5.6 has had an effect on node type and workspace names:
marketing-tag
node type and is stored in the marketing-tags
workspace.marketing-tag
node type and is stored in the marketing-tags
workspace.tag
node type and is stored in the tags
workspace....
log4j2.xml
that Magnolia provides and customize it to your needs.Update your magnolia.properties (log4j.config) to point to the new file.
Tip |
---|
We recommend the new file be called |
Do a basic library check:
log4j-1.2.17.jar
or similar in WEB-INF/lib anymore.log4j-api-2.8.2.jar
log4j-core-2.8.2.jar
log4j-slf4j-impl-slf4j-impl-2.8.2.jar
(the slf4j implementation is now provided by Log4j 2)
Warning |
---|
Make sure you don't have |
If in doubt about your config, you may set the level of Log4j's status-logger to debug as follows:
Code Block | ||
---|---|---|
| ||
<Configuration status="DEBUG">
... |
Make sure you don't have |
If in doubt about your config, you may set the level of Log4j's status-logger to debug as follows:
Code Block | ||
---|---|---|
| ||
<Configuration status="DEBUG">
... |
Since ClientErrorInterceptor
does not exist in RESTeasy 3, its capabilities were removed from our client implementation, the REST client module. If you have been relying on such objects, you have to handle it in a different way.
Please be aware that the version numbers for the Magnolia main and UI projects are not in sync with the version number of the bundles starting with release 5.6.3.
If you are updating from an earlier version:
Projects based on an older maven archetype may not build correctly starting with Magnolia 5.6.3 - because the version of the Magnolia main modules is not the same as the Magnolia bundle anymore. If you experience a problem, please update your project parent pomSince ClientErrorInterceptor
does not exist in RESTeasy 3, its capabilities were removed from our client implementation, the REST client module. If you have been relying on such objects, you have to handle it in a different way.
Anchor | ||||
---|---|---|---|---|
|
...
/.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.
...
When you click the Export button in a content app or from the JCR tools Tools app, the XML opens directly in the browser, replacing the AdminCentral instead of showing the usual Download dialog from the browser. This issue only affects the upgrades to Magnolia 5.6.6.
...