Media Manager

[David Karich]

20 hours ago, kongondo said:

A question to you all, how does the powerful but potentially confusing inputfield selector work for your clients? Do they use it or would you prefer a simpler interface such as the WP one in the screenshot shown above by @David Karich?

@kongondo From my experience, my clients are overwhelmed with the InputfieldSelector and Lister and don't know what to do with them. I would also prefer a very simple approach here: "Search field for text", optional filter options in a simple UI: file type, time period (of the upload).

[David Karich]

17 hours ago, nurkka said:

Hi @kongondo

First of all thank you for the awesome plugin!

It would be really awesome if the selection would run through an interface with a folder structure. And it would be perfect if one could define per template in which folder the selection would start.

An example: Assuming we have a folder "Employee photos" and a folder "Customers" (or a lot more folders and subfolders 😉 ), then it would be perfect if one could give the input field the information that the image selection on employee detail pages starts in the folder "Employee photos". That would be much easier for the clients/editors to work with.

And without a folder structure, it would be great if one could define per template with which category or tag the input field starts, i.e. to have a ore-defined filter setting per template.

Very good approach, but possibly not or not only via a template approach. I am very fond of the PW-internal possibilities of input and field dependencies (https://processwire.com/docs/fields/dependencies/). Here is a productive scenario of how I run it in an editorial workflow on another system I developed from scratch: 

• The article template has the input fields date, category of the article (page reference or select), article images, etc. 
• The editor can upload new images (or select existing ones from the library and add them) directly to the input field of the article images by dragging and dropping. 
• When the new images are uploaded, they are automatically assigned in the library on the basis of the selected category and date. This eliminates a complete step of manual assignment for editors.

@kongondo My idea for the MM: to enable a configuration for the input field that assigns new images to defined categories on the basis of other fields of the template and their values when they are uploaded. If this option is not configured, then I would also prefer the default behaviour "uncategorised" as lying in a "root folder" and the editors have to clean up themselves.

[David Karich]

@kongondo And because it is so much fun to think about the new MM and which requirements are more difficult to implement so far, I have another feature request. 🤪

I have a few multi-language websites that keep running into the problem that different images have to be displayed depending on the language, e.g. because there is text on the images.

Currently, I can only solve this in a complicated way using the PW-internal option with image tags. Personally, I find this a design workflow break in the whole PW concept, because the rest works wonderfully with the LangTabs modules. Perhaps also a feature request to @ryan at this point. 🙃

My wish here would be to map the MM-InputfieldImage in the same way as multi-lang text fields. So with a simple language switch, select another item from the library.

[kongondo]

Thanks @David Karich, @nurkkaand @gebeer for the great insights and suggestions!

On 3/10/2023 at 7:08 PM, David Karich said:

But it behaves like real folders. When you click on "People", only two folders are displayed, but no pictures from both subfolders. I would also prefer this. Inheriting subitems in the view works well for a few folders, but not for 20, 50, 100 and then recursively over several levels lower.

Thanks for confirming. I now see how displaying all items from nested folders in the parent folder view can be problematic.

On 3/10/2023 at 8:38 PM, nurkka said:

It would be nice to have a full text search, which would always be visible.

I have been thinking of this (as a 'simple search') that is always visible and underneath that a link to click to reveal the 'advanced search'. This could either be a 'toned down' lister (e.g. some system settings not visible as clients perhaps don't use this) or a (configurable?) custom filter/lister that has only the most relevant features such as date, title, etc?

On 3/10/2023 at 8:38 PM, nurkka said:

and previously set filter values would be visible right away.

Yes, can work this in. Either cookies, local storage or session.

On 3/10/2023 at 8:38 PM, nurkka said:

Also a more compact view for pdf documents would be great, because the current grid and list view both require a lot of space if one has some hundred pdfs in the library. In a past project I added the pdf filenames to the grid view by modifiying some javascript files, to have a more compact view with the filenames visible. Perhaps, pdf icons could be a lot smaller or omitted at all in the document view.

I agree about the need for compactness and even make this configurable. A visual to mockup to get more going would be great if you could show me one, thanks.

On 3/10/2023 at 8:38 PM, nurkka said:

The UI elements could be smaller and information like how many times an image was used, filesize, etc. could be hidden and made visible with a toggle button, so everything would take up less space and more image and document items would fit on the screen.

Agreed. I am leaning toward how it is done in GDrive, with the 'view details' icon opening the details pane on the right.

On 3/11/2023 at 2:43 AM, gebeer said:

ATM there are too many steps involved when tagging uploaded media.

Yes, agreed.

On 3/11/2023 at 2:43 AM, gebeer said:

I agree this should be separate from the media types. Maybe something like "uncategorized"

Good idea.

On 3/11/2023 at 2:43 AM, gebeer said:

The inbuilt image/file tags could be used in the background to store the tags. But for editing I would prefer if I did not have to edit an image before I can input tags. It would be cleaner and faster for editors if they can just edit tags directly without having to go the extra step to edit the image. So the tags field would have to live on the MM page that holds the media. Does that make sense?

Definitely agree. Tagging process should be as easy as possible for editors. In terms of the DB layer, I thought a bit about using the inbuilt image tags but now I am leaning toward saving these separately as 'categories', one per page. Although I am still thinking about this, one page per category has many advantages, including:

1. Management: Managing all categories in one place: e.g., categories 'animal', 'dog', 'cat' are easier managed in one place rather than in image/file tags. Editors wouldn't have to know or worry about these pages. Their only interaction would be creating, managing (editing, deleting, etc.) categories.
2. Editing: Edit once, edit everywhere: If we wanted to change 'dog' to 'Canis lupus familiaris' for instance, we can do it easily in one place just by editing the category 'dog' instead of updating image/file tags.
3. Inputfield Control: Per template category control of available media (suggested by Nurrka) Using pages would make this implementation much easier, e.g. if people is a category, and an MM inputfield is limited (at template level) to only allow media in people category, we would only allow selection and storage of people children, i.e. categories 'men' and 'women', for instance.
4. Category Tree: This will help with building the tree on the left. It is easier than to fish for tags saved in media. It is easier to work with what is referenced (the categories) instead of the 'referrer' (the media themselves) in this case.
5. Nesting: It is also easier to nest categories (folders) if the are pages instead of image/file tags.
6. Multilingual: Page titles (category titles) can be multilingual; image/file tags are not.
7. Customisation: Pages allow one to scale as much as they need to. Say, in future, you want your categories to have a description or some other field, developers can easily add extra fields to the MM categories template.

On 3/11/2023 at 2:43 AM, gebeer said:

Also there should be a way how we can pre-define available categories. Just like we can pre-define available tags for aan image/file field.

Agreed. In my thinking above, this would be a new 'Manage Categories' MM view. Predefined categories will force editors to only pick from these categories. We can perhaps use the details pane on the right (like GDrive) that I am thinking of as mentioned above for this. Editors could then apply categories to a selected media. Choices would be in a Selectize input. In this details pane, just like GDrive, if one media is selected, we show you its details, plus have the input for categories. If multiple media are selected, we don't show details, just manage/add categories input. 

I'll have a think about whether to retain the current MM bulk apply/remove 'tags'. Also, whether to retain this feature at all (i.e., the current 'tags'.) given that 'categories' are a more powerful feature (at least that's what I think).

On 3/11/2023 at 2:43 AM, gebeer said:

Almost all of my clients are overwhelmed by PW Lister filters. Even with predefined filter profiles it is hard for non-techy people to understand the concept and what they see in the dropdown selects. I think this is a very tough one to tackle. If you have just one search input like in WP, you get back results that you where not looking for because the search is too broad. Maybe a combination of a text input that searches for file names and one select dropdown that determines the category you want to search in could work? 

Thanks for the feedback. Maybe my suggestion for a 'simple' default search and an 'advanced' one would help with this issue?

 

On 3/11/2023 at 2:43 AM, gebeer said:

Totally agree. It could be a configurable option whether to include files from subfolders in the view or not.

Good point, maybe even add a configurable threshold, e.g. if 20 or more items, grab first 20 then show text like '+ 150 more' or similar.

On 3/11/2023 at 2:43 AM, gebeer said:

For the time being a config option for icon size would be helpful. Or do the Preview maximum width/height settings already have an effect on those icons? 

Another great suggestion! We can make this configurable.  No, the preview min/max are just for the upload (They are jQuery File Upload options).

 

[kongondo]

On 3/11/2023 at 9:27 AM, David Karich said:

From my experience, my clients are overwhelmed with the InputfieldSelector and Lister and don't know what to do with them. I would also prefer a very simple approach here: "Search field for text", optional filter options in a simple UI: file type, time period (of the upload).

Thanks for the feedback.

On 3/11/2023 at 9:42 AM, David Karich said:

My idea for the MM: to enable a configuration for the input field that assigns new images to defined categories on the basis of other fields of the template and their values when they are uploaded. If this option is not configured, then I would also prefer the default behaviour "uncategorised" as lying in a "root folder" and the editors have to clean up themselves.

I'll have a think about this @David Karich. It does sound like something that could be accomplished via a Hook. 

On 3/11/2023 at 9:51 AM, David Karich said:

My wish here would be to map the MM-InputfieldImage in the same way as multi-lang text fields. So with a simple language switch, select another item from the library.

Very interesting idea. So, the images themselves (the pages in MM library) would be language-unaware but the MM Inputfields would be language aware (perhaps configurable) and fall back to default language media if no media in 'other language'.  I am not good with GUIs so any mock-up for this that I can get would be appreciated. Although, for consistency, it should perhaps mimick the current image fields language tabs.

Lots to think about for me but thoroughly exciting! 😄 

[gebeer]

15 hours ago, kongondo said:

I thought a bit about using the inbuilt image tags but now I am leaning toward saving these separately as 'categories', one per page.

Great idea. This is the most flexible way of handling categories. Go for it 🙂 

[MrSnoozles]

@kongondo Just want to let you know I'm super happy development on the module continues. The functionality of the current version is great, it's just a bit unpolished compared to file managers from other CMS.

As for new features: I agree with the others, folders and simplified search (+ advanced filtering) are definitely my top two wishes too. Also easier API access to render media in the frontend would be a nice to have. If I remember correctly it was a bit more complicated to use than the usual ProcessWire API.

Super excited for the updates, thank you!

[kongondo]

8 hours ago, MrSnoozles said:

The functionality of the current version is great, it's just a bit unpolished compared to file managers from other CMS.

Agreed! 

8 hours ago, MrSnoozles said:

Also easier API access to render media in the frontend would be a nice to have. If I remember correctly it was a bit more complicated to use than the usual ProcessWire API.

Great thoughts! I've thought about this before. I am keen to work on it. A $mediaManager variable will make it very easy to interact with MM in the frontend. This will make it easier to directly use media items in the frontend. For instance, directly build a photo gallery using images from the library without the need to add these to a page first. It will also make it easier to manage media items using the API, import items into the library, etc.

I have updated the the MM Next plans post.

[gornycreative]

Hey @kongondo I just realized you were redoing this - wow!

If I could suggest two places to look for inspiration from the UI side. WP is nigh unusable out of the box for a number of clients in terms of both media and filtering and the two favorite plugins I deploy to handle these have always been Admin Columns Pro on the filtering side and WP Media Folder on the media management side:

https://www.admincolumns.com/what-is-admin-columns/

Admin Columns Pro is just pure magic for clients. Being able to edit-in-place on the post/page list, add images from the grid, batch commands from the grid - this plugin alone does so much for wordpress it's a no-brainer first install. But the filtering columns at the top of the list that conform to custom posts and pages (like if you are using ACF or Pods) is really intuitive and awesome AJAX. Like I said, clients love how much it streamlines their work.

I personally have gotten used to listers, but the experience of listers on Processwire is a lot more like NSP Code's advanced ordering WP plugin where you are able to filter and sort hierarchical lists and then create set list pages for them:

https://www.nsp-code.com/premium-plugins/

This sort of thing is fine for developers to put together special lists - and I actually use lister pro to provide clients with worklists that detect content that is incomplete (missing author, card image, unpublished, too short, etc.) but as other have mentioned, the lister interface for some reason is hard to grasp. I always had the same problem trying to train people on using Advanced Post Types Order.

https://www.joomunited.com/wordpress-products/wp-media-folder

I tried a bunch of media managers for wordpress and this is the one that folks seemed to like the best, and I like that it produces its own metalayer without disturbing the file system away - so if for some reason they uninstall it everything revert to the big perpetual stew that is WP media.

Not saying that you need to duplicate anything here, but I saw others posting about things that clients have liked from a UX perspective and so here ya go!

[kongondo]

Hey @gornycreative,

Great write-up, insights and suggestions!

4 hours ago, gornycreative said:

Not saying that you need to duplicate anything here, but I saw others posting about things that clients have liked from a UX perspective and so here ya go!

This is very inspirational! It is going to be very helpful, thanks!

[sodesign]

I wonder if anyone can help. I'm writing an import script to add a few hundred pages to a site, and each page has a media-manager-image field. (It's for a staging site where I'm merging some recent content from a production site to keep it up-to-date.)

I successfully imported the pages using the native Processwire Import/Export, but the media manager fields were empty. I think this is because the page IDs are different on the production site and the staging site.

I have also successfully imported all of the media manager pages and assets to the staging site.

Is there a way I can populate the media-manager-image fields with the API? 

Thanks in advance, I've been pulling my hair out trying to achieve this! 😅

// I tried this approach, but it's not right
$existing_image_path = extract_img_path($img); // custom function to parse CSV, eg '/site/assets/files/86258/an-image-name.jpg'
$exists = wire('files')->exists($existing_image_path);
if ($exists) {
	// This doesn't work because it's not an image field
	$p->blog_images->add($existing_image_path);
}
$p->save();

// I then tried several ways like this, because the media is all on the staging site, but I couldn't find a way to query the media manager // pages successfully
$filename = extract_img_filename($img); // custom function to parse CSV, eg 'an-image-name.jpg'
$filename_query = "media_manager_image.filename=$filename";
$m = wire('pages')->find("template=media-manager-image,$filename_query");
if ($m->id > 0) {
	// This doesn't work because it's not an image field
	$p->blog_images = $m;
}
$p->save();

 

Edited April 19 by sodesign
add some example code

[kongondo]

Hi @sodesign,

8 hours ago, sodesign said:

script to add a few hundred pages to a site, and each page has a media-manager-image field

It is not clear to me what you mean by 'media-manager-image field'. Do you mean images in a FieldtypeMediaManager/InputfieldMediaManager field on a 'usual' ProcessWire page or are you talking about the actual image field (media_manager_image) that holds the images for media items in media manager pages  (which live in /admin/media-manager/...)?

Are the staging and production sites on the same server?

Edited April 19 by kongondo

[sodesign]

Thanks for getting back to me.

Yes, I did mean a FieldtypeMediaManager field on a usual PW page.

The sites aren’t on the same server currently.

[kongondo]

10 hours ago, sodesign said:

I successfully imported the pages using the native Processwire Import/Export, but the media manager fields were empty. I think this is because the page IDs are different on the production site and the staging site.

I think you are right. It sounds like the import for the media pages themselves (i.e. the media manager pages) worked. However, these were created as new pages using the template 'media-manager-image'. On the other hand, the 'usual' pages with FieldtypeMediaManager field perhaps also got their values imported. One of the values they hold is the page ID of the page where the media (in this case image) really lives. So, in the production site one value could be 1234. However, the newly created page in the staging could have been created with a page ID 5623.  This means that if by coincidence some IDs are identical between the sites, you might get MM images showing up in the wrong pages 😀.  

 

Back to your script.

You need to find a connection between production 'media manager pages' (i.e. the pages that use the template media-manager-image) and the staging usual pages media manager fields. The connection between them that has not changed is the page name of the media manager pages, i.e.

Production

MM Page

• Title: My Awesome Image
• Page ID: 1234
• Name: my-awesome-image

Page with MM Field

• A Frontend Page with a Gallery showing some MM Images in an MM Field
• MM Field (WireArray of WireData where each WireData has a property id, i.e. $mmObject->id == 1234) [see the docs].

Staging

MM Page

• Title: My Awesome Image
• Page ID: 5623
• Name: my-awesome-image

Page with MM Field

• A Frontend Page with a Gallery showing some MM Images in an MM Field
• MM Field (WireArray of WireData where each WireData has a property id, i.e. $mmObject->id == 1234) <- it points to the old value in the production site.

As you can see, the common things between the two sties is the name/title. 

One (rather convoluted way) to go about it is (written in browser, not tested and only quickly thought through).

1. Get the values of the $mmObject->id in your 'new pages [the imports]', i.e., the value 1234 in our example. You could loop through each of the staging pages or just grab them all using findRaw("template=your-template",['id','mm_field']);
2. Process the the above array to get all the 'data' values in the 'mm_field'. Keep this one one array.
3. Use the ids you have collected in #2 and do a findRaw in the production site (implode the IDs so you get 1234|1345|4356, etc). What you want are the names, so findRaw("id=$ids,check_access=0",['id','name']);
4. #3 Will give you the names and IDs of the MM pages in Production. Prepare these names for an OR selector string similar to what you did with $ids in #3.
5. Use the $names selector string in #3 to find the corresponding MM pages in the staging site, i.e. findRaw("name=$names",['id','name']);
6. You will end up with two arrays, one for production and one for staging with values $productionArray = [1234=>'my-awesome-image'] and $stagingArray = [5623 => 'my-awesome-image'].
7. You can process this two arrays so that you end up with $processedArray = [1234 => 5623, etc]
8. Loop through the newly imported pages in staging, loop through their MM fields and replace 1234 with 5623.

OR simply...

1. Install ProcessDatabaseBackups in the production site
2. Export the site usign ProcessDatabaseBackups
3. Install ProcessDatabaseBackups in the staging site
4. Use ProcessDatabaseBackups to backup the current DB in the staging site
5. Import the exported db from production (#2) into the staging site using ProcessDatabaseBackups
6. Copy the assets from production site into staging site
7. Test
8. Done 🙂

[sodesign]

That makes sense,  finding the connection between production 'media manager pages' and the staging usual pages media manager fields is where I was getting stuck trying to use a selector but your suggestion of looping through and creating the two arrays to compare is a great idea.

The only question I still have is with point 8:

9 hours ago, kongondo said:

Loop through the newly imported pages in staging, loop through their MM fields and replace 1234 with 5623.

How do I add a MM page to the MM field using the API if the field is currently empty? 

I'll be sure to check out ProcessDatabaseBackups! Can it handle individual parts of a site?

[kongondo]

8 hours ago, sodesign said:

I'll be sure to check out ProcessDatabaseBackups! Can it handle individual parts of a site?

You can cherry pick what tables to backup up, e.g. 'pages', 'field_body', 'field_images', 'templates', etc.

8 hours ago, sodesign said:

How do I add a MM page to the MM field using the API if the field is currently empty? 

If the MM fields are empty you need to find the connection between the production 'usual pages' with MM fields and the corresponding staging 'usual pages' with MM fields. Given that you used an import, similar to above assumptions, their titles and names will (should) be identical, but their IDs will be different. Hence:

Production

A Usual Page -> exported to staging

• Title: My Usual Page
• Page ID: 1450
• Name: my-usual-page
• mm_field (WireArray of WireData where each WireData has a property id, i.e. $mmObject->id == 1234)

Staging

A Usual Page <- imported from production

• Title: My Usual Page
• Page ID: 1876
• Name: my-usual-page
• mm_field (WireArray of WireData BUT EMPTY -> SO NO values for mm_field)

Production and Staging 'usual pages' are connected via 'names'. So...

1. Staging: Use findRaw or Loop through imported staging pages. Save their names and IDs in an array.
2. Staging: Prepare an OR (piped) selector string of $namesPipedSelectorString from #1
3. Production: Use findRaw with $namesPipedSelectorString to find the ids, names and mm_fields values in the corresponding pages in production.
4. Production: Prepare the IDs of the mm_fields in #3 as $idsOfMMPagesInMMFieldPipedSelectorString. If you use findRaw, this will be in the array column 'data'. These are the page IDs of the MM pages in production.
5. Production: Use $idsOfMMPagesInMMFieldPipedSelectorString in a findRaw to get the names of the MM pages in production. Prepare these in an array of $namesOfMMPagesPipedSelectorString. d
6. Staging: Use $namesOfMMPagesPipedSelectorString from #5 in a findRaw() to find the page IDs of the corresponding MM pages that were created when you imported from production. In other words, the MM pages in #5 and #6 are identical, expect for their page IDs.
7. Production & Staging: Prepare an array that contains the names of the exported usual pages, the IDs of the imported usual pages (the ones with empty MM fields), the page IDs of the MM pages in #6.
8. Your connection is complete. You now know the IDs of the MM pages and their corresponding usual pages where they need to be references in the MM fields.
9. Staging: Loop through newly imported pages and use the array in #7 to populate the empty MM fields. I.e., in the loop, when you get to a page, e.g. 'my-usual-page', using the array in #7 find the page IDs of the corresponding MM pages. Use each of those to create a WireData object that you add to the WireArray mm_field. Pseudo code below (not tested):

<?php

namespace ProcessWire;

$importedUsualPages = $pages->find("your-selector");

$arrayOfConnections = [
  'my-usual-page' => [
    'id' => 1876,
    'imported_mm_pages_ids' => [2035, 2036, 2038, 2056]
  ]
];

foreach($importedUsualPages as $importedUsualPage){
  $importedUsualPage->of(false);
  $mmField = new WireArray();
  $importedMMPagesIDs = $arrayOfConnections[$importedUsualPage->name];
  foreach($importedMMPagesIDs as $importedMMPageID){
    $mmFieldItem = new WireData();
    $mmFieldItem->id = $importedMMPageID;
    $mmFieldItem->type = 3;// 1-audio; 2-document; 3-image; 4-video
    // add MM item to WireArray
    $mmField->add($mmFieldItem);
  }
  // -----
  // populate mm_field of page
  $importedUsualPage->set('mm_field', $mmField);
  $importedUsualPage->save('mm_field');
}

 

Hope this helps. Let me know how it goes.

[sodesign]

Amazing, I'll give this approach a go and let you know how I get on.

Thanks you for taking the time to write this up, I really appreciate it 🙂

[gebeer]

@kongondo on multilang installs, when the title field is set to TextLanguage, MM pages that are creted for each image under Admin->Media Manager->Media Manager: image are published in the default language only. Other languages are disabled.

This poses a problem with $pages->find operations, e.g. 

$this->wire->pages->findIDs("template=media-manager-image, image_gallery=1, products.id={$this->id}");

this return 0 pages for non-default languages. I had to change the selector to

$this->wire->pages->findIDs("template=media-manager-image, image_gallery=1, products.id={$this->id}, include=all, status!=" . Page::statusUnpublished . ', status<' . Page::statusTrash);

in order to get results.

It might be good to have these pages published in all languages by default.

[Grzegorz]

Hi, 

I need to upgrade my links and buttons so they can point not only to pages but also to any file inside media manager.
Right now links can be added two ways, in the text field using ckeditor and in button field (is assisted url).CKEditor works for me well but I have a problem with assisted url field.
When I select any media like pdf or image via assisted url it doesn't update the field with media url and console shows this error:
MediaManagerImageEditor.js:77 Uncaught TypeError: Cannot read properties of undefined (reading 'getSelection') at insertLinkMediaManager (MediaManagerImageEditor.js:77:29)

Does anyone who use Media Manager module with assisted url have the same issue?

 

[kongondo]

12 hours ago, gebeer said:

on multilang installs, when the title field is set to TextLanguage, MM pages that are creted for each image under Admin->Media Manager->Media Manager: image are published in the default language only. Other languages are disabled.

Thanks for reporting @gebeer. Added to my TODO.

[Boost]

Hei,

Is it only me or the ProcessMediaManager by @kongondo doesn't install on the latest PW? I'm getting this error:

[fruid]

not sure if this has been asked before, is there a way to filter the media by the page that they are used on?

[kongondo]

On 5/11/2023 at 1:50 PM, Boost said:

Hei,

Is it only me or the ProcessMediaManager by @kongondo doesn't install on the latest PW? I'm getting this error:

Hi @Boost,

Are you able to install other modules by uploading their zip files? If not, I am thinking is a permissions issue in your system?

[kongondo]

4 hours ago, fruid said:

not sure if this has been asked before, is there a way to filter the media by the page that they are used on?

Hi @fruid,

Do you mean when viewing the media in Media Manager? If yes, that is not currently possible. What's your use case? I'll have a think about this.

[fruid]

15 hours ago, kongondo said:

Do you mean when viewing the media in Media Manager? If yes, that is not currently possible. What's your use case? I'll have a think about this.

We have different pages using the same images, that's why I wanted to give MM a try. Now there's unfortunately no possibility to have any structure in the MM – other than the type of media – but no subfolders, no parents. So I thought, if I could just filter/search an image by the page that it is already used in, that would be a work-around. I would just upload the image at the input field of the first page I want to use it in directly and for the other pages find the images by the title of the page where I uploaded it. But you cannot do that either. All I can do is filter the name of the image which is kind of a drag because our naming convention is quite messy and we migrate from a different CMS.