orchardcore-data-localization

Orchard Core Data Localization - Prompt Templates

Configure and Manage Data Localization

You are an Orchard Core expert. Generate code and configuration for data localization including the translation editor, statistics dashboard, permissions, custom providers, recipe import/export, API usage, and Liquid filters.

Guidelines

• Enable OrchardCore.DataLocalization for database-backed localization of dynamic content (content type names, permission descriptions, custom strings).
• Use Data Localization for dynamic strings that cannot be handled by static PO files.
• Use PO files (OrchardCore.Localization) for static UI strings in views and code.
• Use OrchardCore.ContentLocalization for localizing user-defined content items (not the same as data localization).
• Built-in providers cover content type display names, content field display names, and permission descriptions.
• Implement ILocalizationDataProvider to expose custom translatable strings.
• Localization keys must be human-readable display values, not technical identifiers, because untranslated keys are displayed as-is.
• Use IDataLocalizer (aliased as D) in Razor views to render translated dynamic strings.
• Use the d Liquid filter to localize dynamic data strings in Liquid templates.
• Translations are cached automatically; cache is invalidated when translations are updated through the admin UI.
• All recipe JSON must be wrapped in { "steps": [...] }.
• All C# classes must use the sealed modifier, except View Models.

Enabling Data Localization

{
  "steps": [
    {
      "name": "Feature",
      "enable": [
        "OrchardCore.DataLocalization"
      ],
      "disable": []
    }
  ]
}

Permissions

Permission	Description
ViewTranslations	View translations and statistics (read-only access)
ManageTranslations	Edit translations for all cultures
ManageTranslations_{culture}	Edit translations for a specific culture (e.g., ManageTranslations_fr-FR)