Page History

...

This page describes two ways in which you may define the type of a field in a form .

...

• For the fieldType property you no longer need to specify the field type using a fully qualified class name. Just provide the field's name as the value of the fieldType property.
  If your project uses the class propertty property in too many places, you can still continue using class. The feature is backwards compatible.
• We have streamlined the definition names by making them shorter. The Short field names list below on this page shows which fields are affected.

...

• The origin of the definition. The fields defined previously as JCR nodes under /modules/<module-name>/fieldTypes folders are now defined from YAML files.
  See the following example showing the definition of damUploadField in Magnolia 5.6.6 and the corresponding damUpload definition in Magnolia 5.7:
  
  
  
  
• The file names. If a field was previously defined in a YAML file, the file's name has changed to the new short name. See for example the definition of the Expandable Expanding text field:
  

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

...