OK, it looks like I have this all figured out... I have added my "Cliff Notes" of what I learned at the bottom of the first post but reposted here:
Quote:
Edit for Cliff Notes to Solution:
The problem I had was caused by the server NOT having write permission for the image file! The server would get a "No Permissions" message but the $watermarked variable was NEVER getting defined elsewhere so the value of the variable was NULL. When the database updated, the "no" became "null". With the value being NULL, the script would never try to watermark the images again (it wanted to see "no") and I would see the "done" message even though the images were not changed!
|
There is an error in the code that should get updated (Change of watermarked ="yes") but as I said this was not the problem itself.
I have two product enhancement suggestions that would have prevented this problem as well...
1. Perhaps you should create a check in there to verify that the server has write permission for an image and let the user know if not
2. Create a default "no" value for the variable so it only gets changed from no if the image is actually watermarked.
Finally, I will take my search for a way to have a smaller watermark for smaller images to a new thread as I have pretty much got my problem figured out with this issue...