Hi,
Thank you for reporting.
What version of PHP and WP are you using?
Ok, I will check the issue and come back with a solution/fix. So please be patient until tomorrow.
PS: the error you just noticed should never happen but with this myriad of environments you never know what might go wrong.
The new published version (0.2.2-3) should fix the symptom you mentioned. Perhaps the plug-in was in conflict with some other plug-ins you might have already on your WP installation. That is more a guess.
Anyway, just install the new version and let me know if it worked out.
OK, I have updated:
`Warning: file_exists() [function.file-exists]: open_basedir restriction in effect. File(/tmp) is not within the allowed path(s): (/users/jdktst/www:/users/_temp/jdktst) in /users/jdktst/www/wp-content/plugins/wp-mybackup/config/config-fixes.php on line 56′
BTW: this side is a freehoster with quite a lot restrictions.
Yes, the message is just an PHP warning, it’s not harmful. It tells us that your hosting company limited your file access to your folder only.
Read more here.
Basically the plug-in just checks at the beginning what resources it may use (like the temporary directory) and trying to access a folder outside of the access area (/tmp is outside of your website folder) triggered that kind of warning.
I could hide that warning but I let it intentionally that way so as you know you have some limitations on the host the WP is installed.
Probably their php.ini has the error reporting option like this:
error_reporting = E_ALL
So this can be fixed (as well as any PHP warning) if you just upload a php.ini file in the website root with only one single line where the error_reporting option is set like this:
error_reporting = E_ALL & ~E_NOTICE & ~E_WARNING
which basically says report all errors but notices and warning.
You can live without this settings, though.
That being said I regard this topic as closed.
