Page 1 of 1
[SOLVED] Products module issue
Posted: Thu Sep 02, 2010 1:45 am
by vlad-m
I am trying to add a custom field in the Products module. The filed is of image type. But everytime I want to add or modify existing product by adding a photo, I get the following message
Field customfield: Preprocessing of the uploaded file failed - WATERMARKING: Watermarking is not properly configured
Problems were encountered when dealing with one or more custom fields. The action has completed successfully, however you should investigate and correct these problems.
Could somebody please help me
Re: Products module issue
Posted: Thu Sep 02, 2010 4:09 am
by pedes
Re: Products module issue
Posted: Sat Sep 04, 2010 2:08 am
by vlad-m
I resolved the problem by updating Calguys Module Extensions
Just change Graphics Settings: choose yes for "Watermarking uploaded images" and yes for "Create thumbnails"
Re: [NOT SOLVED] Products module issue
Posted: Mon Nov 22, 2010 10:12 pm
by spcherub
I had the same problem but the fix suggested by vlad-m did not fix the problem.
I am using CMSMS 1.9 and CGE 1.21.3
Thanks.
Re: [SOLVED] Products module issue
Posted: Mon Nov 22, 2010 11:41 pm
by pukka
spcherub could you describe your problem in a bit more detail.
Thanks.
Re: [SOLVED] Products module issue
Posted: Tue Nov 23, 2010 3:30 am
by spcherub
@pukka - the problem is the same as reported by the original poster, so I quote verbatim:
I am trying to add a custom field in the Products module. The field is of image type. But everytime I want to add or modify existing product by adding a photo, I get the following message
Field customfield: Preprocessing of the uploaded file failed - WATERMARKING: Watermarking is not properly configured
Problems were encountered when dealing with one or more custom fields. The action has completed successfully, however you should investigate and correct these problems.
I was able to hunt down down the line in the Product module code that calls the watermarking function and comment it out which lets me upload images fine for now, but that is more of a workaround than a fix.
Thanks,
Sanjay