Jump to content

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 post
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 post
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 post
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 post
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 post
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 post
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 post
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 post
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 post
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 post
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 post
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 post
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 post
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 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 monollonom
      (once again I was surprised to see a work of mine pop up in the newsletter, this time without even listing the module on PW modules website 😅. Thx @teppo !)
      Github: https://github.com/romaincazier/FieldtypeQRCode
      Modules directory: https://processwire.com/modules/fieldtype-qrcode/
      This is a simple module I made so a client could quickly grab a QR Code of the page's url in the admin.
      There's not much to it for now, but if need be you can output anything using a hook:
      $wire->addHookAfter("FieldtypeQRCode::getQRText", function($event) { $event->return = "Your custom text"; }) You can also output the QR code on your front-end by calling the field:
      echo $page->qr_code_field; The module uses the PHP library QR Code Generator by Kazuhiko Arase. When looking for a way to generate a QR Code in PW I came across @ryan's integration in his TFA module. I'm not very familiar with fieldtype/inputfield module development so I blindly followed @bernhard (great) tutorial and his BaseFieldtypeRuntime. At some point I'll take a deeper look to make a module on my own.
      Some ideas for improvements :
      add the ability to choose what to ouput : page's url / editUrl / file(s) / image(s) / ... allow to output multiple QR codes ?
    • By Chris Bennett
      Inspired by @bernhard's excellent work on the new customisable LESS CSS getting rolled into the core soon, I thought I would offer up the module for beta testing, if it is of interest to anyone.

      It takes a different approach to admin styling, basically using the Cascade part of CSS to over-ride default UiKit values.
      Values are stored in ModuleConfig Module creates a separate AdminThemeTweaker Folder at root, so it can link to AdminThemeTweaker.php as CSS AdminThemeTweaker.php reads the module values, constructs the CSS variables then includes the CSS framework Can be switched on and off with a click. Uninstall removes everything, thanks to bernhard's wonderful remove dir & contents function.
      It won't touch your core. It won't care if stuff is upgraded. You won't need to compile anything and you don't need to touch CSS unless you want to.

      It won't do much at all apart from read some values from your module config, work out the right CSS variables to use (auto contrast based on selected backgrounds) and throw it on your screen.
      You can configure a lot of stuff, leave it as it comes (dark and curvy), change two main colors (background and content background) or delve deep to configure custom margins, height of mastheads, and all manner of silly stuff I never use.

      Have been developing it for somewhere around 2 years now. It has been (and will continue to be) constantly tweaked over that time, as I click on something and find something else to do.
      That said, it is pretty solid and has been in constant use as my sole Admin styling option for all of those 2 years.

      If nothing else, it would be great if it can provide any assistance to @bernhard or other contributor's who may be looking to solve some of the quirkier UiKit behavior.
      Has (in my opinion) more robust and predictable handling of hidden Inputfields, data-colwidths and showIf wrappers.
      I am very keen to help out with that stuff in any way I can, though LESS (and any css frameworks/tools basically) are not my go.
      I love CSS variables and banging-rocks-together, no-dependency CSS you can write with notepad.


    • By opalepatrick
      I see old posts saying that repeaters are not the way to go in Custom Process Modules. If that is the case, when using forms (as I am trying to do) how would one tackle things like repeat contact fields where there can be multiple requirements for contact details with different parameters? (Like point of contact, director, etc) or even telephone numbers that have different uses?
      Just for background I am creating a process module that allows me to create types of financial applications in the admin area (no need to publish any of this, pure admin) that require a lot of personal or company information.
      Maybe I am thinking about this incorrectly?
    • By HMCB
      I ran across a reference to IftRunner module. The post was 6 years ago. I cant find it in available modules. Has it been pulled?
    • 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 (-).

      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.
  • Create New...