This documentation applies to Omni for Umbraco 17 and 18. Both version lines have the same functionality and configuration. Choose the package version for your Umbraco site.
Built-in editor aliases
Umbraco.TextBoxUmbraco.TextAreaUmbraco.Plain.Stringfor direct text values; recognised editor UIs can use specialised handling as described below.Umbraco.RichTextandUmbraco.TinyMCEUmbraco.BlockList,Umbraco.BlockGridandUmbraco.SingleBlockUmbraco.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.TextInputUmbraco.Community.Contentment.TextboxListUmbraco.Community.Contentment.ContentBlocksUmbraco.Community.Contentment.Notes
Third-party package compatibility
Omni includes dependency-free support for selected third-party property editors. The package does not install or reference these editors; it recognises their persisted value shapes when they are already installed on the Umbraco site.
- SeoVisualizer (
EnkelMedia.SeoVisualizer): translates populated SEO titles and descriptions while preserving indexing and title-suffix settings. - MetaMomentum (
DM.MetaMomentum): translates search and explicitly overridden social titles and descriptions while preserving media identifiers, indexing settings and fallback behaviour. - UmbNav 4.x (
Umbraco.Community.UmbNav): translates prose names and descriptions for built-in navigation item types. URLs, content references, hierarchy, display settings and custom item types remain unchanged. - UmbHost.Tables 17.x (
UmbHost.Tables): translates prose cells only when the data type explicitly hasenableRichTextdisabled. Rich-text tables and tables containing HTML are skipped. - Community Heading (
Umbraco.Community.Heading): translates heading text while preserving the H1–H6 level. Top-level properties and headings nested in Block List, Block Grid and Contentment ContentBlocks are supported. - Dyfort/our HTag Editor (
ourHtagEditor, orUmbraco.Plain.Stringwith theourHtagEditorUI): translates its text while preserving heading tag, alignment and other fields. Supported at the top level and inside supported blocks. - Ph Heading (
Umbraco.Plain.Stringwith thePh.HeadingEditorUI): uses the safe rich-text parser to translate visible text while preserving inline formatting and attributes, including inside blocks.
Third-party compatibility is based on known persisted formats and fails closed when a value is malformed or its protected structure changes.
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.
Pickers are deliberately excluded because they store references rather than translatable prose. Translate a referenced content item separately when needed. Invariant properties are shared across languages and are also skipped; supported text properties must be configured to vary by culture.
Support applies to known persisted formats, not every string inside an editor. Rich-text HTML attributes are preserved rather than translated, and invariant block settings remain untouched. Missing, malformed or uncertain structures are reported instead of guessed.
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.