-
-
Notifications
You must be signed in to change notification settings - Fork 196
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 replying #635
Comments
Yup, all the same :) Do you have access to your apache conf? |
I don't think so. I hosting on a Media Temple Grid. |
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. |
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. |
I may try adding those edits in the new year. See if it makes a difference. |
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. |
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. |
I think that makes a lot of sense. Especially if you hope Known to be David Mead http://twitter.com/davidmead On Jan 9, 2015 9:01 PM, "Ben Werdmuller" notifications@github.com wrote:
|
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! |
Pretty sure this is fixed, closing. |
Replying to a post on Twitter returns these errors, after clicking 'publish'.
I assume it's related to #614 and #629
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: