Open Basedir Errors after updating to 3.3
-
Hi, after I updated to 3.3 I get errors when I go to Permalinks in the Dashboard like:
Warning: file_exists() [function.file-exists]: open_basedir restriction in effect. File(/var/customers/webs/turbo/.htaccess) is not within the allowed path(s): (/var/customers/webs/turbo/whiterabbithole.org/:/tmp/) in /var/customers/webs/turbo/whiterabbithole.org/whiterabbithole/wp-admin/options-permalink.php on line 132 Warning: is_writable() [function.is-writable]: open_basedir restriction in effect. File(/var/customers/webs/turbo) is not within the allowed path(s): (/var/customers/webs/turbo/whiterabbithole.org/:/tmp/) in /var/customers/webs/turbo/whiterabbithole.org/whiterabbithole/wp-admin/options-permalink.php on line 132 Warning: is_writable() [function.is-writable]: open_basedir restriction in effect. File(/var/customers/webs/turbo/.htaccess) is not within the allowed path(s): (/var/customers/webs/turbo/whiterabbithole.org/:/tmp/) in /var/customers/webs/turbo/whiterabbithole.org/whiterabbithole/wp-admin/options-permalink.php on line 132 Warning: file_exists() [function.file-exists]: open_basedir restriction in effect. File(/var/customers/webs/turbo/.htaccess) is not within the allowed path(s): (/var/customers/webs/turbo/whiterabbithole.org/:/tmp/) in /var/customers/webs/turbo/whiterabbithole.org/whiterabbithole/wp-admin/includes/misc.php on line 133 Warning: is_writable() [function.is-writable]: open_basedir restriction in effect. File(/var/customers/webs/turbo) is not within the allowed path(s): (/var/customers/webs/turbo/whiterabbithole.org/:/tmp/) in /var/customers/webs/turbo/whiterabbithole.org/whiterabbithole/wp-admin/includes/misc.php on line 133 Warning: is_writable() [function.is-writable]: open_basedir restriction in effect. File(/var/customers/webs/turbo/.htaccess) is not within the allowed path(s): (/var/customers/webs/turbo/whiterabbithole.org/:/tmp/) in /var/customers/webs/turbo/whiterabbithole.org/whiterabbithole/wp-admin/includes/misc.php on line 133
I’ve got a second WordPress Site on the same server , with the exact same properties, but there is now open basedir error ( yes for security open basedir is on , on both websites ).
When I looked at the google sitemap plugin I saw that
Detected Path: /var/customers/webs/myname/sitemap.xml
is different to the website where everything is fine:
Detected Path: /var/customers/webs/myname/wordpresswebsite1/sitemap.xml
I think that could be the problem, but why ?
And how can I change it ?Thanks a lot, I couldn’t find an answer on google.
Viewing 3 replies - 1 through 3 (of 3 total)
Viewing 3 replies - 1 through 3 (of 3 total)
- The topic ‘Open Basedir Errors after updating to 3.3’ is closed to new replies.