Nothing Special   »   [go: up one dir, main page]

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when posting #629

Closed
davidmead opened this issue Dec 15, 2014 · 6 comments
Closed

Error when posting #629

davidmead opened this issue Dec 15, 2014 · 6 comments

Comments

@davidmead
Copy link

Posted a status update from my blog, clicked to share it with Twitter and Facebook and clicked publish.

The page, http://blog.davidjohnmead.com/status/edit, returned this error:

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: 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 refreshed the page, it submitted the form (I assume) again but still had this error. Editing the URL to http://blog.davidjohnmead.com/ revealed it had been posted twice.

screen shot 2014-12-15 at 12 59 31 pm

Facebook shows it once, then a second time with an instagram image from the previous entry.
screen shot 2014-12-15 at 12 55 45 pm

Twitter only seems to have posted it once.
screen shot 2014-12-15 at 12 56 16 pm

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@mapkyca
Copy link
Member
mapkyca commented Dec 15, 2014

The printed errors are related to #614, and will need an upstream fix (will add a note to this ticket). Basically curl won't follow redirects if safe mode or basedirs are set, because Reasons. This causes problems when Known makes any web services calls. The specific error is being thrown by the Pingback/webmention code which is pinging the links in your post... this is a third party module which will need to be patched.

If you're self hosted you could disable basedir in your apache config, which will stop the mention client throwing a shoe until it's fixed.

@davidmead
Copy link
Author

Thanks for the info. I am self-hosted, but not sure where to disable the basedir.

mapkyca added a commit to mapkyca/idno that referenced this issue Dec 15, 2014
@mapkyca
Copy link
Member
mapkyca commented Dec 15, 2014

@davidmead
Copy link
Author

Media Temple just informed me...

@davidmead Unfortunately, because the GRID is a shared service, the apache config file cannot be modified. Sorry! *DT

So I'll have to wait for a fix from @benwerd. Thanks for the help @mapkyca .

@mapkyca
Copy link
Member
mapkyca commented Mar 28, 2015

Is this still an issue?

@benwerd
Copy link
Member
benwerd commented Jan 29, 2016

This isn't an issue due to a change in Known. Closing.

@benwerd benwerd closed this as completed Jan 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants