WordPress 2.9 CURLPROTO_FILE bug

Merry Christmas to everyone and an upcoming happy new year! I hope you’ve got all your reservations because by this time, all of the good spots may already be fully booked. ;)

As for WordPress, it recently released upgrade version 2.9. Joyful as it sounded, it seemed there was a bug in it.

Warning: curl_setopt() [function.curl-setopt]: CURLPROTO_FILE cannot be activated when in safe_mode or an open_basedir is set in /home/domain/public_html/domain/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/domain/public_html/domain/wp-includes/http.php on line 1303

It’s not really a security flaw so don’t fret if you’ve upgraded too. Plus, some are saying its plugin conflicts but the majority has concluded it’s a core bug.

And not to worry, WordPress 2.9.1 should be out soon (hopefully before the new year) and this bug would’ve been squahed. :)

P.S.: I just noticed it’s affecting my Twitter and Delicious plugins too. :(

P.P.S.: Also found, it’s messing with scheduled publishing.

Comments

Have something to say? Leave a comment



View Comments to “WordPress 2.9 CURLPROTO_FILE bug”

  1. Response #1 by Wordpress 2.9 CURLPROTO_FILE bug | Websites Made Simple | Wordpress Marketing on December 28th, 2009

    [...] Go here to read the rest: WordPress 2.9 CURLPROTO_FILE bug | Websites Made Simple [...]


Other articles you should have read: