BUMP!
Still not working, or at least the issue is back in WordPress 3.8!
Yeah, well. Maybe no need to iterate but same problem here. http://www.1pstart.net. But since nothing has been updated I’m guessing Twitter may have changed something in their API or is just having a temp issue.
But I turned the option off and it solved the problem, like you said. Thanks!
Well, it’s not my server, but a friends but from what i’ve read neither turning safe mode off nor making changes to open_basedir is recommended.
Is there any serious issues with setting CURLOPT_FOLLOWLOCATION to false? That at least solved the issue, but I’m not exactly sure what the other problems may arise if I do that.
