Menu

Docs MediaHub Version 1.x Asset Detail Page

Asset Detail Page

The asset detail view: preview, file information, crops, usage tracking, metadata editing, renaming, and actions.

Overview

Each asset in the library has its own detail page. Click any asset tile in the library to open it.

The main content sits in a bordered card; the page background shows through around it. The header strip shows stat cubes for file format, size, dimensions (images), crop count, and usage count. Below that:

  • Preview - full image preview for images; native audio/video player for uploaded media when the browser can decode the file; embedded YouTube/Vimeo player with click-to-play consent for embed assets; preview cover image for PDFs and other non-image types when set; file icon fallback when no cover exists
  • Preview image (non-image assets) - choose a library image or crop as the tile thumbnail, or rely on auto-generated covers when the server supports them. See Preview Covers
  • File information - filename, format, MIME type, file size, dimensions, upload date, and page ID
  • Crops - all crops created for this asset, viewable in grid or list mode. List view includes Created and Modified columns.
  • Image variations (raster images, from 1.21) - the original file plus every ProcessWire size variation already on disk in this asset's files folder, with dimensions, file size, modified time, and download. You can delete a variation after confirming. ProcessWire recreates a deleted size the next time a template, a field card, or pre-generated sizes on save requests it. The table lists existing files only; it does not generate new sizes. From 1.22.0, each image on a MediaHub field card creates two admin variations by default (260w card thumb + 800w preview/lightbox) instead of four. See Adding to templates → Thumbnails and disk variations and Field automation for pre-generating additional sizes on upload and save.
  • Usage - every ProcessWire page that references this asset, with links to edit or view
  • Metadata sidebar - from 1.19.25, split into Asset details (title, filename, alt text for images, custom fields) and Asset Internal Notes (About, labels, collections, preview image for non-image assets). A heart control marks or clears the asset as a site-wide favourite.

Actions

The Actions panel in the sidebar provides:

  • Crop image - opens the unified crop editor (raster images only). The action bar offers Save as crop (a child crop linked to this asset, listed in the Crops section above) and Save as new asset (a standalone Library asset with its own metadata). See Image Cropping.
  • Focus point - opens the editor to set which part of the image auto-generated crops should frame around (raster images only). See Focus Point.
  • Replace file (uploaded files, not embeds — beta, 1.22.31) — see Replace file or summary below.
  • Download original - downloads the source file
  • Copy URL - copies the direct file URL to the clipboard
  • Duplicate asset - creates a copy of the asset as a new page (including the file)
  • Delete asset - permanently deletes the asset and all its crops. The confirmation warns you if the asset is referenced on other pages (with a link to view usage) and lists how many crops will be removed.

When the Palette add-on is installed, a Palette button also appears in the quick toolbar beside the preview image (raster images only). It opens the same colour modal as the field Actions menu.

Replace file (beta)

Short summary — full workflow, staged job, logging, and limits: Replace file.

Public beta from 1.22.30; confirmation, cache-busting, and rich-text options reflect 1.22.31. Prefer staging; 1.22.2 remains the recommended production build until this feature graduates.

From the Actions sidebar, Replace file swaps the on-disk master for this asset while keeping the same page ID and references (images, SVG, video, audio, PDF, and other documents; not YouTube/Vimeo embeds). Larger swaps run as a staged job in the browser. Leave the tab open until the summary appears. Crop and variation stages apply to images only; see Replace file → PDF and other documents.

  • Collections, labels, title, alt, About, and other asset metadata stay on the same page. Only the file (and optionally its on-disk name) changes.
  • The confirmation shows current and new files side by side with Changes, Rich text, and Filename groups. Filename switches choose keeping the current name (recommended) or renaming to match the upload.
  • Matching library and field crops are rebuilt from the new master when stored geometry still fits the preset.
  • When aspect ratio changes, turn Fit to new shape on (default) to recalculate rich-text height from each saved width, or turn it off and adjust pages manually via Usage.
  • Optional Cache-bust replaced files adds mhv= timestamps in public HTML output so visitors see a new file when the on-disk name stays the same — see Configuration → Replacing files.
  • An audit entry is always written to the media-hub log, even when optional MediaHub logging is off.

Replacements respect module image size limits and the same colour rules as upload. See Uploading → Colour profiles and the 1.22.31 changelog.

Renaming files

The master filename in the File Information card has an inline edit button. Clicking it lets you rename the file on disk.

From MediaHub 1.19.0, crop filenames in the Crops section can be renamed the same way (blur or Enter). The crops table and any rich-text embed URLs stay in sync.

Page reference fields remain linked automatically because they reference the page ID, not the filename. Any MediaHub images embedded in rich text (TinyMCE) fields are also updated automatically via the data-mediahub-id rename tracking system. See Rich Text Integration for details.

Usage tracking

The Usage section lists where this asset appears on your site. Each row shows the page title, URL, field name, and template, with links to open the page in the admin editor or visit the live page.

MediaHub records two kinds of placement:

  • Page fields — the asset (or one of its crops) is selected in a field on a content page, such as a gallery or hero image.
  • Rich text — the asset was inserted with Insert from Media Hub in the editor.

The library sidebar’s Unused filter uses this same information: if Usage shows at least one row, the asset will not appear under Unused. See The Admin → Library sidebar → Unused for a fuller explanation.

References in template code, Hanna Code, or hand-written HTML are not listed here unless the asset was also added through a field or through Insert from Media Hub in the editor.

Last updated