Page History

...

Please note that the new short field type names affectnaming affects:

• The node name if the field is defined via JCR in the origin of the definition. The renamed fields defined originally as JCR nodes under /modules/<module-name>/fieldTypes folder. folders are now defined in YAML files (in the classpath).
  See the following example showing the definition of damUploadField in Magnolia 5.6.6 and the corresponding damUpload definition in Magnolia 5.7:
  Image Added
  Image Added
  
  
• The file namenames, if the field is defined via a YAML file, e.g.  the definition of the Expandable text field:
  

  /content-editor/fieldTypes/expandingTextField.yaml (in Magnolia 5.6.6)
  /content-editor/fieldTypes/expandingText.yaml (in Magnolia 5.7)

 If 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.

...