We recently had a situation where we uploaded 50+ assets as SVG items, but then had to replace them all with PNG assets. This involved viewing each existing item individually, deleting individually, and then re-uploading.
There appears to be a bulk upload feature (which works really well), however a bulk delete would also be equally useful : )
Hey @tim,
I understand how this can become a pain, i will add this in our feature request tracker even though this is not something that we will work in a short period of time.
So, I'm reviewing this almost 12 months later and looks like we're still more or less in the same place?
I wonder if any of the Prismic team actually use Prismic 'in the wild' in live projects of their own? Because if you had to manage hundreds of images with multiple languages, you would very quickly see that changing a single image can easily waste hours of your time and become a huge pain point (almost to the point of wanting to move elsewhere).
I understand it could be a complex feature to make, however I'm sure you can appreciate that most users would be coming from an environment where this is a 'standard' feature e.g. WordPress or Prisma etc.
Please consider adding it to the feature list soon!!
Sorry about the lack of communication on this one, it wasn't assigned to one of The Team that monitors the forum, so it went unnoticed. Our bad.
So we totally agree that you have a right to complain about this one because it's something that we know is frustrating. We know making bulk changes is time-consuming currently. We really want to improve this, but this first involves making the Dashboard easier to work on for our development team.
The Dashboard was built with an internal language, so we are now in the process of modernizing our technology stack that way we can more quickly make changes like this. Once this is done we'll have more bandwidth to work on features like bulk media deletion. This could involve rebuilding the media library from the ground up and could include features like folders and improved search. So given all that I don't have any ETA on this.
We will be releasing bulk actions for documents in the near future though which was our first priority. So we hear you and we are working hard to meet your expectations.
Thank you for your patience and understanding.
Phil
(Phil Snow)
closed , flag & select 'Something Else' to reopen.
14
@Phil Is there any progress on this? I believe it's been 9 months since the last update, and it's a pretty essential task to any content-management system. Is it being worked on, or is it on some process queue so your users can track it?
Unfortunately, Delete Media assets in bulk is not possible with the bulk actions feature. Bulks actions only bulk archive, publish, delete, etc., the documents. Learn more about bulk action in this article: Make Changes in Bulk - Prismic
If you want the bulk actions feature activated to your repo, please request it as a feature activation with your repo name.
I completely agree that bulk deleting media assets is an important feature. I would also like to see such functionality, although this is not something that the development team is working on right now.
Hello @mike_g, We don't have any updates about this feature request yet. You can check out all other features that are WIP in our progress page: What's new - Prismic
This is frustrating to see. I've seen too many threads about a better media library UX, and years later still no implementation. A CMS with a great media library is a given! All the other CMS I've tried have this.
This is the most frustrating thread ever. The media library is REALLY bad compared to almost every other CMS out there.
I initially really loved working with prismic, but as projects grow, so does the media library and it's just one of the most frustrating things ever to work with.
At least add the functionality to bulk edit/remove items and a folder support. It cannot be that hard and is such a huge win for all of us. @Priyanka@Pau@Phil
Bulk tools would make it easier to delete content too (without having to code via the API) - this would reduce storage use, so your service overheads - so a potential win-win?