Jump to content

Media Manager


kongondo

Recommended Posts

27 minutes ago, David Karich said:

Apropos: I never received a download link for the update to 012 by mail. Or do I have to buy a new license?

Subscriptions (update + VIP support) are valid for 1 year. After that you can renew for a fraction of the original price. Otherwise, I don't send out update reminders but post here in the forums. If you have a valid subscription, you can use the resend download links form to get an email with the download link to the latest version (or use the link in the original email you received after purchase). For renewals, please use the renewal form. Any problems, please PM or send me an email.

  • Like 1
Link to comment
Share on other sites

47 minutes ago, kongondo said:

Each media is a PW page, hidden in admin part of the tree. Non-supersusers never get to see them :-).

@kongondo To prevent a misunderstanding: each media is stored in the database, not in the file system?

Link to comment
Share on other sites

33 minutes ago, Lutz said:

@kongondo To prevent a misunderstanding: each media is stored in the database, not in the file system?

Sorry I wasn't clear.

Media = $page

Media has one MM field. In the case of images, it is an multi image field. So $page->image_field will give you the image

Media has a title field: $page->title;// title of your media

If you had own fields to Media, you can access them using $page->your_field, as usual.

However, we don't use the variable $page. Instead what you get is a MediaManager Object.

So, Media page object is $mm.

Echo $mm->id: id of the media

Echo $mm->title;

// this is the image field

foreach($mm->media) {

}

Hope this makes sense.

 

Link to comment
Share on other sites

31 minutes ago, kongondo said:

Hope this makes sense.

 

@kongondo Yes, thank you, this is what I had expected and hoped for. My question was in terms of scalability, regarding file system limits. In PW, files are stored in subdirectories under /site/assets/files, therefore we normally have to deal with max directory limits (e.g. 32k). We have $config->pagefileExtendedPaths, but it's marked as beta. So as you mentioned +500k, I hoped for an info regarding the stability of pagefileExtendedPaths (or another way to avoid collisions with max directory limits). When they manage +500k, did they enable pagefileExtendedPaths?

Link to comment
Share on other sites

  • 3 weeks later...

Thanks for this awesome module! Here is some feedback after some hours of testing: When using MediaManager along with Ryan’s ProDrafts, I had to manually disable ProDrafts support for the MediaManager specific templates. Otherwise, inserted images from the MediaManager would not display in the saved pages (neither drafts nor published versions). I figure this was because the images in MediaManager were by default also handled as drafts. After disabling ProDrafts for the MediaManager templates, everything – including working with drafts – works just fine.

  • Like 1
Link to comment
Share on other sites

11 hours ago, tb76 said:

Thanks for this awesome module!

Glad you like it.

11 hours ago, tb76 said:

I figure this was because the images in MediaManager were by default also handled as drafts. After disabling ProDrafts for the MediaManager templates, everything – including working with drafts – works just fine.

Thanks for testing and reporting back. I guess it doesn't make much sense to have a draft media (i.e. using ProDrafts). However, if you have added other fields to your Media Manager templates, you might want those to work with drafts. Hmm. I've never used ProDrafts before but you've given me something to think about.

Link to comment
Share on other sites

Hi kongondo,

one of our customers asks, if it would be possible to write out not only the usage amount of media manager items, but also all usages as list with concrete info about field, page etc. I know, this isn't going to be easy, but maybe it's worth the effort, if other users reported the same idea?

Greetings,

Thomas.

  • Like 1
Link to comment
Share on other sites

On 6/21/2019 at 3:57 PM, xportde said:

one of our customers asks, if it would be possible to write out not only the usage amount of media manager items, but also all usages as list with concrete info about field, page etc. I know, this isn't going to be easy, but maybe it's worth the effort, if other users reported the same idea?

Hi Thomas,

I'll have a think. The interface will need careful thought as it would need to be separate from the tooltip.

Link to comment
Share on other sites

  • 1 month later...
On 5/10/2019 at 3:09 PM, kongondo said:

However, two people have reported an error about class ProcessMediaManager not found in line 20 of MediaManagerUtilities.

Three people now! haha

Any news on this bug?? Thanks!

I rolled back but now I am having issues with JqueryUpload version 008 working, tried rolling back to 002 but I still can't open when I click on Add Media on any of the pages, getting:

 Uncaught Error: Class 'ProcessWire\JqueryFileUpload' not found in /srv/users/serverpilot/apps/ladosis/public/site/modules/ProcessMediaManager/ProcessMediaManager.module:209

Ok this took me through a tour of namespacing issuer all over the MediaManager modules and got it working back. 

Link to comment
Share on other sites

On 7/31/2019 at 6:23 AM, elabx said:

Three people now! haha

Any news on this bug?? Thanks!

I rolled back but now I am having issues with JqueryUpload version 008 working, tried rolling back to 002 but I still can't open when I click on Add Media on any of the pages, getting:

 Uncaught Error: Class 'ProcessWire\JqueryFileUpload' not found in /srv/users/serverpilot/apps/ladosis/public/site/modules/ProcessMediaManager/ProcessMediaManager.module:209

Ok this took me through a tour of namespacing issuer all over the MediaManager modules and got it working back. 

Hey @elabx,

Sorry for the delay in responding. I have just tested in a new PW install with only 3 modules: MM, JFU and Tracy. I had to click on Clear Compiled Files 3 or 4 times for it to finally work. Here's what I did.

  1. Upgrade JqueryFileUpload by overwriting the existing files
  2. Delete MediaManagerTabs.php and pocketgrid.css in the current (old) Media Manager install
  3. Overwrite MM version 011 files with version 012 files
  4. Access Media Manager
  5. You might see Class not found error (either MediaManagerUtilities or JqueryFileUpload
  6. Access Modules (on same tab in #4) and click on Clear Compiled Files
  7. Once step #6 is finished, click browser back button to go back to Media Manager.
  8. If you get class error again, repeat steps 6 - 7 as necessary

Please let me know if this works for you. Thanks.

  • Like 1
Link to comment
Share on other sites

@kongondo Finally managed to updated!! But you know what, now I didn't have to clear anything, it just worked after a module refresh!! Just so you have more info, the only difference was that I namespaced the old modules (in a desperate attempt to bring back everything to work because it kind of broke after I rolled back from my first install failure). honestly don't have very clear what happened, but indeed the new version works flawlessly.

Questions/issues: 

  • I don't seem to be able to drag and drop over the Inputfield. I can give you access to my site if you need to debug.
  • I cannot seem to find the edit button for the image description now, the one that was placed at the top right? Is there a new way to edit the descriptions? Appending how my images look when I click on them.   Jut realized now this is done in a normal, maybe you could enable an Edit link right on the Inputfield? At least on my site it's not showing, I'd guess that's the most practical for editors, instead of opening the Media Manager Popup.
  • I cannot get the alt text on images placed in CKEditor to update accordingly, I also have the setting updated in the Inputfield configuration, have you had any issues with this?

All my questions crossed where solved configuring the Inputfield :)

This is a GREAT update kongondo! I know this has been mentioned before but the improvement in the UI is a huge plus! I see you mentioned you have a lot of users that had never mentioned this, but in my case as with other PW users, all my clients complained about the lack of polish in UI, but this update really solves a lot of the inconveniences. 

Link to comment
Share on other sites

10 hours ago, elabx said:

Just so you have more info, the only difference was that I namespaced the old modules

Aah, nice workaround. I never thought to do that 😊.

10 hours ago, elabx said:

This is a GREAT update kongondo! I know this has been mentioned before but the improvement in the UI is a huge plus! I see you mentioned you have a lot of users that had never mentioned this, but in my case as with other PW users, all my clients complained about the lack of polish in UI, but this update really solves a lot of the inconveniences. 

Glad you like it :-).

10 hours ago, elabx said:

I cannot get the alt text on images placed in CKEditor to update accordingly, I also have the setting updated in the Inputfield configuration, have you had any issues with this?

I don't follow. What is this alt text please? Please clarify which inputfield configuration, CKEditor or MM?

Full documentation is available here, by the way :-).

Thanks.

Edited by kongondo
Link to comment
Share on other sites

5 hours ago, kongondo said:

I don't follow. What is this alt text please? Please clarify which inputfield configuration, CKEditor or MM?

 

When you insert an image through CKEditor, ideally I'd want to grab the description from the image's description field. CKEditor Inputfields fields have an option called "Image management" that should enable this:

https://processwire.com/docs/fields/textarea-fieldtype/#markup-html-option

I just can't get this to work well, if I add a new image to the text fields, their descriptions are not pulled from the images. 

My bad again man, I kept on reviewing this on the CKeditor source and just realized this is done on runtime. 

Link to comment
Share on other sites

  • 4 weeks later...

@kongondo Thank you for that module. Befor I go and order it, I'd like to make sure that the feature my client needs is included already.

For that client each media item should be available as a public download. So in the list of media in the manager there should be something like a button to copy that public link and when editing media that public link should be displayed also.

I guess the module needs some customizing to do this. Would this be possible through hooks? Especially for the media lists in the manager. Are there hooks available where I could inject some markup or even an extra column in list view?

Since all media are pages, I guess I can hook into ProcessPageEdit for those templates and add the link to display in the page editor screen? 

Link to comment
Share on other sites

On 8/28/2019 at 10:54 AM, gebeer said:

So in the list of media in the manager there should be something like a button to copy that public link and when editing media that public link should be displayed also.

Where is the link being copied from?

On 8/28/2019 at 10:54 AM, gebeer said:

Since all media are pages, I guess I can hook into ProcessPageEdit for those templates and add the link to display in the page editor screen? 

Yes, but Media Manager methods are currently not hookable. I'm not sure you've seen it, but Media Manager allows you to add your own (ProcessWire) fields to the media pages templates. Those will then be displayed in the list (table) view if you configure them to be displayed in Media Manager settings. However, you will not be able to edit the values directly in the table view. Instead, each media has an edit link that when clicked will open the full page for editing - this is a normal (almost) ProcessWire page edit form. You can use it to edit any of the fields in the template as well as the media themselves. In the frontend you access them as $m->your_public_link_field. I hope this makes sense. If not, please let me know.

Thanks.

Link to comment
Share on other sites

  • 3 months later...

Hi kongondo!

Recently, I used Media Manager in a client project. In this real world use case, the media library very quickly grew to an extent, where it was too confusing for the client. Of course I know how to apply filters, but for my client, configuring and applying filters was to complicated - even with the relatively new feature of pre-defined filters. So I thought I would ask you, if you could image to implement some additional filter-features, that would make it easier for clients:

- It would be great, if it was possible to set a default filter for every MediaManager-Field. I have a lot of different "image-types", like icons, fotos, sketches and so on. With such a feature, it would be possible to limit the displayed images to just the "type" of image, that suits the context of the current MediaManager-field. Like when applying some product icons, you don't want to choose from the whole library with all the staff portraits.

- Another great feature would be, if pre-defined filters could be applied with one click in the overview. I tried to sketch this in a fake screenshot:

image.png.e2ba4df88805529eb8e8537ea84bd795.png

In this way, an admin could pre-define all needed filters, and the user/client could just apply them with one click - without worrying about or even understanding the actual filter definition.

I guess those features don't exist already, but if so, I would be very happy, if you could point me to any existing solution.
Otherwise it would be great to have those - or similar - features in a future version.

Thanks again for the great module!

Link to comment
Share on other sites

  • 2 weeks later...
On 11/29/2019 at 1:33 PM, nurkka said:

Recently, I used Media Manager in a client project. In this real world use case, the media library very quickly grew to an extent, where it was too confusing for the client.

Hi @nurkka. Sorry for the late response. I have been away.

On 11/29/2019 at 1:33 PM, nurkka said:

It would be great, if it was possible to set a default filter for every MediaManager-Field. I have a lot of different "image-types", like icons, fotos, sketches and so on. With such a feature, it would be possible to limit the displayed images to just the "type" of image, that suits the context of the current MediaManager-field. Like when applying some product icons, you don't want to choose from the whole library with all the staff portraits.

This is an excellent suggestion! I'll have a think on how to best implement it but theoretically, it is doable.

On 11/29/2019 at 1:33 PM, nurkka said:

In this way, an admin could pre-define all needed filters, and the user/client could just apply them with one click - without worrying about or even understanding the actual filter definition

Another great suggestion! I would have to rethink the GUI a bit since tabs (Filter: Icons, Filter:Photos, etc) would quickly become unwieldy. 

On a related note, I have been planning to refactor the items shown in the Inputfield Selector (the filters) as there are a number of things not directly relevant to Media Manager that would confuse editors. For instance, the Inputfield shows non-Media Manager fields, items like Path/URL, etc.

I am planning to work on your suggestions and the refactoring in the next update.

I might call on you for a bit of testing before release, if that's OK.

Thanks. 

  • Like 2
Link to comment
Share on other sites

  • 1 month later...

Hi kongondo,

because there's no option for limiting uploaded images to image width and/or height in MM settings (or is there?), we've found out, that the PW-native image field limitations from the underlaying field media_manager_image works (input > maximum image dimensions). Unfortunately, this restriction works quiet, i.e. the MM-upload will be finished without error or warning, but the image will correctly not stored because of violating the image field dimension rules.

Would it be possible to apply the image field rules already in MM upload screen, so that the user can see possible violations before start uploading (like the maximum file size rule from MM settings)?

Greetings,

Thomas.

Link to comment
Share on other sites

1 hour ago, xportde said:

there's no option for limiting uploaded images to image width and/or height in MM settings (or is there?),

Actually, there is 😁. See under Settings > Upload Settings > Image. There are settings for min/max height and min/max width. These are directly coupled to the the field's (media_manager_image) corresponding settings. If you change one it will change the other. However, I have just noticed a bug. The min values are decoupled! This shouldn't matter much though since Media Manager will still honour the min values. I will fix these later (i.e. the 'decoupling' issue).

1 hour ago, xportde said:

so that the user can see possible violations before start uploading (like the maximum file size rule from MM settings)?

Excellent suggestion! I will add this to my TODO as well. 

NO ETA for above, just yet, sorry. I hope it isn't urgent?

Thanks!

 

 

 

Link to comment
Share on other sites

Quote

Actually, there is 😁. See under Settings > Upload Settings > Image. There are settings for min/max height and min/max width

Do you mean Image maximum width / height? So I misunderstood the notes Maximum width / height of resized images (pixels), I thought, this settings are for resizing, not for uploading? But in fact, it corresponds with the equivalent image fields. Maybe you could write the notes accordingly (Max width / height for uploaded images)?

Greetings, Thomas.

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

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

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

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

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

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

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

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

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

      Links
      ProcessWire module directory
      github.com
×
×
  • Create New...