Jump to content

Media Manager


Recommended Posts

1 hour ago, Rudy said:

I am using Reno theme with Lightwire CK Editor theme. The MMImage and MMLink icons did not appear (see screenshot)

AFAIK it's a CSS issue, the LightWire theme hides the original icons and replaces them with its own icons, but unfortunately it hasn't got icons for third party plugins. To display them, use !important for the icons, at least that's why I've done in AdminOnSteroids module.

  • Like 2
Link to comment
Share on other sites



When I change the code from the WireUpload::validateFilename method like this, it doesn't add any underscores more:

//$value = $this->wire('sanitizer')->filename($value, Sanitizer::translate); 
$value = $this->wire('sanitizer')->filename($value); // removing Sanitizer::translate

But I don't know how big this affects other code areas of ProcessWire. Do you know an other way how i could turn off adding of underscores to the filename?

Link to comment
Share on other sites


Changing core files is never recommended. Have you tried to play around with the settings in the module InputfieldPageName as stated in the $sanitizer docs (please see below)? Does that help? That core module is found at /your-pw-admin/module/edit?name=InputfieldPageName


$beautify (optional) bool or int

Should be true when creating a file's name for the first time. Default is false. You may also specify Sanitizer::translate (or number 2) for the $beautify param, which will make it translate letters based on the InputfieldPageName custom config settings.



Link to comment
Share on other sites


Somehow the InputfieldPageName settings doesn't have any effect on the filename of images (i changed "ö=o" to "ö=owww" to test and it only affected the pagename when creating new pages). Perhaps I should start a new topic since this isn't a Media Manager issue furthermore it is a pw-general issue (I know it isn't really an issue since its just validating the filename, but it still adds underscores when using umlauts, which i think is a issue, since it is nowhere declared how i can change this behavior) . Sorry for hijacking this thread Mate. But still thanks for your help @kongondo. :)

Link to comment
Share on other sites

  • 2 weeks later...

Hi @kongondo

I have a couple of Questions:

1. Is it possible to save the filter interface configuration (like in ListerPro)?

2. Filtering tags by words (it should ignore the order) doesn't work as expected.

I have this image with the following tags: Eintritt Formular Event

Bildschirmfoto 2016-10-26 um 11.18.39 3.png

But when I try to filter with "Contains Words" it doesnt't work as expected, it doesn't find anything.


So I tried it also to search with the listerpro and there I get this error:


Do you have any ideas why this doesn't work?

Link to comment
Share on other sites

I tried the Lister Pro 1.0.8 with Media Manager 0.0.6 on localhost on a fresh install. It works well with the "contains words" option. Looks like it's a issue from some code snippets(hooks etc..) I wrote. I will search through the code to look if I find something which causes this problem.  Sorry for blowing up the thread @kongondo...

Link to comment
Share on other sites

Hi everyone,

Is the module compatible with PW 3.x ? I tried to update an installation yesterday but it all broke down :) The noticed the files in the module had been deleted! (one of the errors said it couldn't find a module file). Tried to reinstall de module, but had no effect. Sorry I didn't bring the complete error log, I did it in a production site so I had to restore quickly.

Thanks for the great support!

Link to comment
Share on other sites



1. Is it possible to save the filter interface configuration (like in ListerPro)?

No it's not. But the filter should remember the filters you set up last. The filter interface as it is is generated by a core module InputfieldSelector (even in ListerPro). Saving the configuration bit is something extra ListerPro does and Media Manager doesn't.

2. Filtering tags by words (it should ignore the order) doesn't work as expected.

I have experienced some weirdness myself but I probably have an older version of InputfieldSelector. The 'OR' filter has not been working for me, i.e. find image media or document media or video media tagged as 'travel'. It is something am looking into and thanks for raising this.


Is the module compatible with PW 3.x ?

Officially, not yet although some people have been using MM in PW 3 without any issues, certainly not files being deleted ???. I am currently working through a requests queue after which I will deal with compatibility issues


I was hoping to release the version 7 of MM by next week but there have been delays (external factors, etc) so there will be a bit of a delay am afraid, sorry. Just to remind you what I am working on:

  1. Multi-tagging (and bulk removal of tags as well
  2. Media replacement (part of a setting on what to do when MM detects a duplicate media is being uploaded )
  3. Sorting media by tags (and sort order)
  4. Uploading of media via the CKEditor plugins
  5. Bug where CKEditor plugin MMLink is conflicting with PWLink (e.g. takes over double click)
  6. List view of media (especially useful when dealing with documents with long file names)
  7. A couple of other enhancements (including CSS Fixes)


  • Like 4
Link to comment
Share on other sites

On 28/10/2016 at 5:52 PM, Rudy said:

Looking forward to version 7 @kongondo! Uploading from CKEditor would be sweet. 

Are you able to fix the CKEditor buttons issue when used with Reno/Lightwire theme as well? Looks like the css fix is pretty straight forward.



Yep, that too :)...edited post above, thanks..

Link to comment
Share on other sites

Great module from what I could see in the videos. Definitely something I want to use in my upcoming projects.

Only one question regarding the handling and output of images

Is there a way to make any kind of pre-defined crop-settings (like in the Croppable Image 3 module) or something like the focus area from the (unsurpassedly useful but unfortunately not PW 3 compatible) ImageFocusArea module available with Media Manager?

Why I ask

In my websites I use responsive images wherever possible, usually using the picture element because I often need its art direction feature.

So my workflow in PW 2.x was:

  1. Use the ImageFocusArea module’s input field to upload an image.
  2. Define the important region (= “focus”) of the image which must be fully visible in all cropped image variations.
  3. Have ProcessWire create all required sizes of all required image variations directly from the original image using the image sizing options (extended by the ImageFocusArea module) in the template files.

The two big pros of this workflow were that the user only had to define the important area of the image once – and was not bothered with any cropping settings (like finding a good-looking image section for an extremely wide horizontal format) – and that all required variations and sizes (I usually use about 10 different images per picture element) were created directly from the original image (which ensures best quality because no unnecessary compression steps were included).

In PW 3.x I had to change this due to the new image field which makes the ImageFocusArea module incompatible with PW 3:

  1. Use the Croppable Image 3 module’s input field to upload an image.
  2. Use the input field’s settings to define the biggest (in pixels) version of each required aspect ratio variation of the image.
  3. Let the user define the best looking image sections for the different crop variations (let’s say we need a 2:1 aspect ratio version and a 4:3 aspect ratio version of the image for one picture element).
  4. Have ProcessWire create the required downscaled versions of the “source images” (i. e. the variants created using the pre-defined crop settings of the Croppable Image input field) using the standard image sizing options in the template files.

While it works, the two big cons here are that the user has to define the different aspect ratio variations manually (assuming that the automatically created default cropping around the image’s center isn’t the best-looking option) and that the downscaled variations of each aspect ratio variations are created from an already processed image (so this includes at least one unnecessary compression step). And of course changing aspect ratio variations later (because of a website layout revision) can result in a lot of manual work to adapt cropped image variations.

What would really be a great extension for Media Manager in my opinion

It would be great if the ImageFocusArea module’s functionality would be available in Media Manager under PW 3. This would make using different image variations a no-brainer – without the website editor having to know anything about image variations, aspect ratios, sizes, cropping, etc.:

  1. The website editor uploads an image in Media Manager.
  2. The website editor defines the important area of the image which may never be cut away.
  3. The website editor selects the image on the respective page using Media Manager’s input field.
  4. That’s it. The template files take care of the rest. And even if the website layout completely changes the selected image needs not to be touched, since all required image variations are created from the original, centrally available image, making sure that the image’s main motive is always presented in the best possible way.

Of course, when inserted into a CKEditor field, the editor can apply an individual cropping if desired.

Unfortunately I’m not a backend developer at all. So I can’t make any code suggestions on how to make this work.

  • Like 1
Link to comment
Share on other sites

52 minutes ago, Rudy said:

@kongondo, is the Add Media link supposed to open in a modal window rather than opening to its own page?  

On mine, it opens to a new page. I have to click on the back button to go back to the entry page.

Should be modal...that's strange. Any JS errors? PW version?

Link to comment
Share on other sites


No it's not. But the filter should remember the filters you set up last. The filter interface as it is is generated by a core module InputfieldSelector (even in ListerPro). Saving the configuration bit is something extra ListerPro does and Media Manager doesn't.

Would it be possible to integrate this config saving feature also in the Media Manager? It would be a very nice addition to it and it would very speed up the workflow of the users.

Link to comment
Share on other sites

@Rudy. Hmm, not sure that's it though. I have been having a pesky JS 'uncaught' error in MM that I haven't been able to catch myself! :) I don't know what it's about. What version of ProcessWire is that? No changed files? 

@Nukro. I'll have a think about that request.

@Michael van Laar. Thanks for your interest in MM. You got some cool ideas there ^-^. However, MM itself is not a media editor and there are no plans to make it one:). Unfortunately, I have never used Croppable Image 3 nor ImageFocusArea. I really have no idea how they work and/if how they could be integrated into MM. I'll try to put aside some time to look into this further, but I can't promise when, unfortunately. If such an extension ever came to light, at this point in time, it looks like it would have to be its own module, packaged and sold or distributed separately from MM.

  • Like 2
Link to comment
Share on other sites

2 hours ago, kongondo said:

However, MM itself is not a media editor and there are no plans to make it one.

I know, images differ from the other media types a little bit.

As an alternative to the above described I could think of input field types which work like Croppable Image 3 or ImageFocusArea, but use a Media Manager image instead of a directly uploaded image. I know this is not something which can be done with Media Manager itself. It would rather be a concept of being able not just to extend the standard image field but to extend a king of “remote image” fieldtype the same way. But I think this would have to be in the core, so that every module which extends or uses the standard (direct upload) image field could use this “get an image from Media Manager and apply the module’s magic to it” image field.

  • Like 1
Link to comment
Share on other sites

Downgraded my site to 2.8.35 and still experienced the issue. A note, the MediaManager field is called inside a repeater, if that makes any different.

Update: Tested MediaManager on its own (without repeater) and the modal window works fine.

Edited by Rudy
Added more info
Link to comment
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 LuisM
      Symprowire is a PHP MVC Framework based and built on Symfony using ProcessWire 3.x as DBAL and Service-Provider
      It acts as a Drop-In Replacement Module to handle the Request/Response outside the ProcessWire Admin. Even tough Symfony or any other mature MVC Framework could be intimidating at first, Symprowire tries to abstract Configuration and Symfony Internals away as much as possible to give you a quick start and lift the heavy work for you.
      The main Goal is to give an easy path to follow an MVC Approach during development with ProcessWire and open up the available eco-system.
      You can find the GitHub Repo and more Information here: https://github.com/Luis85/symprowire
      The Symprowire Wiki https://github.com/Luis85/symprowire/wiki How to create a simple Blog with Symprowire https://github.com/Luis85/symprowire/wiki/Symprowire-Blog-Tutorial Last Update
      16.07.2021 // RC 1 v0.6.0 centralized ProcessWire access trough out the Application by wrapping to a Service https://github.com/Luis85/symprowire/releases/tag/v0.6.0-rc-1 Requirements
      PHP ^7.4 Fresh ProcessWire ^3.0.181 with a Blank Profile Composer 2 (v1 should work, not recommended) The usual Symfony Requirements Features
      Twig Dependency Injection Monolog for Symprowire Support for .env YAML Configuration Symfony Console and Console Commands Symfony Webprofiler Full ProcessWire access inside your Controller and Services Webpack Encore support Caveats
      Symfony is no small Framework and will come with a price in terms of Memory Usage and added Overhead. To give you a taste I installed Tracy Debugger alongside to compare ProcessWire profiling with the included Symfony Webprofiler

      So in a fresh install Symprowire would atleast add another 2MB of Memory usage and around 40ms in response time, should be less in production due to the added overhead of the Webprofiler in dev env
    • By FireWire
      Hello community!

      I want to share a new module I've been working on that I think could be a big boost for multi-language ProcessWire sites.

      Some background, I was looking for a way for our company website to be efficiently translated as working with human translators was pretty laborious and a lack of updating content created a divergence between languages. I, and several other devs here, have talked about translation integrations and have recognized the power that DeepL has. DeepL is an AI deep learning powered service that delivers translation quality beyond any automated service available. After access to the API was opened up to the US, I built Fluency, a DeepL translation integration for ProcessWire.
      Fluency brings automated translation to every multi-language field in the admin, and also provides a translation tool allowing the user to translate their text to any language without it being inside a template's field. With Fluency you can:
      Translate any plain textarea or text input Translate any CKEditor content (yes, with markup) Translate page names for fully localized URLs on every page Translate your in-template translation function wrapped strings Translate modules Fluency is free, and now so is DeepL
      Since this module was first built DeepL has introduced free Developer accounts that allow anyone to start using Fluency at zero cost and beginning with the version 0.3.0 release Fluency now supports free DeepL accounts. As of June 2021 DeepL supports translation to 26 languages and continues to offer more!
      Installation and usage is completely plug and play. Whether you're building a new multi-language site, need to update a site to multi-language, or simply want to stop manually translating a site and make any language a one-click deal, it could not be easier to do it. Fluency works by having you match the languages configured in ProcessWIre to DeepL's. You can have your site translating to any or all of the languages DeepL translates to in minutes (quite literally).
      Let's break out the screenshots...
      When the default language tab is shown, a message is displayed to let users know that translation is available. Clicking on each tab shows a link that says "Translate from English". Clicking it shows an animated overlay with the word "Translating..." cycling through each language and a light gradient shift. Have a CKEditor field? All good. Fluency will translated it and use DeepL's ability to translate text within HTML tags. CKEditor fields can be translated as easily and accurately as text/textarea fields.

      Repeaters and AJAX created fields also have translation enabled thanks to a JavaScript MutationObserver that searches for multi-language fields and adds translation as they're inserted into the DOM. If there's a multi-language field on the page, it will have translation added.

      Same goes for image description fields. Multi-language SEO friendly images are good to go.

      Creating a new page from one of your templates? Translate your title, and also translate your page name for native language URLs. (Not available for Russian, Chinese, or Japanese languages due to URL limitations). These can be changed in the "Settings" tab for any page as well so whether you're translating new pages or existing pages, you control the URLs everywhere.

      Language configuration pages are no different. Translate the names of your languages and search for both Site Translation Files (including all of your modules)

      Translate all of the static text in your templates as well. Notice that the placeholders are retained. DeepL is pretty good at recognizing and keeping non-translatable strings like that. If it is changed, it's easy to fix manually.

      Fluency adds a "Translate" item to the CMS header. When clicked this opens up a modal with a full translation tool that lets the user translate any language to any language. No need to leave the admin if you need to translate content from a secondary language back to the default ProcessWire language. There is also a button to get the current API usage statistics. DeepL account owners can set billing limitations via character count to control costs. This may help larger sites or sites being retrofitted keep an eye on their usage. Fluency can be used by users having roles given the fluency-translate permission.

      It couldn't be easier to add Fluency to your new or existing website. Simply add your API key and you're shown what languages are currently available for translation from/to as provided by DeepL. This list and all configuration options are taken live from the API so when DeepL releases new languages you can add them to your site without any work. No module updates, just an easy configuration. Just match the language you configured in ProcessWire to the DeepL language you want it to be associated with and you're done. Fluency also allows you to create a list of words/phrases that will not be translated which can prevent items such as brands and company names from being translated when they shouldn't

      No "translate page" - Translating multiple fields can be done by clicking multiple translation links on multiple fields at once but engineering a "one click page translate" is not feasible from a user experience standpoint. The time it takes to translate one field can be a second or two, but cumulatively that may take much longer (CKEditor fields are slower than plain text fields). There may be a workaround in the future but it isn't currently on the roadmap. No "translate site" - Same thing goes for translating an entire website at once. It would be great, but it would be a very intense process and take a very (very) long time. There may be a workaround in the future but it isn't on the roadmap. No current support for Inline CKEditor fields - Handling for CKEditor on-demand hasn't been implemented yet, this is planned for a future release though and can be done. I just forgot about it because I've never really used that feature personally.. Alpha release - This module is in alpha. Releases should be stable and usable, but there may be edge case issues. Test the module thoroughly and please report any bugs via a Github issue on the repository or respond here. Please note that the browser plugin for Grammarly conflicts with Fluency (as it does with many web applications). To address this issue it is recommended that you disable Grammarly when using Fluency, or open the admin to edit pages in a private window where Grammarly may not be loaded. This is an issue that may not have a resolution as creating a workaround may not be possible. If you have insight as to how this may be solved please visit the Github page and file a bugfix ticket.
      ProcessWire  3.0+ UIKit Admin Theme That's Fluency in a nutshell. A core effort in this module is to create it so that there is nothing DeepL related hard-coded in that would require updating it when DeepL offers new languages. I would like this to be a future-friendly module that doesn't require developer work to keep it up-to-date.
      The Module Is Free
      This is my first real module and I want to give it back to the community as thanks. This is the best CMS I've worked with (thank you Ryan & contributors) and a great community (thank you dear reader).
      DeepL Developer Accounts
      In addition to paid Pro Developer accounts, DeepL now offers no-cost free accounts. Now all ProcessWire developers and users can use Fluency at no cost.
      Learn more about free and paid accounts by visiting the DeepL website. Sign up for a Developer account, get an API key, and start using Fluency today.
      Download & Feedback
      Download the latest version here
      Github repository:
      File issues and feature requests here (your feedback and testing is greatly appreciated):
      Thank you! ¡Gracias! Ich danke Ihnen! Merci! Obrigado! Grazie! Dank u wel! Dziękuję! Спасибо! ありがとうございます! 谢谢你!

    • By tcnet
      PageViewStatistic for ProcessWire is a module to log page visits of the CMS. The records including some basic information like IP-address, browser, operating system, requested page and originate page. Please note that this module doesn't claim to be the best or most accurate.
      One of the biggest advantage is that this module doesn't require any external service like Google Analytics or similar. You don't have to modify your templates either. There is also no Javascript or image required.
      There is only one disadvantage. This module doesn't record visits if the browser loads the page from its browser cache. To prevent the browser from loading the page from its cache, add the following meta tags to the header of your page:
      <meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate" /> <meta http-equiv="Pragma" content="no-cache" /> <meta http-equiv="Expires" content="0" /> How to use
      The records can be accessed via the Setup-menu of the CMS backend. The first dropdown control changes the view mode.

      Detailed records
      View mode "Detailed records" shows all visits of the selected day individually with IP-address, browser, operating system, requested page and originate page. Click the update button to see new added records.

      Cached visitor records
      View modes other than "Detailed records" are cached visitor counts which will be collected on a daily basis from the detailed records. This procedure ensures a faster display even with a large number of data records. Another advantage is that the detailed records can be deleted while the cache remains. The cache can be updated manually or automatically in a specified time period. Multiple visits from the same IP address on the same day are counted as a single visitor.

      Upgrade from older versions
      Cached visitor counts is new in version 1.0.8. If you just upgraded from an older version you might expire a delay or even an error 500 if you display cached visitor counts. The reason for this is that the cache has to be created from the records. This can take longer if your database contains many records. Sometimes it might hit the maximally execution time. Don't worry about that and keep reloading the page until the cache is completely created.
      Special Feature
      PageViewStatistic for ProcessWire can record the time a visitor viewed the page. This feature is deactivated by default. To activate open the module configuration page and activate "Record view time". If activated you will find a new column "S." in the records which means the time of view in seconds. With every page request, a Javascript code is inserted directly after the <body> tag. Every time the visitor switches to another tab or closes the tab, this script reports the number of seconds the tab was visible. The initial page request is recorded only as a hyphen (-).

      New in version 1.1.0
      A new feature comes with version 1.1.0 which offers to record user names of loggedin visitors. Just activate "Record user names" and "Record loggedin user" in the module settings.
      You can access the module settings by clicking the Configuration button at the bottom of the records page. The settings page is also available in the menu: Modules->Configure->ProcessPageViewStat.
      This module uses the IP2Location database from: http://www.ip2location.com. This database is required to obtain the country from the IP address. IP2Location updates this database at the begin of every month. The settings of ProcessPageViewStat offers the ability to automatically download the database monthly. Please note, that automatically download will not work if your webspace doesn't allow allow_url_fopen.
      This module uses DragScroll. A JavaScript available from: http://github.com/asvd/dragscroll. Dragscroll adds the ability in view mode "Day" to drag the records horizontally with the mouse pointer.
      This module uses the PHP class parseUserAgentStringClass available from: http://www.toms-world.org/blog/parseuseragentstring/. This class is required to filter out the browser type and operating system from the server request.
    • By clsource
      Inertia Adapter ProcessWire Module
      Hello! Long time no see.
      I created this module so you can use Inertia.js (https://inertiajs.com/) with ProcessWire.
      Inertia allows you to create fully client-side rendered, single-page apps, without much of the complexity that comes with modern SPAs. It does this by leveraging existing server-side frameworks.
      Inertia isn’t a framework, nor is it a replacement to your existing server-side or client-side frameworks. Rather, it’s designed to work with them. Think of Inertia as glue that connects the two. Inertia comes with three official client-side adapters (React, Vue, and Svelte).
      This is an adapter for ProcessWire. Inertia replaces PHP views altogether by returning JavaScript components from controller actions. Those components can be built with your frontend framework of choice.
      - https://github.com/joyofpw/inertia
      - https://github.com/joyofpw/inertia-svelte-mix-pw
      - https://inertiajs.com/

    • By sms77io
      Hi all,
      we made a small module for sending SMS via Sms77.io. It supports sending to one and multiple users.
      You can download it from GitHub and follow the instructions on how to install it - it is quite easy. An API key is required for sending, get yours for free @ Sms77 and receive 0,50 €.
      Hope this helps somebody and we are open for improvement suggestions!
      Best regards
  • Create New...