Deletion menu absent from search results

[newmikey]

If this question has been answered before, my apologies! I am a new user of Chevereto although I have used other PHP based image galleries before as well as Piwigo.

I have migrated thousands of images off Flickr and onto my new Chevereto-driven site and I'm trying to cull them as there are many images from literally before 2010 with lower quality which I would really prefer to ditch. Preserve hosting server space etc. I have found it very useful to organize images that I want people to actually see in public albums, images I don't necessarily need everyone to look at but that I want to share in a private album with sharing enabled (like the screenprints below f.i.) and all others in a private album where I can sort and sift at will.

I found that I can make a large selection in the album view and then select [Delete] but the [Delete] option does not appear when i have the results of a search action. Is mass-deletion in a search results screen possible?

 

[Rodolfo]

Chevereto supports expirable images, so you can use that to force the deletion of old content.

Here is an example: https://chevereto.com/community/threads/delete-images-that-have-less-than-1-view.12423/#post-63544

You will only need to tweak the the dates.

 

[newmikey]

Thanks! I noticed that the dropdown options [Create album] and [Move to album] are also missing. Is that equally easy to address?

User case:
1. Want to go through all images throughout with "sunset" in their name and move them to a new album or a different existing album
2. Use search option with *sunset* as key
3. Select good one ones and use dropdown menu [Move to album] to do what is required
4. Use [select all] on the remainder on the page and use the dropdown [Delete]

 

[Rodolfo]

General search misses these options because the search is site wide, for all users.

For your use case, you should search from the /user profile. That way the results will show the album move options.

 

[newmikey]

You Sir, are a genius! That did the trick and I now also understand why it wouldn't work site wide.