I have been using WordTwit plugin from Brave New Code for a few months now, but ever since I’ve upgraded to FireFox 3, I have been having problems with it.
For those that do not know, WordTwit is suppose to send a Tweet message on Twitter letting everyone who follows you know that you have a new blog entry.
Alas lately it hasn’t been sending out any tweets when I have added a new blog post. I get the following error instead:
Warning: curl_setopt() [function.curl-setopt]: CURLOPT_FOLLOWLOCATION cannot be activated when in safe_mode or an open_basedir is set in /home/gusdigi/public_html/wp-content/plugins/wordtwit/wordtwit.php on line 31
Warning: Cannot modify header information – headers already sent by (output started at /home/gusdigi/public_html/wp-content/plugins/wordtwit/wordtwit.php:31) in /home/gusdigi/public_html/wp-includes/pluggable.php on line 694
Granted I’ve asked people on Twitter to help, but have gotten no response yet, so I’m asking anyone out there again if they can help me out on this one.
What version of PHP is running on your web server?
Currently running PHP Version 5.2.6 as a “default”.
Since version 4.4.4, CURLOPT_FOLLOWLOCATION has been disabled when in safe mode due to a security vulnerability. I am running 5.2.6 also, but do not have the error as safe mode is off. This might require that Duane tweeks the plugin once he returns from vacation; but in the meantime you can turn off safe mode by editting your php.ini file.
Thanks Gregg,
Being un-geeky, I have no idea how to do that
Do you have full access to your webserver? If you do, you should find a file called php.ini in the root folder. Open it in a text editor, and do a search for the word safe . In my php.ini, I found the following:
; Safe Mode;
safe_mode = Off
The semi-colons make the line a comment only. The final line is the one to change, your’s will probably say
safe_mode = Offand you should change it to Off like mine.
Crap, I meant to say yours will likely be
safe_mode = ON.And ignore the line numbers that the “code” tag has added in.
I’ve tried to search for the php.ini file but couldn’t find it anywhere…alas I did say I wasn’t geeky enough
I think I started to experience the problem when I switch servers on BlueFur too. The old one was PHP4, whereas the new one is PHP5. I guess we have to wait for an update for the plug-in.