open_basedir restriction proper plugin settings | Peter's Custom Anti-Spam for WordPress | Forum
Back to the custom anti-spam plugin page
Log In
Home
Topic RSS
1:56 am
Offline
In this section:
// Leave this as FALSE unless you have an open_basedir restriction on your server and can't get it removed. In that case, enter the server path to your blog (different from the site address!) like in the example below WITH a trailing slash.
// $cas_abspath = "/home/yourusername/public_html/blog/";
$cas_abspath = false;
The first cas_abspath line is an example that does not factor into the plugin. If you are going to enter the server path, it should look something like this:
// $cas_abspath = You can write anything on this line. It is the line below that matters.
$cas_abspath = "/home/peter/public_html/wordpress/";
In other words, DO NOT do something like this:
// $cas_abspath = "/home/peter/public_html/wordpress/";
$cas_abspath = true;
9:29 pm
Hi Peter, first of all congratulations for such a wonderful plugin... I just installed and, although the plugin is working, I need your help with an error message...
I installed the plugin and activated as instructed... went to Manage » Custom anti-spam and fount that the GD Library, Free Type and get_option are fine... but the open_basedir reads:
Your server has an open_basedir restriction on. Make sure you edit the $cas_abspath value in the plugin file to set the absolute server path to your blog (something like /home/peter/public_html/blog/).
Went to your Forum and found the instructions at open_basedir restriction proper plugin settings, so I changed $cas_abspath file - the second one :-) – to $cas_abspath = “/home/xxxxxxxx/public_html/wp-content/themes/default/â€;
But received the following error message...
Parse error: parse error, unexpected T_DEFAULT in /home/alospi86/public_html/wp-content/plugins/custom-anti-spam/custom_anti_spam.php on line 115
When changed back to false, the error disappears...
Thanks for your help... the blog url is http://www.alospiesdelacruz.com/... and sorry, I am using your new version 2.9.0 on WP 2.2...
11:57 pm
Offline
Did you use proper quotes? "/path/"
You could also try using single quotes: '/path'
If neither of those work, is the word "default" in your path for some reason?
If all of the above fails, e-mail me the plugin file (contact info on the right sidebar on theblog.ca).
Of course, if your plugin is working and it's only the diagnostic page that gives the error, there's no need to fix it, I suppose...
