Updatred to Wp 2.9 and get this error – Warning: curl_setopt() [function.curl-se

Dear everyone,
Having the same problem just after upgrade to WP 2.9

To fix it, you just need to modify the script as pointed out by eric.fournier

Edit /wp-includes/http.php and change the if statement on line 1300 to this:

if ( defined( ‘CURLOPT_TIMEOUT_MS’ ) ) {
// EDF – The option doesn’t work with safe mode or when open_basedir is set. More
// research is probably necessary however this seems to fix the problems I was
// seeing in the “WordPress Development Blog” section of the Dashboard.
if ( !ini_get(‘safe_mode’) && !ini_get(‘open_basedir’) ) {
$timeout_ms = (int) ceil( 1000 * $r[‘timeout’] );
curl_setopt( $handle, CURLOPT_CONNECTTIMEOUT_MS, $timeout_ms );
curl_setopt( $handle, CURLOPT_TIMEOUT_MS, $timeout_ms );
}
} else {
$timeout = (int) ceil( $r[‘timeout’] );
curl_setopt( $handle, CURLOPT_CONNECTTIMEOUT, $timeout );
curl_setopt( $handle, CURLOPT_TIMEOUT, $timeout );
}

The only problem now is, I have to modify the said code one-by-one, manually for each websites which I am currently handling with.

Anyway, thank you very much for sharing the way how to resolve this matter.

https://www.arifabdull.com

An update has been released for people using Google XML Sitemaps. Hopefully that will fix it for those users of the plugin.

I seem to get this intermittently now

I just re-cloned my Test System from my Production system, did an upgrade to 2.9, and the “Failed to write session data” warnings disappeared, without any sign of the curl errors. Admittedly, I don’t use the XML Google sitemap plug-in, but I do use cforms.

The problem is from the XML Google sitemap, that’s why when you want to publish or update a post you get that error message, because after updating or publishing, the plugin is called to rebuild the sitemap automatically.. I disabled the plugin and things got back to normal.. Try it and let me know..

@ Zakshow.

Thanks for your advice. I disabled the XML Google sitemap and all works fine again.

Robert

https://www.semiologic.com/2009/12/21/wp-2-9-three-bugs-and-how-to-fix-them/

The problem at my site with this error is the GD Simple Widgets plugin.

FYI:
Even after changing code of http.php and Google sitemap update, error is still there.

WordPress Development Blog Configure
Warning: curl_setopt() [function.curl-setopt]: CURLPROTO_FILE cannot be activated when in safe_mode or an open_basedir is set in /home/putocomc/public_html/some.com/wp-includes/http.php on line 1302

Warning: curl_setopt() [function.curl-setopt]: CURLPROTO_FILE cannot be activated when in safe_mode or an open_basedir is set in /home/putocomc/public_html/some.com/wp-includes/http.php on line 1303

WordPress 2.9, oh so fine 19, December, 2009
I want to make you mine, all the time… oh wait. Hello. I’m here on behalf of the entire WordPress development team and community to announce the immediate availability of WordPress version 2.9 “Carmen” named in honor of magical jazz vocalist Carmen McRae (whom we’ve added to our Last.fm WP release station). You can upgrade [...] […]
2010: A Theme Odyssey 18, December, 2009
After the video from the core team meetup was posted, the topic that seemed to get the most attention on Twitter and various community sites was Matt’s announcement that there would be a new default theme in 2010, so I thought I’d start with that as the first of the meetup summaries. When Kubrick was bundled [...] […]

another one, it is a clean install with no plugin added just a theme. definitely there is an error or at least unexpected problem with wordpress 2.9 i expect wordpress team to read this and tell us about the importance of it.

@userword: see my above comment. It’s one of three known WP 2.9 bugs, which are addressed in the coming 2.9.1.

When I encountered the curl issue after upgrading to 2.9 I overwrote both php files (default-widgets and http) with their 2.86 versions and all’s been well.

Should I leave it be or upload the 2.9 versions and the patches?

@userword: see my above comment. It’s one of three known WP 2.9 bugs, which are addressed in the coming 2.9.1.

i thought you were guessing not that you were sure about it. Nice to hear that they will fix it in next release.

@eric.fournier: thanks for the tip. worked slick. i am a virgin to wp with my first install today. saw the error codes and panicked. all good now. going to load a graph paper press theme next. cheers, steve.

Just do it yourself or ask your provider to change the following settings in php.ini file where your website is running:
open_basedir off
safe_mode off