Documentation

Supported property editors

See which persisted values Omni can translate safely and which values it deliberately skips.

Built-in editor aliases

  • Umbraco.TextBox
  • Umbraco.TextArea
  • Umbraco.RichText and Umbraco.TinyMCE
  • Umbraco.BlockList, Umbraco.BlockGrid and Umbraco.SingleBlock
  • Umbraco.MultipleTextstring

Block List and Block Grid support includes supported text editors nested inside other blocks. Omni walks each level, translates the readable values and retains the existing block hierarchy, keys, settings and order.

Contentment compatibility

Omni recognises selected persisted Contentment value shapes without taking a direct package dependency:

  • Umbraco.Community.Contentment.TextInput
  • Umbraco.Community.Contentment.TextboxList
  • Umbraco.Community.Contentment.ContentBlocks
  • Umbraco.Community.Contentment.Notes

Values that are skipped

Umbraco.MarkdownEditor is currently unsupported. Rich text containing embedded blocks translates the markup, but skips the embedded block content and reports a warning.

Media and content pickers, URLs, aliases, keys, UDIs, booleans, numbers, dates, colours, settings and arbitrary JSON are not translated. Unsupported editors are shown in the preview report and skipped without guessing at safe write behaviour.

Custom editors

Editors that persist plain text or compatible rich text can be mapped through configuration. Complex persisted shapes can be supported with an IContentTranslationPropertyEditorAdapter. See custom property editors.

Diplo Translator Omni

Ready to translate your first draft?

Bring AI translation into the Umbraco backoffice — and keep the final say with your editors.