- Messages
- 2,867
- Reaction score
- 165
- Points
- 63
I recently updated to Wordpress 2.9 and began receiving an error like:
Warning: curl_setopt() [function.curl-setopt]: CURLPROTO_FILE cannot be activated when in safe_mode or an open_basedir is set in /home/(user)/public_html/wp-includes/http.php on line 1302
There's an earlier thread covering this somewhere. Refreshing the page does work for the dashboard however, I'm trying to use the XML Sitemap Generator plugin.
I never had a problem with Wordpress 2.8 but it looks like the sitemap can't successfully update with that error appearing. When I try to rebuild the sitemap manually, I get a list of 6 of the same error I pasted above (alternating between line 1302 and 1303). Even though it says the sitemap was built successfully, all posts I added since updating to 2.9 aren't part of the Sitemap.
http://www.techairlines.com/sitemap.xml
Is there any way to fix this? This never occurred in Wordpress 2.8.
Update: After some research, it seems to be a bug with the new release. I applied the patch some person provided here: http://www.semiologic.com/2009/12/21/wp-2-9-three-bugs-and-how-to-fix-them/ and it works.
(Sorry, I can't figure out how to delete this thread.)
Warning: curl_setopt() [function.curl-setopt]: CURLPROTO_FILE cannot be activated when in safe_mode or an open_basedir is set in /home/(user)/public_html/wp-includes/http.php on line 1302
There's an earlier thread covering this somewhere. Refreshing the page does work for the dashboard however, I'm trying to use the XML Sitemap Generator plugin.
I never had a problem with Wordpress 2.8 but it looks like the sitemap can't successfully update with that error appearing. When I try to rebuild the sitemap manually, I get a list of 6 of the same error I pasted above (alternating between line 1302 and 1303). Even though it says the sitemap was built successfully, all posts I added since updating to 2.9 aren't part of the Sitemap.
http://www.techairlines.com/sitemap.xml
Is there any way to fix this? This never occurred in Wordpress 2.8.
Update: After some research, it seems to be a bug with the new release. I applied the patch some person provided here: http://www.semiologic.com/2009/12/21/wp-2-9-three-bugs-and-how-to-fix-them/ and it works.
(Sorry, I can't figure out how to delete this thread.)
Last edited: