Page History

...

Check custom fields extending or decorating Magnolia fields

We have changed a few names for field definitions. This was part of the initiative allowing you 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:

Use the Definitions app to check for problems.

Apache Tomcat 9.0.8

If you use Apache Tomcat: we have upgraded to Apache Tomcat 9.0.8.

...