Open_basedir is a PHP security restriction added to either php.ini or a site’s virtual hosts file on the server. It prevents PHP from accessing directories above the directory specified by the open_basedir directive. Not sure the solution in this case but I wouldn’t lift the restriction. There’s a little more about this here.
As a basic explanation,
if the path to your site relative to the server is
/var/www/your-site/
and WordPress is installed in the site’s root directory (/your-site/) then the path to wp-content would be
/var/www/your-site/wp-content/
and the plugin would be stored in
/var/www/your-site/wp-content/plugins/wpsearch/
Open_basedir would normally be configured in the virtual host file for the site to prevent PHP scripts from looking outside of the site’s root directory. That’s to say
php_admin_value open_basedir "/var/www/your-site/"
This keeps hackers from making a mess of all sites on the server if they manage to upload a PHP shell below the ‘/your-site/’ directory.
Are you running WordPress on a home or dedicated server?
Hello, my WP runs on shared hosting without any difficulties (the only problem is safe_mode set on “true” for some cache plugins). The (sub)folder(s) structure is default.
Frankly, “I am searching for WP search plugin” REALLY capable to find the data strings “hidden” both in shorcodes and ALT/TITLE/CAPTION parameters. Your plugin seems to be an interesting improvement of ugly default WordPress search, but I am not sure if is able to do this “deep search” (in the current version :-))
Thanks for your message, with best regards, Joo
hi Joo-Joo. This isn’t one of my plugins. You can easily integrate Google Custom Search into your site. There are several search plugins you can use too. Such as
http://wordpress.org/extend/plugins/search-everything/
and
http://wordpress.org/extend/plugins/relevanssi/
The developer of this plugin (WP Search) probably isn’t aware of your question. Developers are not automatically advised of questions posted at WordPress.org about their plugins.
