Limitations & planned improvements
Current limits of MediaHub v1.x, features in beta, and improvements planned for future releases. Updated as the product evolves.
This page is a living reference for what MediaHub does not do yet, which features are still maturing, and what is planned next. It is updated as releases ship — check the changelog for what has actually landed in each version.
How to read status labels
| Label | Meaning |
|---|---|
| Planned | On the product roadmap. Not available in the current release; wording and timing may change. |
| Beta | Available to use today, but still evolving. Expect UI or behaviour tweaks between point releases. Worth trying on a staging copy or a small pilot before relying on it site-wide. |
Admin interface language
Status: Planned
MediaHub's admin screens (library, upload, import, crop editor, and field picker) are written in English. Strings use ProcessWire's translation hooks, but the module does not yet ship translated language packs for other locales.
Multi-language sites are supported where ProcessWire itself is configured for languages. The gap here is localising the MediaHub admin experience, not blocking front-end output in your chosen languages.
Multi-language asset metadata
Status: Planned
On the asset detail page, core library metadata — Alt and About — is stored in standard single-language fields. Editors see one value per asset, not per-language tabs.
Asset page titles follow your site's normal ProcessWire title setup; on some multilingual sites the title may already be translatable through ProcessWire, independent of MediaHub.
For template output, findRaw can return language-aware title, alt, and related fields when your install uses ProcessWire's multi-language field types. The planned work is extending the admin editing experience so librarians can manage those translations in one place.
Import and hosting limits
Status: Current limitation (not beta — use with care)
MediaHub offers two import paths:
- Scan and import — site-wide scan of existing ProcessWire image fields, then import selected files into the library. Mature and tested at large scale, but each import creates new asset pages and copies files. Imports are capped at 500 images per request; run larger jobs in sensible batches.
- Import page images — per-field button on the page editor (see Beta below).
On shared or modest hosting, respect PHP memory and time limits. Take a database backup before bulk work, filter by template or field rather than importing everything at once, and monitor progress. See Importing Assets and the Migration Guide for practical batch sizes and rollback thinking.
Import page images
Beta. The Import page images workflow is available and useful for gradual migrations, but we still treat it as a beta feature: matching heuristics and edge cases may be refined in future releases. Try it on a copy of the site first; verify a sample of matches before importing hundreds of files from legacy fields.
When enabled on a MediaHub field, editors can pull images from other standard image fields on the same page into the MediaHub field without hunting the library. It is ideal for phased rollouts, not a replacement for the main Scan and import tool when you need site-wide migration.
Custom fields on MediaHub assets
Status: Available (1.19.25)
MediaHub integrates ProcessWire's standard custom-field workflow into shared assets and the page-edit drawer. Add fields to the pkd-mediahub-asset template and they appear on the asset detail page and (by default) in every InputfieldMediaHub drawer, with the same override-and-reset model as Title and Alt. Use a file-less mediahub-field-{fieldName} template when you want to curate a specific drawer or add field-only metadata. See Custom Fields for full setup and API details.
Migrating legacy Pageimage custom field values
Status: Planned
If your site uses custom fields defined on standard ProcessWire image fields (the field-{fieldName} template pattern on legacy image fields), those per-image values are not automatically carried across when you import assets into MediaHub. The import tools bring in the image file and basic metadata; editorial custom field values need to be re-entered or migrated manually via your own scripts. A dedicated migration tool for this pattern is on the roadmap. See Importing Assets and the Migration Guide.
Questions or priorities
If a limitation affects your project, note your MediaHub version and use the support channel provided with your licence. This page will be revised when items move from planned or beta to generally available.
Last updated