Menu

Sign In Create Free Account
Docs MediaHub Version 1.x Admin translations

Admin translations

Enable bundled Dutch, French, German, and Polish translations for the full MediaHub admin interface using ProcessWire Language Support.

MediaHub ships bundled admin translations for Dutch (nl), French (fr), German (de), and Polish (pl). German has been available since 1.19.51; Dutch, French, and Polish joined in 1.22.0. Every user-facing string in PHP views and JavaScript uses ProcessWire's translation functions, so additional languages can follow the same CSV workflow.

What is translated

Each bundled languages/*.csv file covers roughly 1,037 strings across:

  • Library, upload, import, and asset detail screens
  • Crop editor, labels, folders, and picker
  • InputfieldMediaHub drawer, Actions menu, and module config (including Preview covers)
  • JavaScript dialogs, flash messages, and client-side picker labels

Glossary notes vary by language — for example German uses Etikett / Etiketten rather than anglicised Label / Labels.

Bundled language files

LanguageProcessWire page nameCSV fileSince
Germandelanguages/de.csv1.19.51
Dutchnllanguages/nl.csv1.22.0
Frenchfrlanguages/fr.csv1.22.0
Polishpllanguages/pl.csv1.22.0

Automatic import

Translation import runs when:

  • ProcessWire's Language Support module is installed
  • A language page with the matching name exists (de, nl, fr, or pl)
  • You refresh or upgrade Process MediaHub under Modules

Import also re-runs when the bundled CSV changes or when a new language is added.

The language page name must match exactly — de, not german or de-DE. Names like dutch or fr-FR require manual CSV import instead (see below).

Setup steps

  1. Install ProcessWire's Language Support module (Modules → Site → Language Support).
  2. Create a language with the correct page name and a human title — for example page name de, title Deutsch (Setup → Languages → Add New Language).
  3. Go to Modules → Site → Process MediaHub and click Refresh.
  4. Set each admin user's Profile → Language to their preferred language.
  5. Open Setup → Media Hub and confirm the library toolbar, breadcrumbs, and detail pages appear in that language.

Important: The MediaHub admin UI follows the logged-in user's profile language. Setting the site default language alone is not enough.

Manual CSV import (fallback)

Use manual import when your language page has a different name, or when automatic import did not run after Language Support was added post-install:

  1. Go to Setup → Languages and open your language page.
  2. Use ProcessWire's language translation import for the ProcessMediaHub text domain.
  3. Import from the matching file in site/modules/MediaHub/languages/ — for example de.csv for German.

Symlinked dev installs

From 1.22.0, bundled translations also work when MediaHub is symlinked outside the site root (for example a git checkout linked into site/modules/). Module strings route through the canonical site/modules/MediaHub/… textdomain so nav dropdowns and other lookups resolve correctly.

Translating to other languages

To add a language MediaHub does not ship yet:

  1. Create the matching language in ProcessWire (Setup → Languages).
  2. Export or copy any bundled *.csv as a format reference.
  3. Translate strings and import via Language Support using the same CSV structure.

All admin strings are wrapped with __(), $this->_(), and the client-side pkdMhT() helper, so standard ProcessWire language workflows apply.

Multi-language sites vs admin UI

Admin translations localise the MediaHub admin experience for editors and librarians. They are separate from multi-language front-end output:

  • Asset page titles may follow your site's normal ProcessWire title language setup.
  • Alt and About on the asset detail page remain single-language fields today. See Limitations → Multi-language asset metadata.
  • findRaw can return language-aware title and alt when your install uses ProcessWire multi-language field types.

See also

Last updated