Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I set a Feed. When I manually run cron.php to test Aggre, it returned the below error:
warning: curl_setopt() [function.curl-setopt]: CURLOPT_FOLLOWLOCATION cannot be activated when in safe_mode or an open_basedir is set in /home/webclewc/public_html/modules/aggregation/aggregation.module on line 1090.
Is it an issue with Aggregation module, or the PHP setting of my server (I user a virtual host). I searched Web but got some conflicting points.
Whatever the cause, I will appreciate it greatly if you are so kind to give any tips.
Comments
Comment #1
askit CreditAttribution: askit commentedWhen I tried it again, the problem didn't repeat. So it's OK now but I don't know why...
Comment #2
tobedeleted CreditAttribution: tobedeleted commentedI'm getting the exact same error when cron runs:
curl_setopt() [function.curl-setopt]: CURLOPT_FOLLOWLOCATION cannot be activated when in safe_mode or an open_basedir is set in /web/example.com/www/sites/all/modules/aggregation/aggregation.module on line 1090.
Anyone else seen this issue? I'm new to using aggregation, any input welcome.
Comment #3
BKWill CreditAttribution: BKWill commentedThis may be useful. I've ran into this problem as well and it seems to only occur when the site is operating in off-line mode or what is referred to in the warning as safe-mode. I had my installation set to maintenance while I was setting up the module. Taking my site online removed the error.
Comment #4
BKWill CreditAttribution: BKWill commentedI did some checking and this seems to be related to an issue with PHP5, I'm not an expert but here's a similar issue and temporary solution that was presented for the FEED API module.
http://drupal.org/node/327561
Comment #5
Ashraf Amayreh CreditAttribution: Ashraf Amayreh commentedSolved in next version of the module. In general, safe_mode or open_basedir are somewhat bad things, I implemented a sort of workaround, but if you can turn off these two directives it's definitely preferred.