Repository navigation
Error when replying #635
Description
Replying to a post on Twitter returns these errors, after clicking 'publish'.
Warning: curl_setopt(): CURLOPT_FOLLOWLOCATION cannot be activated when an open_basedir is set in /nfs/c03/h06/mnt/56448/domains/blog.davidjohnmead.com/html/external/mention-client-php/src/IndieWeb/MentionClient.php on line 248
Warning: curl_setopt(): CURLOPT_FOLLOWLOCATION cannot be activated when an open_basedir is set in /nfs/c03/h06/mnt/56448/domains/blog.davidjohnmead.com/html/external/mention-client-php/src/IndieWeb/MentionClient.php on line 259
Warning: Cannot modify header information - headers already sent by (output started at /nfs/c03/h06/mnt/56448/domains/blog.davidjohnmead.com/html/external/mention-client-php/src/IndieWeb/MentionClient.php:248) in /nfs/c03/h06/mnt/56448/domains/blog.davidjohnmead.com/html/Idno/Common/Page.php on line 519
I assume it's related to #614 and #629
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
Activity
mapkyca commentedon Dec 18, 2014
Yup, all the same :)
Do you have access to your apache conf?
davidmead commentedon Dec 31, 2014
I don't think so. I hosting on a Media Temple Grid.
mapkyca commentedon Dec 31, 2014
This will (should) be fixed by #632, however it depends on merging a pull request in the upstream webmentions project first (indieweb/mention-client-php#16) so has been delayed a bit.
It's a bit clunky, but you could try applying both patches to the relevant projects.
Other than that, I think you're pretty much left with needing to disable the basedir directive in the apache conf.
davidmead commentedon Dec 31, 2014
OK. I guess I have to wait.
See my reply on #629. As it's a shared server I can't get to the apache conf.
davidmead commentedon Dec 31, 2014
I may try adding those edits in the new year. See if it makes a difference.
mapkyca commentedon Dec 31, 2014
Yeah, that's a common problem. It's also a common thing that third party plugins include their own Curl connectors (Flickr, etc) ... so I think we're going to be back here again, and adapting a number of projects to use Known's own webservices code.
Probably a good thing since that means it'll obey the proxy settings config enabling you to run over tor without leaking.
benwerd commentedon Jan 10, 2015
So in the same way that I'm talking about progressive enhancement to add queueing functionality to Known where you might not have the ability to run your own queue server, I'm thinking about farming off webmentions to a central service if you want. That way you don't need to worry about open_basedir or Apache configuration, we handle all the tricky bits, and you still get to own your own data on your own server.
davidmead commentedon Jan 10, 2015
I think that makes a lot of sense. Especially if you hope Known to be
adopted outside the indieweb community on shared servers.
David Mead
http://twitter.com/davidmead
http://davidjohnmead.com
http://dmwebsites.com
On Jan 9, 2015 9:01 PM, "Ben Werdmuller" notifications@github.com wrote:
benwerd commentedon Jan 10, 2015
We're leaning towards it as a strategy for Known the company. Then people who wanted to use a different publishing platform could potentially use the services too!
mapkyca commentedon Feb 6, 2016
Pretty sure this is fixed, closing.