Jump to content

Media Manager


Recommended Posts

Media Manager
Released 31 March 2016



As of 10 May 2019 ProcessWire versions earlier than 3.x are not supported

*******************************************************   ORIGINAL POST   *******************************************************

API Example (frontend; will be added to documentation site)

Accessing and outputting the contents of the MediaManager field(s) in your template is quite simple. The fields are accessed like many other ProcessWire fields. The fields return an array of type MediaManagerArray that need to be looped to output each media within. Assuming you created a field of type MediaManager named 'media', you can loop through it for a given page as shown below.

Each MediaManager object has the following 5 basic properties:
DATABASE (saved properties)
1. id => pageID of the page where the media lives (hidden in admin and not important to know about)
2. type => integer denoting media type (1=audio; 2=document; 3=image [for variations this will be 3x, where x is the number of the variation of an original image]; 4=video)
3. typeLabel => user friendly string denoting media type (audio, document, image, video)
4. media => a ProcessWire Image/File Object including all their properties (ext, filesizeStr, height, width, description, tags, filename, basename, etc.)
5. title => title of media (@note: this is the title of the page where the media lives; may or may not be the same as the name of the media file itself). This can be used as a user-friendly name for your media
$media = $page->media;// returns a MediaManagerArray. Needs to be looped through

foreach ($media as $m) {
	echo $m->id;// e.g. 1234 (hidden page in /admin/media-manager/media-parent/)
	echo $m->type;// e.g. 3 (a media of type image) OR 1 (a media of type audio)
	echo $m->typeLabel;// e.g. 'document' (i.e. type would be 2)
	echo $m->title;// e.g. 'My Nice Trip' (whose media file could be my-nice-trip.mp4)
		- $m->media returns an object;
                   either a ProcessWire Image (for image media) or File object (for audio, document and video media)
		- This means you have access to all the properties of that object,
                   e.g. ext, tags, description, url, filename, basename, width, height,
                        modified, created, filesize, filesizeStr, etc
                        as well as associated methods, e.g. size()
	echo $m->media->tags;

// only output images
foreach ($media as $m) {
	if($m->typeLabel =='image') {
		echo "<img src='" . $m->media->size(100,75)->url . "'><br>";

// There's also a toString() method so you can do:
echo $page->media;

All your media will be output wrapped in appropriate HTML tags, i.e.:

	audio: <audio></audio>;
	document: <a></a>;
	image: <img>;
	video: <video></video>;


*******************************************************   ORIGINAL POST   *******************************************************
The topic of a central media manager feature for ProcessWire has come up several times:
More recently, regarding my Visual Page Selector module, I have been asked several times why the module does not have an in-built feature to upload images.
There's two camps on the topic of a central media manager: those who like them (especially those coming in to PW from other CMSes) and those who don't like them (primarily because of the chaotic way some CMSes (dis)organise their media management) :-). I think that we can have our cake and eat it too! If done the right way, closely following the principles of and harnessing the power of ProcessWire, we can have a well-implemented, organised, feature-rich, site-wide media manager.
Introducing Media Manager: (a commercial module)
Alongside a number of modules I am currently working on (both free and commercial), I have been developing  a centralised Media Manager for ProcessWire. Before you cast the first stone, no, this is not going to be a one-large-media-bucket as in other CMS where it gets very messy very quickly :). In the backend things are neatly stored away, yes, in pages. However, those are pages you will not see (just like repeater pages). Before anyone has a go at pages, remember a page is not that thing you see on the ProcessWire Tree (that's just its visual representation); A page is a record/row in the database  :P  ;). For the end-user of Media Manager, all they will see is the 'familiar media bucket' to select their media from. As long as it works efficiently, I don't think they care about the wizardry behind the scenes :) . 
The module allows for the comprehensive management of several media types:

  • Audio
  • Video
  • Images
  • Documents

Each media type will be handled by its own sub-module so the user can pick and install/choose the type of media management they want.
Features include:

  • Access controls
  • Centralized uploads of media
  • Bulk management of media: tag, delete, describe, replace, etc.
  • Bulk upload: zip; scan, single
  • Quick upload in page edit mode
  • Usage stats across pages (maybe?)
  • Etc..

Would love to hear your thoughts and any feature suggestions. I think there's enough demand for such a module. If not, please let me know so that I can instead focus on other things  :lol:, thanks.
How other CMS do it
The more efficient (PW) way of doing it

Edited by kongondo
added link to documentation; PW 3 support only
  • Like 20
Link to comment
Share on other sites

Definitely going to keep my eye on this - fantastic idea! One of my current issues with file uploads is that they expose a certain directory structure. As much as PW is protected from that, I prefer file URIs to be a little more 'process' oriented - hence one of the reasons I created little Dispo.

(Speaking of Pages as records, I've been meaning to discuss the possible storage-switch from DB to Pages for Jumplinks when I rewrite... Perhaps that would make it a lot more flexible...)

  • Like 1
Link to comment
Share on other sites

  • 3 weeks later...
  • 3 weeks later...

So here is a wild and possibly silly question, have you put thought in to media preview for documents and audio files? If I have a pile of audio files in a folder I think it would be the bees knees to be able to hit preview or something with a little ajax player...

  • Like 1
Link to comment
Share on other sites

So here is a wild and possibly silly question, have you put thought in to media preview for documents and audio files? If I have a pile of audio files in a folder I think it would be the bees knees to be able to hit preview or something with a little ajax player...

Not wild not silly... Yes, you are covered :-)...but currently only audio + video. Documents are trickier, except for PDF. Still mulling using a different jQuery plugin vs fancybox?

Link to comment
Share on other sites

Drag and drop to sort or to upload? Both are already implemented :-)

Man you are a boss! What about google drive / dropbox uploading ;) now I'm just being difficult. Seriously though, this is going to be super useful. I can think of a musician I know that I'm going to be building a site for and I was really wanting to handle his content this way. 

Link to comment
Share on other sites

Very good idea for the module! I like the concept, and in the end also for the end user easier to understand than him unlearn habits. Absolutely helpful would be an own InputField. So you can add assets not only in the text editor, but also the template. Either select from the Library, replace a selected asset or a new upload. Just like the current file InputField, but just connected to the module. Thank you for doing the work. I look forward to the module.

  • Like 3
Link to comment
Share on other sites


The module consists of 3 modules: A Process module, a Fieldtype and, you guessed it, an own Inputfield :-). The Inputfield is what you see in the first and second screenshots above. 

Haha okay. Right. Sometimes you can not see the forest for the trees.  :frantics:  :biggrin:

Link to comment
Share on other sites

  • 4 weeks later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Similar Content

    • By Sebi
      AppApiFile adds the /file endpoint to the AppApi routes definition. Makes it possible to query files via the api. 
      This module relies on the base module AppApi, which must be installed before AppApiFile can do its work.
      You can access all files that are uploaded at any ProcessWire page. Call api/file/route/in/pagetree?file=test.jpg to access a page via its route in the page tree. Alternatively you can call api/file/4242?file=test.jpg (e.g.,) to access a page by its id. The module will make sure that the page is accessible by the active user.
      The GET-param "file" defines the basename of the file which you want to get.
      The following GET-params (optional) can be used to manipulate an image:
      width height maxwidth maxheight cropX cropY Use GET-Param format=base64 to receive the file in base64 format.
    • By MarkE
      This fieldtype and inputfield bundle was built for storing measurement values within a field, rendering them in a variety of formats and converting them to other units or otherwise modifying them via the API.
      The API consists of a number of predefined functions, some of which include...
      render() for rendering the measurement object, valueAs() for converting the value to another unit value, convertTo() for converting the whole measurement object to different units, and add() and subtract() for for modifying the stored value by the value (converted as required) in another measurement. In the admin the inputfield includes a checkbox (which can be optionally disabled) for converting values on page save. For an example if a value was typed in as centimeters, the unit was changed to metres, and the page saved with this checkbox selected, said value would be automatically converted so that e.g. 170 cm becomes 1.7 m.

      A simple length field using Fieldtype Measurement and Inputfield Measurement.
      Combination units (e.g. feet and inches) are also supported.
      Please note that this module is 'proof of concept' at the moment - there are limited units available and quite a lot of code tidying to do. More units will be added shortly.
      See the GitHub at https://github.com/MetaTunes/FieldtypeMeasurement for full details and updates.
    • By tcnet
      File Manager for ProcessWire is a module to manager files and folders from the CMS backend. It supports creating, deleting, renaming, packing, unpacking, uploading, downloading and editing of files and folders. The integrated code editor ACE supports highlighting of all common programming languages.

      This module is probably the most powerful module. You might destroy your processwire installation if you don't exactly know what you doing. Be careful and use it at your own risk!
      ACE code editor
      This module uses ACE code editor available from: https://github.com/ajaxorg/ace

      This module uses the JavaScript dragscroll available from: http://github.com/asvd/dragscroll. Dragscroll adds the ability to drag the table horizontally with the mouse pointer.
      PHP File Manager
      This module uses a modified version of PHP File Manager available from: https://github.com/alexantr/filemanager
    • By tcnet
      This module implements the website live chat service from tawk.to. Actually the module doesn't have to do much. It just need to inserted a few lines of JavaScript just before the closing body tag </body> on each side. However, the module offers additional options to display the widget only on certain pages.
      Create an account
      Visit https://www.tawk.to and create an account. It's free! At some point you will reach a page where you can copy the required JavaScript-code.

      Open the module settings and paste the JavaScript-code into the field as shown below. Click "Submit" and that's all.

      Open the module settings
      The settings for this module are located int the menu Modules=>Configure=>LiveChatTawkTo.

    • By tcnet
      Session Viewer is a module for ProcessWire to list session files and display session data. This module is helpful to display the session data of a specific session or to kick out a logged in user by simply delete his session file. After installation the module is available in the Setup menu.

      The following conditions must be met for the module to work properly:
      Session files
      Session data must be stored in session files, which is the default way in ProcessWire. Sessions stored in the database are not supported by this module. The path to the directory where the session files are stored must be declared in the ProcessWire configuration which is by default: site/assets/sessions.
      Serialize handler
      In order to transform session data easier back to a PHP array, the session data is stored serialized. PHP offers a way to declare a custom serialize handler. This module supports only the default serialize handlers: php, php_binary and php_serialize. WDDX was dropped in PHP 7.4.0 and is therefore not supported by this module as well as any other custom serialize handler. Which serialize handler is actually used you can find out in the module configuration which is available under Modules=>Configure=>SessionViewer.

      Session data
      The session data can be displayed in two different ways. PHP's default output for arrays print_r() or by default for this module nice_r() offered on github: https://github.com/uuf6429/nice_r. There is a setting in the module configuration if someone prefers print_r(). Apart from the better handling and overview of the folded session data the output of nice_r() looks indeed nicer.

      ProcessWire module directory
  • Create New...