warning: curl_setopt() [function.curl-setopt]: CURLOPT_FOLLOWLOCATION cannot be activated when in safe_mode or an open_basedir is set in /home/egazetec/public_html/sites/all/modules/feedapi/parser_common_syndication/parser_common_syndication.module on line 177.

this is the error I get when I create or refresh a feed. How can I correct this ?

Comments

alex_b’s picture

alex_b commented
Title: Getting error » Error: "CURLOPT_FOLLOWLOCATION cannot be activated when in safe_mode"
Component: Code feedapi (core module) » Code parser_common
Status: Active » Postponed (maintainer needs more info)

Looks like curl is available but PHP is running in safe_mode. Should we fall back to drupal_http_request if PHP is in safe_mode? I also wonder whether this issue affects 1.x as well.

Could you try the developer snapshot of FeedAPI and see whether the bug persists? Keep in mind to back up before that and don't use the developer snapshot in production, it is too buggy at this point.

drupallogic’s picture

drupallogic commented

I just updated to 1.7-beta1. Errors are gone.

But I realize that "Promoted items: " is also gone. This is very disappointing.

aron novak’s picture

aron novak
Primary language Hungarian
Location Hungary, Budapest
commented
Status: Postponed (maintainer needs more info) » Fixed

Well, "promoted item" setting was the source of the most annoying problems and complainments: http://drupal.org/node/246604

drupallogic’s picture

drupallogic commented

I'm very upset as "promoted item" is cruical for me. I have several feeds and one of them has allways the coming day's dates. so this feed's news allways stay at top and no other feed can be seen on the front page. I was setting this feed's feed's promoted item to 0 so it was never going to front page. Can't you add it as an option to next release ???

well there is something strange with FeedAPI 1.6 actually. I have some old sites without this "CURLOPT_FOLLOWLOCATION cannot be activated when in safe_mode" error which I use FeedAPI 1.6. there is something strange but I couldn't figure out.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.