Watermark not showing any more

yanzen

On ZP 1.4.4.3 I uploaded a different watermark and it is not showing. When I switch to the default ones or to my old one, they are not showing any more either. My old one did show until now, even on newly uploaded images.

What I did:

• Upload wm2.png to /plugins/watermarks
• switch from wm1 to wm2 in options → image
• Clear /cache and browser cache again and again
• switch back and forth between wm1.png, wm2.png and default watermarks
• Check filenames in /cache/... – they have the correct wm1 or wm2 alright, depending on which I picked
• chmod /cache and /plugins/watermarks to 777, 755, 644,...

Anything I missed? Thanks!

acrylian

Did you look into the error logs? The image could be corrupt or not being processed because of being to large for example.

sbillard

First, unless you purged your cache during the upload the images did not change, so if they were watermarked that should have remained.

Have you looked directly at the images in the cache? Do they have the watermark on them? How about if you use one of the supplied watermarks, does it show?

yanzen

Thanks for your suggestions. Just to be sure I also switched to default theme and tried the hole routine, but no look.

@acrylian: No, haven't looked at logs.

debug-1.log consists of the same two Notices over and over again (6MB of it), only the dates change:

`
{4547:Sat, 02 Mar 2013 22:14:53 GMT}
NOTICE: Undefined variable: galleryactive in /themes/frokost/header.php on line 359
include called from include (news.php [1])
from index.php [93]
{4551:Sat, 02 Mar 2013 22:14:59 GMT}
NOTICE: Undefined variable: videopresent in /themes/frokost/album.php on line 154
include called from index.php [93]
`
debug.log is pretty much the same. I guess I should look into those but it seems they're unrelated. Are there other logs I could look into? security.log didn't reveal anything either.

File too large or corrupt seems unlikely as after switching to the new one and back the old watermark stopped working, too. File sizes are pretty much equal.

@sbillard cleaned cache again and again. Downloaded image from cache, no watermark on them. Supplied ones don't show either.

acrylian

Hm, no idea of those two errors but those are theme dependent. I just tried watermarks with the current master and it does work for me. Can you try the master from GitHub maybe?

yanzen

Yes, sure. Will try over the weekend.

By the way: you guys are not only producing a fantastic piece of software, you also are the best in supporting it! Thanks a lot!

acrylian

Thanks very much!

yanzen

Just had a go, downloaded »1.4.5 Development builds (GitHub)« from the frontpage but get a bucket full of errors. Before I start digging, did I download the right thing? Do I have to proceed any different from a regular zp installation?

sbillard

That build should not give you a "bucket full of errors", but is probably not the one you wanted to try. You want the "master" build. There are links to these on the downloads page of the website, select the support release.

yanzen

Thanks a lot. The errors had nothing to do with ZP but were all due to inappropriate chmodding, which, by the way, will one day surely drive me nuts – but that is an entirely different story.

I installed the support master on a test-domain and sure enough watermarking works like it should. I haven't really grasped the difference in between support master and the release version, as version numbers seem to be the same. Should I wait for the next release? Or can I use support master on my live site?

Thanks again, have a good weekend!

acrylian

Master -> Support build becoming the next bugfix/maintainance release of the current stream. This gets all fixes as needed and discovered of the current release but no new features. In this case this is currently 1.4.4.3 and will become therefore 1.4.4.4 later on. By testing these you help use to lower possible new or old errors/issue to return.

Dev build -> This is the developlement of the next release, in this case 1.4.5, that gets all the new features planned.

Edit: I have updated the installation page with this additional infos as well

yanzen

Ok, cool. Thanks for explaining. I indeed found a small z-index-issue while testing (submitted it on github).

So I'll just wait for 1.4.4.4 and see if that fixes the watermark issue.

Cheers!

acrylian

Well, actually you should try the support build now so there is no watermark issue!.:-)

yanzen

all the .gitignore-files are not an issue?

I am a bit reluctant using it on the live site as I had errors on the test site once I switched to my custom theme. some calls to undefined functions, like printLatestNews and printCustomMenu – but maybe they go away if I use the proper database with news and custom menu enabled?

acrylian

Those are just git related files and do nothing actually.

OF course testing on a live site is never recommended although the support build should not cause issues in regard to compatibility.

printLatestNews and printCustomMenu are plugin based functions (Zenpage and menu manager) so you naturally get errors if you have no checks for function_exists() in your custom theme.

yanzen

I'm trying it now on my test-site. The thing is that my custom theme has grown organically over the past years, which, in all honesty is just a euphemism for »bit by bit I turned it into an undocumented, bloody mess«. I learned a lot but I don't want to put too much strain onto it.

Thanks again, will let you know if other issues turn up.

acrylian

Yeah, that "growing" does happen easily with a lot of stuff!