Jump to content

Recommended Posts

Media Manager
 
Released 31 March 2016
https://processwireshop.pw/plugins/media-manager/

Documentation 

http://mediamanager.kongondo.com/

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.

 
@note:
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)
 
RUNTIME
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)
	/*
		@note: 
		- $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:
 
https://processwire.com/talk/topic/4330-get-image-from-other-pages-via-images-field/
https://processwire.com/talk/topic/4330-get-image-from-other-pages-via-images-field/?p=42578
https://processwire.com/talk/topic/4330-get-image-from-other-pages-via-images-field/?p=42582
https://processwire.com/talk/topic/425-file-manager/
https://processwire.com/talk/topic/425-file-manager/?p=13802
https://processwire.com/talk/topic/425-file-manager/?p=13861
https://processwire.com/talk/topic/10763-asset-manager-asset-selector/
 
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
post-894-0-53440600-1443797542_thumb.png
 
The more efficient (PW) way of doing it
post-894-0-21221700-1443797544_thumb.png

Edited by kongondo
added link to documentation; PW 3 support only
  • Like 20

Share this post


Link to post
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

Share this post


Link to post
Share on other sites

Getting warmer....(OK, so my icons suck, but hey...we're 75% there. :-))..

Page Edit List View

post-894-0-79570600-1449049855_thumb.png

Page Edit Grid View

post-894-0-76137900-1449049859_thumb.png

Page Edit Insert Media

post-894-0-00404300-1449049871_thumb.png

ProcessMediaManager

post-894-0-31466400-1449049861_thumb.png

post-894-0-03749200-1449049866_thumb.png

post-894-0-53330900-1449049867_thumb.png

  • Like 9

Share this post


Link to post
Share on other sites

Don't worry about the icons, have you seen some of those many wordpress plugins?  :P

  • Like 1

Share this post


Link to post
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...

  • Like 1

Share this post


Link to post
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?

Share this post


Link to post
Share on other sites

this looks great kongondo!

have you thought about implementing the blueimp file uploader to it? it has built in preview (at least for mp3 and images) and supports client side image resizing. that's one thing i am missing most when it comes to image galleries!

looking forward to trying this module :)

  • Like 1

Share this post


Link to post
Share on other sites

@BernhardB, yes, I have considered it. Will look further into it, thanks.

  • Like 1

Share this post


Link to post
Share on other sites

hmm yeah, drag and drop would be crazy cool too. Danger scope creep warning :)

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

  • Like 1

Share this post


Link to post
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. 

Share this post


Link to post
Share on other sites

What about google drive / dropbox uploading ;)

Planned for version > 1, maybe 2nd release

  • Like 1

Share this post


Link to post
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

Share this post


Link to post
Share on other sites

@David,

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. 

  • Like 1

Share this post


Link to post
Share on other sites

@David,

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:

Share this post


Link to post
Share on other sites

Not sure what's going on with my previous post. I've deleted it...Will update with short video instead...

  • Like 1

Share this post


Link to post
Share on other sites

Video clip showing latest development...(note: previews of other types other than images are still a work in progress...)

  • Like 21

Share this post


Link to post
Share on other sites

DAM it ;-)

I love this. 

This modules makes ProcessWire a respectable Digital Asset Management.

Great job kongondo

  • Like 1

Share this post


Link to post
Share on other sites

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 MoritzLost
      TrelloWire
      This is a module that allows you to automatically create Trello cards for ProcessWire pages and update them when the pages are updated. This allows you to setup connected workflows. Card properties and change handling behaviour can be customized through the extensive module configuration. Every action the module performs is hookable, so you can modify when and how cards are created as much as you need to. The module also contains an API-component that makes it easy to make requests to the Trello API and build your own connected ProcessWire-Trello workflows.
      Features
      All the things the module can do for you without any custom code: Create a new card on Trello whenever a page is added or published (you can select applicable templates). Configure the target board, target list, name and description for new cards. Add default labels and checklists to the card. Update the card whenever the page is updated (optional). When the status of the card changes (published / unpublished, hidden / unhidden, trashed / restored or deleted), move the card to a different list or archive or delete it (configurable). You can extend this through hooks in many ways: Modifiy when and how cards are created. Modify the card properties (Target board & list, title, description, et c.) before they are sent to Trello. Create your own workflows by utilizing an API helper class with many convenient utility methods to access the Trello API directly. Feedback & Future Plans
      Let me know what you think! In particular:
      If you find any bugs report them here or on Github, I'll try to fix them. This module was born out of a use-case for a client project where we manage new form submissions through Trello. I'm not sure how many use-cases there are for this module. If you do use it, tell me about it! The Trello API is pretty extensive, I'll try to add some more helper methods to the TrelloWireApi class (let me know if you need anything in particular). I'll think about how the module can support different workflows that include Twig – talk to me if you have a use-case! Next steps could be a dashboard to manage pages that are connected to a Trello card, or a new section in the settings tab to manage the Trello connection. But it depends on whether there is any interest in this 🙂 Links
      Repository on Github Complete module documentation (getting started, configuration & API documentation) TrelloWire in the modules directory Module configuration

    • By Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-04-06 -- SnipWire 0.8.6 (beta) released! Adds support for Snipcart subscriptions and also fixes some problems 2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By bernhard
      #######################
      Please use the new RockFinder2
      #######################
      WHY?
      This module was built to fill the gap between simple $pages->find() operations and complex SQL queries.
      The problem with $pages->find() is that it loads all pages into memory and that can be a problem when querying multiple thousands of pages. Even $pages->findMany() loads all pages into memory and therefore is a lot slower than regular SQL.
      The problem with SQL on the other hand is, that the queries are quite complex to build. All fields are separate tables, some repeatable fields use multiple rows for their content that belong to only one single page, you always need to check for the page status (which is not necessary on regular find() operations and therefore nobody is used to that).
      In short: It is far too much work to efficiently and easily get an array of data based on PW pages and fields and I need that a lot for my RockGrid module to build all kinds of tabular data.

      Basic Usage

       
      Docs & Download
      https://modules.processwire.com/modules/rock-finder/
      https://github.com/BernhardBaumrock/RockFinder
       
      Changelog
      180817, v1.0.6, support for joining multiple finders 180810, v1.0.5, basic support for options fields 180528, v1.0.4, add custom select statement option 180516, change sql query method, bump version to 1.0.0 180515, multilang bugfix 180513, beta release <180513, preview/discussion took place here: https://processwire.com/talk/topic/18983-rocksqlfinder-highly-efficient-and-flexible-sql-finder-module/
    • By MoritzLost
      Process Cache Control
      This module provides a simple solution to clearing all your cache layers at once, and an extensible interface to perform various cache-related actions.
      The simple motivation behind this module was that I was tired of manually clearing caches in several places after deploying a change on a live site. The basic purpose of this module is a simple Clear all caches link in the Setup menu which clears out all caches, no matter where they hide. You can customize what exactly the module does through it's configuration menu:
      Expire or delete all cache entries in the database, or selectively clear caches by namespace ($cache API) Clear the the template render cache. Clear out specific folders inside your site's cache directory (/site/assets/cache) Clear the ProCache page render cache (if your site is using ProCache) Refresh version strings for static assets to bust client-side browser caches (this requires some setup, see the full documentation for details). This is the basic function of the module. However, you can also add different cache management action through the API and execute them through the module's interface. For this advanced usage, the module provides:
      An interface to see all available cache actions and execute them. A system log and logging output on the module page to see verify what the module is doing. A CacheControlTools class with utility functions to clear out different caches. An API to add cache actions, execute them programmatically and even modify the default action. Permission management, allowing you granular control over which user roles can execute which actions. The complete documentation can be found in the module's README.
      Plans for improvements
      If there is some interest in this, I plan to expand this to a more general cache management solution. I particular, I would like to add additional cache actions. Some ideas that came to mind:
      Warming up the template render cache for publicly accessible pages. Removing all active user sessions. Let me know if you have more suggestions!
      Links
      https://github.com/MoritzLost/ProcessCacheControl ProcessCacheControl in the Module directory CHANGELOG in the repository Screenshots


    • By Macrura
      PrevNextTabs Module
      Github: https://github.com/outflux3/PrevNextTabs
      Processwire helper modules for adding page navigation within the editor.
      Overview
      This is a very simple module that adds Previous and Next links inline with the tabs on the page editor. Hovering over the tab shows the title of the previous or next page (using the admin's built in jqueryUI tooltips.)
      Usage
      This module is typically used during development where you or your editors need to traverse through pages for the purpose of proofing, flagging and/or commenting. Rather than returning to the page tree or lister, they can navigate with these links.
      Warnings
      If you are using PW version 2.6.1 or later, the system will prevent you from leaving the page if you have unsaved edits.
      For earlier versions, to avoid accidentally losing changes made to a page that might occur if a user accidentally clicks on one of these, make sure to have the Form Save Reminder module installed.
      http://modules.processwire.com/modules/prev-next-tabs/
×
×
  • Create New...