Page History
...
You must remove the magnolia-module-webdav module because Apache Jackrabbit 2.16 no longer supports WebDAV.
Check
...
custom fields extending or decorating Magnolia fields
We have changed a few names for field definitions. This was part of the initiative to reference fields by its "short" name with the property fieldType (see Referencing fields). The name which may have changed is the node name if the field is defined via JCR in the folder modules/some-module/fieldTypes or the file name of a YAML based definition.
If you have custom fields which reuse an existing Magnolia configuration via YAML include, YAML inherit, JCR extends or by decoration, your custom definition may be broken now if you reference to a field which has changed its name.
Here's a list of the field names which have been changed:
| Old name | new name. |
|---|---|
Use the Definitions app to check for problems.
Check the magnolia.properties file
Between Magnolia 5.6.6 and Magnolia 5.7, the magnolia.properties file has not changed.
| Tip |
|---|
When upgrading Magnolia, it is always worth comparing your |
| Todo |
|---|
|
Below are the latest versions of the magnolia.properties files for the Magnolia 5.7 series:
| Artifact resource link | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Magnolia CE / Magnolia EE Standard *
| Code Pro |
|---|
Between Magnolia 5.6.6 and Magnolia 5.7, the magnolia.properties file has not changed.
| Tip |
|---|
When upgrading Magnolia, it is always worth comparing your |
| Todo |
|---|
|
Below are the latest versions of the magnolia.properties files for the Magnolia 5.7 series:
| Artifact resource link | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Magnolia CE / Magnolia EE Standard *
| Code Pro | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
...
| Code Pro | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Check custom fields extending or decorating Magnolia fields
We have changed a few names for field definitions. This was part of the initiative to reference fields by its "short" name with the property fieldType (see Referencing fields). The name which may have changed is the node name if the field is defined via JCR in the folder modules/some-module/fieldTypes or the file name of a YAML based definition.
If you have custom fields which reuse an existing Magnolia configuration via YAML include, YAML inherit, JCR extends or by decoration, your custom definition may be broken now if you reference to a field which has changed its name.
Here's a list of the field names which have been changed:
...
Apache Tomcat 9.0.8
If you use Apache Tomcat: we have upgraded to Apache Tomcat 9.0.8.
...
Overview
Content Tools