Watermarking error after upgrade
 

I recently upgraded to 6.01 and had no problems uploading images to already created categories that existed before the upgrade, but when I created a new category, and tried to upload images to that category I get this error:

Error creating watermarked original! Error code: 1

Command: "/usr/bin/composite" -compose over -gravity SouthEast 1 '/home/mysite/public_html/gallery/data/9186/spacesiege1.jpg' '/home/mysite/public_html/gallery/data/9186/spacesiege1.jpg'

I've checked the chmodding of /gallery and /gallery/data and /gallery/data/9186/thumb and /gallery/data/9186/mini and /gallery/data/9186/medium

I am unable to check the chmodding of /gallery/data/9186 because I can't seem to find it in the long list of directories for all the categories I have. I'm pretty sure I have my server set to show 10,000 directories via FTP but the directory is only showing 5497 directories, so I assume it's not because my server is hiding it, probably just can't find it in there.

Can I get some help so that I can resolve this problem.

Thank you.

My response would be one of two things for you to check as that is a permissions issue without any hesitation there.

1. Since your using Imagemagick the watermark needs to be a gif and you need to have the correct path to that watermark in watermark options in admin.

2. You must check your data directory and make sure it is 777 permissions at every level. In one sentence above you note you have checked the directory but in the next sentence you say you cant find it so thats a big issue. You must find that directory and ensure it is 777 and all its subdirectories.

Watermarking has been working fine on previous pictures.

This problem only seems to happen on newly created categories after the upgrade.

I was able to finally find that directory and it IS chmodded to 777 as well as my data directory and all the subfolders of the 9186 directory. The thumb folder has the thumbnails in it too, if that makes a difference in troubleshooting.

Is safe mode on? Does uploading work fine without watermarking set to yes?

Feel free to actually post a site url for us to look at and a test login.

You have verified all these new categories in data exist and permissions exist?

I am having the same problem after a new clean install of 6.01. All data directories are chmod 777 with proper owner. Am using IM and .gif watermark with directory of
/home/wiscon/public_html/photopost/watermark.gif

I get the following:

Error creating watermarked original! Error code: 1

Command: "/usr/bin/composite" -compose over -gravity NorthWest 1,3,4,8 '/home/wiscon/public_html/photopost/data/506/nice_michigan_buck.jpg' '/home/wiscon/public_html/photopost/data/506/nice_michigan_buck.jpg'

I can upload photos without watermarks just fine.

Test account at http://www.wisconsinoutdoorsman.com

username: tester
password: monday15

I just don't get it.

Well if you can upload fine then there has to be an issue with the watermark. So what is the watermark your using? You sure its a path not a url you have in watermark options and that the image is not corrupt?

I've tried both png and gif files. The file is not corrupt. Any other ideas? Just check and triple checked my path. Tried a watermark image that I know works on another one of my websites with PP. Do you want the keys to my machine?

Sure you can send the info to support@photopost.com

Based on the error and that you can upload without a watermark something has to be off there in watermarking.

Please enclose direct paths to both your watermark images so I can test as well.

I fixed my problem by deciding to do the overlay watermarking with image protection. It now works. I don't know what was wrong before, but it was a different problem than wacnstac's because it worked fine in other categories, but had a problem in cats that were newly created in 6.01

Okay the error though remains it is a permissions error ERROR CODE 1 that is listed right on Imagemagicks support site.

So how do I go about fixing it? Because the directories are chmodded to 777, so I don't see what the problem is?

I still ask, because I see that there is a way to get images without my watermark simply by finding the path to the thumbnail and then removing the /thumb directory and anybody can get the images without the watermark.

I don't like that, especially since I create gaming wallpapers that I want my watermark left on as they float around the internet.

What else can be tried to fix the problem?

The overlay is working it could be a simple problem of your watermark image. The one you created and use for overlay works the one for permanent images did not. I have seen that before. I prefer using on the fly watermarks and all the secure features as in moving the large images below the webroot if your trying to protect images.

The thing is, the watermark works fine for categories that already existed before my upgrade to 6.01 but when I try to process the images in a category that was created after being upgraded to 6.01 it doesn't work and gives the error I mentioned. It shows the thumbnails on the bulk upload page, but when it tries to actually process the images is when it gives the error.

My watermark worked fine on my previous version of PP and I didn't change it. It's just a png with transparency.

Any other ideas I can try?

In Admin => Edit Categories make sure to edit your new categories and make sure you dont have any bogus watermark paths that would override your global watermarking options and cause issues.

Nope. I went back and looked through all the categories that were part of the path to the category I was having trouble with before I switched to "on-the-fly" watermarks and there is nothing in the watermark fields for any of the categories that should cause a problem. Only the master watermark is all that's set.

i would be glad to look and test if you send a proper admin login to support@photopost.com as well as a url.

Any resolution to this? I've been experiencing the EXACT same problem after upgrading to 6. Everything worked in the past without problem.

resolution to what? you would need to open your own support issue so we could look into what your issue might be.