I can see how to add action to imageache presets, but I would like to have the same watermark on original file, since I am opening original with lightbox and I am after copyright protection...

Thank you!

Comments

dman’s picture

dman commented
Status: Active » Closed (won't fix)

Understood, I had a similar use in mind, BUT...
Behavior of 'original' handling is pretty consistant through Drupal - which is to leave it alone.
The big problem is that updates to the 'watermark' preset would become cumulative, and damage the 'original' if you ever updated it. We really need the original available somewhere in the background for drupal to get at.
Also the thumbs or previews would inheirit the changes made to the original. This may not be a killer for you, but is at least ugly.

The (or a) solution is to use lightbox to present a large watermarked version, possibly fullsized. lightbox had an option to choose the preset used for view-full IIRC, if not it can be hacked in.

There is a small issue of the unwatermarked versions still being technically available on the website, if you can guess the paths (not difficult to drupalistas) so if you are really paranoid it needs a little apache access restriction or something.

Currently I find this request unfeasable, sorry, due to these side-effects.
I'd be interested in any practical solutions that allow round-tripping of the source files while still protecting them from public access.
Alternative work-around suggestions?

Richard_’s picture

Richard_ commented

Hi, I agree with you, but there is a big disadvantage in storage resources.
For now I also use new preset, but my storage is getting to be eaten very soon :)

dman’s picture

dman commented

Yeah, no.
The thing to do is get more storage space. That's the cheapest thing these days. Really, that's not a good reason. :-/
Any work-around I can imagine would be messy.
It could be applied as a hack - but would be within imagecache.module if anything.
The system is set up - as a cache - that needs to be able to regenerate images quietly for any number of reasons.
An alternative method that just did a run-once on upload could be designed, and even re-use the 'actions' if you wanted, but it's just not part of the pipeline we have.

Have a look at media-mover module, which can pipeline run-once processes against media files. If we can expose the imagecache - actions to the mm api, it's a win, and you can create a new pipeline. Some assembly required. Even mm is not prone to deleting or overwriting its originals, (for above reasons) but it could be done.