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 header strip shows stat cubes for file format, size, dimensions (images), crop count, and usage count. Below that:

  • Preview - full image preview for images; file icon for documents, audio, or video
  • 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
  • Usage - every ProcessWire page that references this asset, with links to edit or view
  • Metadata sidebar - edit the asset's title, alt text (images only), About note, tags, and collections

Actions

The Actions panel in the sidebar provides:

  • Crop image - opens the crop editor (images only). See Image Cropping.
  • 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 (with confirmation)

Renaming a file

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

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 every page that references this asset via a ProcessWire page reference field. 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.

Usage is only tracked for assets added to pages via ProcessWire fields. References embedded directly in template code or rich text are not tracked.