Changing watermark settings does not work retroactive, watermark settings apply to new images only.
-Shaman- - April 6, 2008 - 12:43
| Project: | Image watermark |
| Version: | 5.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
"Changing watermark settings does not work retroactive, watermark settings apply to new images only."
Last times I've changed a watermark image, to a new one, but there's a problem, because I have already more than 800 pics in my system, so trying to apply watermark to each image manually is insane…
I'm finding this issue as 'critical' because it is really important to make this working as it shoould.
#1
This is the way the module works at the moment. It was designed to be triggered when an image is uploaded.
Adding a new feature for this is fine, but someone has to come up with a patch to do this, and it has to be smart to do images in batches, while keeping track of new images so as not to recreate the watermark for them.
#2
Very nice, but i don't mind who and how would make this working, I'm sure that this should be done very soon, because this is a real problem.
#3
Shaman
The module has existed for close to 2 years, and no one has needed this new feature, so it is only a problem for you and not for others who use it. Perhaps most sites using it only had this module from the start, and hence do not need to do anything retroactively.
Please understand that this is open source software. People enhance it when they need to.
So, if someone in your situation has the time and knowledge to add this feature, I will include it. Another option is to find someone who can do it, and pay him for adding this feature on your behalf.
Until then, you have to be patient.
#4
I would disagree with You that this is only mine problem, I've had saw a lot of forum topics about this, and even at the project site there is a sentence which I believe You posted:
"Known Limitations:
* Changing watermark settings does not work retroactive, watermark settings apply to new images only."
I thought that You as the author are working to fix this, (I would say) issue. When You're telling that this module wasn't updated for 2yrs that not so good at all, and also that "someone would do this for money" I guess that this is totally oppose to a drupal non-profit idea. I have fixed a lot of bugs in Drupal modules, and I've also added some snippets, which should was applyied from very first relases, but this module is too much complicated for me, so I posted this issue in here, hoping, that You as the author would pay some attention to this…
#5
You misunderstand. I did not say the module was not updated for 2 years. I said it has existed for 2 years, and this feature/bug/whatever was never an issue.
If I had the time, I would add this feature, but my time is limited.
As I said, be patient. Someone else can write a patch for it, and I will include it.
What you can do is post in the forums where you saw this mentioned, and ask for people to help with it. Perhaps someone can come up with a patch.
As for your comment about non-profit, you misunderstand what Open Source is about. Again, open source is written and maintained by the community, not by one person. The software is free, but the effort to do it depends on those who write it (me or someone else). People can write it in their spare time, or it can be sponsored by a company, or a project or a client.
#6
"If I had the time, I would add this feature, but my time is limited."
You could say that in the first reply to my post, and I would understand this :-)
Obviously I know that time is money, and not everything is for free (althought this is beutiful dream :) )
Hope that You'll gonna find some time, and manage with this, I'll keep my finger crossed for that.
Shaman