There’s a fine line between simplicity and functional overload. So rather than add a ton of things right out of the gate, I wanted to see what real users wanted vs. what I personally thought might be useful.
Keeping an internal backup variation is one of the things I thought might be useful, but wanted to see if anyone else thought the same. Part of me didn’t like storing the original since it’s potentially a much larger file/different format (it could eat a lot of storage space if someone has a ton of images). I also don’t love that WordPress’s media variations are all publicly accessible if someone knows the URL, so it would allow a smart malicious user to pull non-watermarked versions of images).
So ya… that was the reasoning about not having it right on day 1.
Thank you for your response and for your amazing extension. Allowing the option to store the original in a subfolder of “wp-content/uploads/” would make it possible to keep it either for a potential targeted rollback or for another use 😉. It is up to the user to implement protections on the folder by any means; there is no shortage of solutions.
Just rolled out 1.0.1, which includes backup support (it’s an toggle in the plugin settings).
That’s great!
Is it possible:
That only the original image is saved without all the WordPress size versions?
That the original image is moved to a backup folder?
That the original is also deleted when we delete it from the media library?
Where can I make a donation to thank you for this extension?
Thank you
-
This reply was modified 2 months, 2 weeks ago by
vmadien.
-
This reply was modified 2 months, 2 weeks ago by vmadien.
While I too, find all the size variations that WordPress generates annoying, honestly that’s a different thing (and just deleting them all could cause problems with themes that expect them to be there). This plugin isn’t intended to be an all inclusive solution to everything related to images. I imagine there’s already something out there that does it already (I don’t actually know, but I would think so)?
Building a separate backup location just opens up a lot potential problems. Doing it the way it’s currently done (with a special image variation) allows other plugins to keep working as expected. An example of this is the backup can automatically be stored in the cloud with R2 if you use my Cloudflare plugin (allows you to store media in the cloud) without plugins needing to change things to then also manage a special custom backup location. It could in theory be done, but you are introducing a lot of extra complexity and you would lose the ability for third-party plugins to work with the custom backup location without them changing their code.
Doing it as it’s done (as a WordPress variation of the image), other things like deletions (even if doing something with a different plugin, like storing them in the cloud) is automatic.
TL;DR: I’m trying to keep it simple and efficient as well as using things (like image variations for backups) so it all works as expected even with third-party plugins.
