Of course anything is possible if you work hard enough at it. Watermarking is an option and watermarked images are cached so there are a couple of approaches.
1. Normally operate without watermarking. Clear your cache of the images you want watermarked. Set the option to the watermark and "view" the images to load them to the cache. Then reset the option. These images will be watermarked so long as the cache is not cleared.
2. Place code in the album.php theme script to set the watermark option if you are viewing the desired album/subalbum, Clear the cache to rid it of unwatermarked images.
I recently upgraded to 1.2.5 and tried method 1, unfortunately without success. As soon as I set the option back to NO WATERMARK, even the newly re-cached images reverted to no mark. I did make sure to do a forced refresh of my browser with each attempt. Is there a special way to "view" the image as you mention, other than just clicking on them from the EDIT tab, to get them loaded into the cache properly?
Is there possibly any plan to include the option to watermark some albums and not others in a future version? I have no idea how to do method 2, or I would try that next. Sorry... still a newbie here, but trying to learn as fast as I can. Thanks for any additional help.
Sorry for the double post -- if someone could possibly post a sample code that I could place in the album.php theme script to execute the specific application of watermarks, I would love to try that method. Thanks again for any help.
Okay, I downloaded all the new files in changeset 4172 and uploaded them to my server into their respective folders. However, when I reran the setup, I got a completely blank screen. I double checked each file to make sure it correctly replaced its older counterpart, and that the new directories (PHP4_functions and PHP5_functions) were created in the proper locations, then reuploaded all the new files again, but got the same result.
I can always go back and reinstall the original 1.2.5 package, but I really want to use this new watermark feature.
Any idea what could have happened to generate a blank page on setup? Thanks again.
Found the problem. Turns out I missed uploading some of the earlier rebuild files before I uploaded the 4172 changeset. Very embarrassed....
THANK YOU for this new feature. It works perfectly. Just have to remember to uncheck the OPTIONS page watermark option and set it in each individual album. I did notice that some of my thumbnails were randomly watermarked/ not-watermarked within the same album, but I don't really care as long as the full sized image is marked, which they all were. Thank you again. Exactly what I needed!
I am still having trouble with an error message on full-sized image loading, though. I get the following error message for some images, (but not all), when I click their reduced size version. This issue seems like it may be related to image file size -- all my images are easily under the 10MB Zen Photo limit, but all uploaded images over about 1.1 MB are failing to load full size (My largest image is about 4.8MB and is one of several that gives the error message below). Any ideas?
` The server encountered an unexpected condition which prevented it from fulfilling the request. The script had an error or it did not produce any output. If there was an error, you should be able to see it in the error log. ` If anyone can give me a quick tutorial on how to retrieve the appropriate error log, I will do that next. Thank you again. I need to make a donation very soon for all this wonderful support. You take Paypal? You guys are really great (and have the patience of saints, I might add).
This feature works only on the images. Thumbs are covered by the thumb options
As to the full sized image--see the troubleshooting guide regards image sizes. In short it is not the file size but the image dimensions that matter.
I think there is a donation button on http://www.zenphoto.org/index.php. I don't really get involved in that. Most people just use the software without contributing, so in a good year we get enough to offset the server costs.
Hm, I don't think it's a dimensions things, at least not with my situation. Some of my smaller-sized files that are loading fine actually have the largest dimensions, whereas all my large size files are failing to display full-sized regardless of dimensions. All are jpg, btw.
Been reading through the Troubleshooting guide and through several topics in the help forums and been wondering if this might have something to do with the fact that I am using PHP 4.4.7 while the new build wants 4.4.8 or later -- something with the memory allotment, maybe?
I will need to go to my web admin for an upgrade there though -- no clue whatsoever how to upgrade my PHP.
Donation sent, btw. Worth it to me for the features and great support. Thanks again.
I would certainly recommend going to PHP 5.2+. Specially for the next release. We are concentrating our efforts on PHP5 and just leaving PHP4 around for legacy. In particular, PHP5 has a bunch of built in functions which we have to reproduce in script for PHP4. That means that the memory footpring of PHP5 will be smaller than the one of PHP4.
Comments
Of course anything is possible if you work hard enough at it. Watermarking is an option and watermarked images are cached so there are a couple of approaches.
1. Normally operate without watermarking. Clear your cache of the images you want watermarked. Set the option to the watermark and "view" the images to load them to the cache. Then reset the option. These images will be watermarked so long as the cache is not cleared.
2. Place code in the album.php theme script to set the watermark option if you are viewing the desired album/subalbum, Clear the cache to rid it of unwatermarked images.
I recently upgraded to 1.2.5 and tried method 1, unfortunately without success. As soon as I set the option back to NO WATERMARK, even the newly re-cached images reverted to no mark. I did make sure to do a forced refresh of my browser with each attempt. Is there a special way to "view" the image as you mention, other than just clicking on them from the EDIT tab, to get them loaded into the cache properly?
Is there possibly any plan to include the option to watermark some albums and not others in a future version? I have no idea how to do method 2, or I would try that next. Sorry... still a newbie here, but trying to learn as fast as I can. Thanks for any additional help.
I can always go back and reinstall the original 1.2.5 package, but I really want to use this new watermark feature.
Any idea what could have happened to generate a blank page on setup? Thanks again.
THANK YOU for this new feature. It works perfectly. Just have to remember to uncheck the OPTIONS page watermark option and set it in each individual album. I did notice that some of my thumbnails were randomly watermarked/ not-watermarked within the same album, but I don't really care as long as the full sized image is marked, which they all were. Thank you again. Exactly what I needed!
I am still having trouble with an error message on full-sized image loading, though. I get the following error message for some images, (but not all), when I click their reduced size version. This issue seems like it may be related to image file size -- all my images are easily under the 10MB Zen Photo limit, but all uploaded images over about 1.1 MB are failing to load full size (My largest image is about 4.8MB and is one of several that gives the error message below). Any ideas?
`
The server encountered an unexpected condition which prevented it from fulfilling the request.
The script had an error or it did not produce any output. If there was an error, you should be able to see it in the error log.
`
If anyone can give me a quick tutorial on how to retrieve the appropriate error log, I will do that next. Thank you again. I need to make a donation very soon for all this wonderful support. You take Paypal? You guys are really great (and have the patience of saints, I might add).
As to the full sized image--see the troubleshooting guide regards image sizes. In short it is not the file size but the image dimensions that matter.
I think there is a donation button on http://www.zenphoto.org/index.php. I don't really get involved in that. Most people just use the software without contributing, so in a good year we get enough to offset the server costs.
Been reading through the Troubleshooting guide and through several topics in the help forums and been wondering if this might have something to do with the fact that I am using PHP 4.4.7 while the new build wants 4.4.8 or later -- something with the memory allotment, maybe?
I will need to go to my web admin for an upgrade there though -- no clue whatsoever how to upgrade my PHP.
Donation sent, btw. Worth it to me for the features and great support. Thanks again.