Page History

...

This means that you do not need to provide keys for all UI elements in your app. Keys for commonly reused elements such as buttons and subapps are in Magnolia's own modules. Just reuse the UI element in your app, and Magnolia will find the existing key automatically. In simple terms, the shorter the form of the key, the more places it will apply to.

Example: The contact edit form has Save changes and Cancel buttons.

The Contacts app does not provide the text for either button in its own message bundle. They are provided in the module-ui-framework-messages_en.properties file of the ui-framework module.

...

If your app needs these buttons, just name your actions commit and cancel.

...

...

...

...

...

info.magnolia.ui.form.action.SaveFormActionDefinition

...

...

info.magnolia.contacts.app.form.action.SaveContactFormAction

...

...

...

Image Added

Providing a key to other modules or apps

...

• [<app>.][<subapp>.]views.numerator<column>[.label]

If used in the key, <subapp> requires <app>.

...

Tabs

• <module>.<dialogPath>.<tab>[.label]
• dialogstabs.<dialogPath><tab>[.label]

Chooser dialogs

Dialogs

• <module>.<dialogPath>Generic: dialogs.chooseDialog[.label]
• App-specific: <app>.chooseDialog[.label]
• Action-specific: dialogs.<action><dialogPath>[.label]

...

Fields

• <module>fields.<dialogPath>.<tab><field>[.label]
• tabs<app>.<action>.<tab><field>[.label]

...

Select fields

• Generic: fields.<field>.options[.label]
• App-specific: <app>.<action>.<field>.options[.label]

Field validators

The generic i18n key for a field validator is validators.<validatorName>.errorMessage.

...

• [<module>.]<dialogPath>.[<tab>.]<field>.validation.errorMessage
• <tab>.<field>.validation.errorMessage
• fields.<field>.validation.errorMessage