Hello, Ive recieved an error (seen here > http://vivithemage.co.uk/blog/). Ive tried upgrading wassup but that creates a blank screen, and even if i deactivate wassup and remove it, the blog still shows a blank screen. Any help would be greatly appreciated. Thanks
Wordpress version: 2.5.1
Wassup version: 1.4.3
The "open-basedir restriction" error is a sign that your ISP host server is running in "PHP safe mode". This is incompatible with several Wordpress plugins, including Wassup 1.4.3 (though not WassUp 1.6). You need to call your ISP to change this restriction or you can deactivate all your plugins, install them again, then activate them one at a time, making sure your blog is not affected after each one. If you cannot access your Wordpress admin menu, you need to delete everything but Akismet from your plugins directory via ftp, beforehand.
You can learn how other Wordpress users have dealt with this problem in the Wordpress support forums.
I checked the server and it was not running in safe mode, ive also tried changing permissions of the wassup folder yet there has been no difference, any other suggestions? Thanks
I visited your blog and viewed the error. Your host server is definitely running in "PHP safe mode". This "PHP safe mode" restricts access to only the directories specified in your ISP's setting, in your case (/home/vivi/, /tmp, and /usr/local/lib/php/). A support tech at your ISP needs to see this error because it looks like there may be a server misconfiguration problem where the allowed paths does not match the real path of your own site. If you can, copy and paste the error in an email and send it to your ISP support email address. That may be the only way to guarantee it will be seen by someone who understands server configuration.
Because of this problem, Wassup is unable to access the default path for PHP session_save_path. Your getting a blank screen even after deactivating Wassup confirms that this problem goes beyond Wassup and is on your host itself.
I am not optimistic that this will help, but you could try entering a different "save path" value in Wassup Options. Go to the Wassup==>Options or type the URL "http://yoursiteurl/blog/wp-admin/admin.php?page=wassup-options" in your browser. Then go to the "Manage Files&Database" tab, and enter a new value for Temporary files location folder. If the value is "/tmp", you need to change it to something like "/usr/home/vivi/tmp". If the value is "/var/tmp", change it to "/tmp", instead, then save. Good luck.
Thanks for the detailed reply. I checked safe mode and it says its off, if you check out http://vivithemage.co.uk/phpinfo.php you can see for yourself. I tried changing the manage files and database tab, but i couldnt find it. I thought it could be this http://vivithemage.co.uk/php-temp.png
Should i change that path, because i could try to create a local php.ini file which should override the system wide on. What do you think?
The "Temporary files location folder" option may not have been available in Wassup 1.4.3, so setting session.save_path in php.ini may be your only way to change that value.
I checked your phpinfo output and saw that "open_basedir" is set at the local level. "open_basedir" is one of the configuration directives used by Safe mode. If it is turned on, then your PHP has restricted directory access, even if the "save_mode" directive itself is turned "off". Please make the following changes to your php.ini file:
; php.ini local settings:
;
; comment out "open_basedir" by adding the semicolon in front of it
; open_basedir = "/home/vivi/:/tmp:/usr/local/lib/php/"
;
;for Wordpress session and WassUp plugin
session.save_path = "/tmp" ; use /home/user/vivi/tmp if /tmp doesn't work
;
; Use error_reporting = 6143 when debugging
error_reporting = 6143 ; E_ALL error reporting level (for debugging only)
Another thing you could do is simply delete the "wassup" folder from your wordpress plugins directory. That removes Wassup from the equation and you can move on to find the actual source of the problem. Good luck.
You must log in to post.
