"addon": Watermark

[owen-b]

Yep, that's correct, they aren't there at the moment because they render my photoblog somewhat useless to visitors!

My htaccess didn't have /pixelpost/admin/wrapper.php, just /admin/wrapper.php (like Vernon suggested) because Pixelpost is in the root (public_html) folder of my server. Is that not correct?

[owen-b]

Is it perhaps something to do with my template not being a standard 'display image' template? It fades them up and has clear gifs on top for the navigational arrows etc.

[dakwegmo+]

/admin/wrapper.php is the correct path for pixelpost installed in the root of the site.

This addon isn't template dependent. When it's working, if you access any jpg in the images directory, it layers your watermark over the requested jpg and presents them as a single image. So if you were to browse to myglasseye.com/images/someimage.jpg you should still see the watermark over the image.

Based on what you've said so far you've done everything right. Do you by any chance have anything else in your image/.htaccess file, or perhaps an .htaccess file in your root directory that might be overriding the settings for this addon?

[owen-b]

Yeah I do have an htaccess file in the root:

# -FrontPage-

IndexIgnore .htaccess */.??* *~ *# */HEADER* */README* */_vti*

<Limit GET POST>
order deny,allow
deny from all
allow from all
</Limit>
<Limit PUT DELETE>
order deny,allow
deny from all
</Limit>
AuthName www.myglasseye.net
AuthUserFile /home/XXXXXX/public_html/_vti_pvt/service.pwd
AuthGroupFile /home/XXXXXX/public_html/_vti_pvt/service.grp

In the images folder is all the photos themselves, and the htaccess file for the watermark (when I have it in there, which is never until I can get this to work coz it stops my photoblog from displaying the photos!) and all it contains is this:

AddHandler watermarked .jpg
AddHandler watermarked .jpeg

Action watermarked /admin/wrapper.php

Should that read 'watermark' instead of 'watermarked'?

The wrapper.php file is completely untouched at the moment. Is that possibly my mistake? Does it need custom edits made to it?

[owen-b]

Seems like it's a problem with the htaccess - removing it from the images folder makes everything work again, even if watermark.png and wrapper.php are still in the admin folder...

Also, adding back in the gif and png lines to the htaccess file and putting it back in images makes no difference.

Hmm. Any ideas? I don't even know what htaccess files do, so I'm at a loss now!

Just to be totally clear, here's what I've done so far.

1) Created a watermark.png file in Photoshop and placed it in public_html/admin
2) Put the wrapper.php file, unedited in any way, in public_html/admin
3) Changed the .htaccess file and placed it in public_html/images

The .htaccess file contains the following and nothing else, not even blank lines:

AddHandler watermarked .jpg
AddHandler watermarked .jpeg
AddHandler watermarked .gif
AddHandler watermarked .png

Action watermarked /admin/wrapper.php

[owen-b]

Anyone got any thoughts?

Vernon Trent to the thread! Paging Vernon Trent!

[Vernon.Trent]

any updates on that, Owen?

[owen-b]

Well my hosting people really worked hard on this. They researched the script, tried it on different servers, all sorts, and they couldn't suggest or tweak anything that wuld make it work.

In the end they found an alternative script that does a very similar thing, but they cant make that work on the main page of my blog either. However, if you surf to the direct location of the image it does indeed display the watermark, but really badly. It's a PNG with transparency and the transparent elements show up as semi-transparent yellow. Yuk.

Basically, it doesn't work.