Please help I get this error since installing the script on every page on my site:

Warning: file_exists() [function.file-exists]: open_basedir restriction in effect. File(/cache/imagenes10d233bad6453f71c651ef12637a2b9cjpg) is not within the allowed path(s): (/home/tchncnwe:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/tchncnwe/public_html/mambots/content/plugin_jw_sigpro.php on line 285

Warning: file_exists() [function.file-exists]: open_basedir restriction in effect. File(/cache/imagenesd81fe0473327ce3921439f1a00058743jpg) is not within the allowed path(s): (/home/tchncnwe:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/tchncnwe/public_html/mambots/content/plugin_jw_sigpro.php on line 285

Warning: file_exists() [function.file-exists]: open_basedir restriction in effect. File(/cache/imagenes0f1d0d2a902b171860023ef9c02b5a99jpg) is not within the allowed path(s): (/home/tchncnwe:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/tchncnwe/public_html/mambots/content/plugin_jw_sigpro.php on line 285

My url is: www.techno.com.mx

Thanks

Resolved it removing the domain from cpanel whm tweak security open base dir protection.

Thanks anyway

Can I change this in the current version (1.2) myself? Because rigth now I can not use this gallery.

Thanks,

Mark

Sorry, that didn't solve the problem. Still I get the errors.

Thanks,

Mark

That did the trick! Yes I have contacted my host on this. They told me that the error was the result of trying to write / read from locations that are not allowed.

Thanks,

Mark

Damn hosting restrictions!  ;D

Anyway, we hope to address that in 1.3, by making the code more flexible to work on such environments.  ;)

Just thought I would let you know I had the same problem as the OP turned out the problem was due to a bug in sig_pro.  The only effect of having open_basedir enabled is that it showed the bug for what it was.

The diff is as follows:
As you can see the original file misses out '$mosConfig_absolute_path' this causes it to generate the wrong path which is why it is (otherwise) inexplicably outside of the allowable open_basedir directories.  You will also notice that it was missing a "." before the $format.  Either of these bugs will prevent the thumbnail check from working and cause the thumbnail to be generated every time.

I know you were joking but I have to say it: Neither open_basedir, nor error reporting are 'damn hosting restrictions'.  Open_basedir is very useful, primarily as a security measure - even in a non-shared environment you would never want your web server to have access out of the document root, some temp folder and maybe a libs folder.  Open_basedir also has the benefit of picking up some bugs that might not be spotted otherwise :P.  Error reporting is clearly beneficial for obvious reasons, though you probably wouldn't want it on a production server.