Jump to content

Media Manager


Recommended Posts


Update is same as any other ProcessWire module. However, in this case, we also have to delete the following folders:

  • /site/modules/InputfieldCKEditor/plugins/mmimage/
  • /site/modules/InputfieldCKEditor/plugins/mmlink/
  • /site/modules/MediaManager/plugins/

In addition, you need to remove references to the the plugins MMImage and MMLink from any CKEditor field that were using them.

  • Edit the field
  • Go to Input Tab
  • Under CKEditor Settings > CKEditor Toolbar delete references to MMImage and MMLink
  • Scroll down to Plugins and untick mmimage and mmlink
  • Save

The update does not write anything; neither to your file system nor to your database. Therefore, it shouldn't affect anything related or unrelated. Better to be safe always, however, so, create a backup of your site first

  • Backup your files and db
  • replace or overwrite the contents of /site/modules/MediaManager/ with the contents of the folder MediaManager-007. If overwriting, remember to delete the plugins folders as stated above since there will be nothing to overwrite them with from the MediaManager-007 folder
  • Hit module refresh
  • Test that everything works fine
  • Acquaint yourself with the latest changes
  • Let your clients know about the changes :-)
  • Like 2
Link to comment
Share on other sites

It should stay there if you are on list view and have a long list. That way you always have the edit panel in view rather than scrolling back up. When you scroll back up it should go back to the normal position. Please see the gif I posted earlier..

Link to comment
Share on other sites

5 minutes ago, kongondo said:

It should stay there if you are on list view and have a long list. That way you always have the edit panel in view rather than scrolling back up. When you scroll back up it should go back to the normal position. Please see the gif I posted earlier..

Possibly I explained it not good enough sry for that. Yeah I understand/know that the image jumps to the top when scrolling so that I can see the image always. But when I go up again the image still has the fixed class. You can see in my previous post, that the image overlaps the search menu...

Link to comment
Share on other sites

29 minutes ago, kongondo said:

Hmm. I had that bug and resolved it in my install. What browser are you using? Or are you on a device?

I'm on my mac. I've tested it on chrome, firefox and safari. The bug is happening in all 3 browsers. I had installed the Module with "Add module from Upload". It created a new folder and changed the old folder to hidden. After that I have updated the media manager and removed the mmplugins from all fields and also from the inputfieldckeditor plugin folder.


EDIT: It's weird. Sometimes it works and sometimes not?   It doesn't work with the images which are very big/long in height (1000px x 2000px). And this behavior also happens only then when the long image was selected first.

Link to comment
Share on other sites

Checked again and it works fine on FF and Chrome in Windows. Wondering if it's a Mac thing? Are you able to test on a Mac machine? 

Anyone else experiencing this? 

Edit: Facepalm! :-[

I should have noted your image dimensions. I forgot to add that to the release notes. For tall images (yours is 2000px high) you will (currently) experience that problem. It has to do with the JS calculating how far the window has been scrolled up in relation to the height of your monitor minus the height of the parent div of the preview/edit panel (the difference). If your image is taller than your monitor, that will result in a negative difference and hence when you scroll back up, the 'fixed' class is not removed. I wasn't able to find a solution before this release but will work on it. Apologies.

  • Like 1
Link to comment
Share on other sites

5 hours ago, Nukro said:

How do I have to update the Media Manager?

For modules not in the modules directory and not on Github I always update by doing: Modules > Site > Add New > Add Modules From Upload

That will also update an existing module. To me that is easier than unzipping and replacing folder.

  • Like 3
Link to comment
Share on other sites

49 minutes ago, Rudy said:

@kongondo, it looks like the modal window repeater bug still exist in 0.0.7.

I would expect it to :P. As per my release notes for version 007, this version is not compatible with PW version 2.8 and 3.x (which are one and the same save for namespacing in the latter). Version 008 of MM will be compatible with those versions of ProcessWire as well as preserve backward compatibility. The repeater bugs were common to these newer versions of ProcessWire and hence will be tackled in the next release. Thanks.

Link to comment
Share on other sites

Hi all. Very minor update (I didn't even change the module version - it stays at 007). I think I've fixed the bug where long images would stay fixed at the top on scroll up in list-view. 

@Nukro, if you don't mind, please download the latest zip file(still MediaManager-007.zip),  test and let me know if this fixes the issue? The only file that needs replacing is ProcessMediaManager.js. Thanks.

  • Like 1
Link to comment
Share on other sites

8 minutes ago, kongondo said:

Hi all. Very minor update (I didn't even change the module version - it stays at 007). I think I've fixed the bug where long images would stay fixed at the top on scroll up in list-view. 

@Nukro, if you don't mind, please download the latest zip file(still MediaManager-007.zip),  test and let me know if this fixes the issue? The only file that needs replacing is ProcessMediaManager.js. Thanks.

Thanks @kongondo it works know :)

  • Like 1
Link to comment
Share on other sites

  • 2 weeks later...

Media Manager version 008  (released 09/12/2016)

Happy to announce the latest release of Media Manager.


  1. Fully compatible with ProcessWire 2.8 and 3.x (@see note #1 below though).
  2. Fully compatible with repeaters including ProcessWire 2.7, 2.8 and 3
  3. Fully compatible with Repeater Matrix
  4. Fixed bug in Media Manager insert-image-in-RTE feature. Please note, there are a some slight UI changes, but nothing major.  Also @see note #2 below.


  1. Maybe it's my environment or the file compiler but in ProcessWire 3.x, if you delete media, they are reported as not deleted until you manually refresh the page
  2. In case you didn't know, you do not have to use FieldtypeMediaManager/InputfieldMediaManager to insert images in the RTE
  3. Please also upgrade to version 004 of Jquery File Upload (uploaded today)
  4. A couple of people are reporting not getting confirmation emails after purchasing MM. I'm looking into this
  • Like 3
Link to comment
Share on other sites

Hi @kongondo

I wanted to ask, how it is going with fixed filters inside the media manager? You had said you would look further into it when you have dispensed the version 7. It is a top priority of my customer since it would pretty simplify the workflow of his workers. It's very important, I would be glad when you could say a period (Version 9 ? ) when you would release such a feature. In the end I wanted to thank you for all you efforts you have put in this respectively in your Product, in my eyes it is a masterpiece of work!

Greetings Orkun 

Link to comment
Share on other sites

14 hours ago, Nukro said:

Hi @kongondo

I wanted to ask, how it is going with fixed filters inside the media manager?

Hi @Nukro,

It is planned for the next version. Technically, I already know how I will implement this. What I am still unsure of is how I will implement the GUI (from a usability point of view). With lister, each lister gets its own fixed filter configurations. With Media Manager, there's only one canvass, so to speak. We will probably need a dedicated page to handle the creation and editing of a filter configuration. Users would need to be able to select the active 'filter' configuration/profile. I would like the whole thing to be a simple thing to do (from user perspective) but without cluttering the MM interface. I'll need some time to think this through.  I would appreciate any thoughts you have, thanks. As for ETA, I am afraid it cannot happen before the new year.

  • Like 2
Link to comment
Share on other sites

Media Manager version 009  (released 16/12/2016)

Happy to announce the latest release of Media Manager.


  1. Filter Profiles: Feature enables configuring of various media filter interfaces (similar to ListerPro). This feature was requested here. Please see otes below

Filter Profiles Usage

  1. To use the so-called Filter Profiles feature, you will first have to enable it in your settings (see images below). 
  2. Head over to any media view. You will see a 'config' tab next to the  Filters tab. Click on it. It will open a modal
  3. Create your profiles (one at a time). These are added to a table in that modal view.
  4. Click on the title of a filter profile to configure it's filters. Moves to 'single filter profile edit view'
  5. Set a filter as active by selecting it in the dropdown at the top of the modal view (#2)
  6. To delete one or more filter profiles, click their trash icon and save (there's a checkbox to confirm action)
  7. Close the modal. The Media Manager Library will reset and if you set an active filter in #5, your Media will be filtered according to your settings

Currently, any user can create filters. Depending on your feedback, this might change. We might also add other features, e.g. locking down filters so they cannot be deleted.

OK, that's it from Media Manager for this year. Hope it's been fun! 







  • Like 4
Link to comment
Share on other sites

  • 3 weeks later...

Hey @kongondo

I think I have encountered an Issue with using the Media Manager with an multi language setup. It looks like the title field is always only filled out in the user language. Let's say I have 2 Languages, english(default) and german. Let's say my user language is german at the moment and I am uploading a new image. Now the default tab of the title of the uploaded image is empty. So when I change the user-language to the default language it won't show any titles in media manager interface since it is empty in the default tab. 

Would it perhaps possible to fillout the default langauge tab of the title field too even my user language is not the default at the moment? When you are adding tags to the image, all language tabs are also filled out. 

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...