Installation
MediaHub is three modules, not one. Here's why, and exactly how to install them in the right order.
Why three modules?
ProcessWire has a convention of splitting large features across module types: a core module that owns the data, a Process module that provides the admin UI, and an Inputfield module for the field editor. MediaHub follows this pattern:
| Module class | What it does |
|---|---|
MediaHub | The core. Installs all templates, fields, database tables, and the page structure. Declares the other two as dependencies; ProcessWire installs them automatically. |
ProcessMediaHub | The admin UI. Provides the Setup → Media Hub section: library, upload, asset detail, tags, and collections. |
InputfieldMediaHub | The picker. Adds the MediaHub field type, the picker modal, crop badges, and per-field settings to the page editor. |
You only need to install MediaHub. ProcessWire handles the rest. This is the same mechanism that built-in module pairs like FieldtypePage / InputfieldPage use.
Step 1: Drop the files in
Copy or clone the MediaHub folder into site/modules/MediaHub/. The folder name must be exactly MediaHub, not MediaHub-main or anything else, or ProcessWire won't recognise the module.
Step 2: Refresh modules
In the ProcessWire admin, go to Modules → Refresh. This scans your modules directory and picks up the three new modules.
Step 3: Install
Find Media Hub (MediaHub) in the Modules list and click Install.
ProcessWire will install all three modules in dependency order: MediaHub first, then ProcessMediaHub, then InputfieldMediaHub, each calling its own ___install() method. You'll see a configuration screen after install; click Submit to accept the defaults.
A note on the configuration screen
The configuration screen includes a section labelled "Inputfield modules available for page selection" with a list of options (Select, Checkboxes, AsmSelect, etc.). This is a standard ProcessWire prompt that appears for any FieldtypePage-based inputfield. It has no effect on how MediaHub works. Leave the defaults as-is and click Submit.
After installation
Once installed, MediaHub will have:
- Created its page structure under a hidden admin branch
- Added a Media Hub item to the Setup navigation
- Registered all necessary templates and fields
Go to Setup → Media Hub. If you see the empty library interface, you're done. Try uploading a test image to confirm everything is working.
If you get a permissions error on first load, check that your web server has write access to site/assets/files/. This is the same requirement as ProcessWire's own file uploads.
Uninstalling
MediaHub requires a config value, a pre-uninstall review, and a confirmation step before anything is deleted. See the dedicated Uninstalling page for the full walkthrough.