-
-
Notifications
You must be signed in to change notification settings - Fork 195
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
Comments
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. |
Thanks for the info. I am self-hosted, but not sure where to disable the basedir. |
Refs: indieweb/mention-client-php#15 (requires) Refs: idno#629 Refs: idno#614
Media Temple just informed me...
So I'll have to wait for a fix from @benwerd. Thanks for the help @mapkyca . |
Refs: indieweb/mention-client-php#15 (requires) Refs: idno#629 Refs: idno#614
Is this still an issue? |
This isn't an issue due to a change in Known. Closing. |
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:
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.
Facebook shows it once, then a second time with an instagram image from the previous entry.
Twitter only seems to have posted it once.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: