Field converters
To provide a smooth transition from Magnolia 5 to Magnolia 6 UI, a number of field converters have been introduced since Magnolia 6.2. These converters allow you to use a Magnolia 5 UI dialog definition in a Magnolia 6 UI app.
Example definition
To open a Magnolia 5 UI dialog definition in an app migrated to
Magnolia 6 UI, use the
info.magnolia.ui.dialog.action.CompatibilityOpenDialogActionDefinition
class in your action definition.
myConvertedDialog:
class: info.magnolia.ui.dialog.action.CompatibilityOpenDialogActionDefinition
dialogId: contacts:renameContact
icon: icon-editConversion is done automatically for every action using
info.magnolia.ui.dialog.actions.OpenDialogActionDefinition when the
magnolia-ui-framework-compatibility module is included in your webapp.
Supported fields
| Magnolia 5 UI definition | Magnolia 6 UI equivalent |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Known limitations
A field converter falls back to an empty field for any Magnolia 5 UI definition that is not supported.
Field definitions
The following Magnolia 5 UI definitions cannot be converted:
-
info.magnolia.ui.form.field.definition.PasswordFieldDefinition -
Those brought in by modules other than
magnolia-ui-framework-compatibility(for example,info.magnolia.dam.app.ui.field.definition.DamUploadFieldDefinition)
In addition, custom fields cannot be converted as they must be configured using Magnolia 6 UI.
|
Link fields can only be converted without the capability to preview content. |