[nodebb-plugin-blog-comments] Blog Commenting Engine (Ghost, Wordpress widget)
-
Hmm, are you logged in as admin on your NodeBB? Also check your console when you refresh your WP article, and let me know if you run into any errors
-
@psychobunny
Ok, realised my error...Didn't change your.nodebb.org to my own website, now I have.
Think it may be because Koding can't write to apache.
New Errors:
Uncaught TypeError: Cannot assign to read only property 'className' of 0 wordpress.js:89 GET http://a5mith.kd.io/api/get_post/?post_id=1 404 (Not Found) wordpress.js:166XHR.onload wordpress.js:166 Unable to access API. Please install the JSON API plugin located at: http://wordpress.org/plugins/json-api
I have the plugin installed.
As an additional bit of feedback, comma delimited may run into issues further down the line, as it's not abundantly clear that if I have 10 blogs, but only 1 of them should go into a different category. If I'd have to do 9 comma delimited categories of where the first 9 go, then 1 for the last, or if it will post to them both. May be worth using a similar form to baris RSS plugin. So each blog has it's own fields.
When I click Publish anyway, i get
Can't set headers after they are sent. at ServerResponse.OutgoingMessage.setHeader (http.js:689:11) at ServerResponse.header (/home/a_5mith/35hz/node_modules/express/lib/response.js:595:10) at ServerResponse.send (/home/a_5mith/35hz/node_modules/express/lib/response.js:143:12) at ServerResponse.json (/home/a_5mith/35hz/node_modules/express/lib/response.js:229:15) at /home/a_5mith/35hz/node_modules/nodebb-plugin-blog-comments/library.js:153:10 at Object.Topics.post (/home/a_5mith/35hz/src/topics/create.js:89:11) at /home/a_5mith/35hz/node_modules/nodebb-plugin-blog-comments/library.js:135:11 at /home/a_5mith/35hz/node_modules/async/lib/async.js:592:17 at done (/home/a_5mith/35hz/node_modules/async/lib/async.js:135:19) at /home/a_5mith/35hz/node_modules/async/lib/async.js:32:16
-
The second error is happening because it can't access data found at:
http://a5mith.kd.io/api/get_post/?post_id=1You said you installed the JSON API plugin, but did you activate it? (I'm actually not sure if you need to activate it)
-
@psychobunny Yepp, activated, even went in and activated all the parts of the plugin, to make sure it wasn't that.
I'll delete it and try again. It's possibly koding at fault. I'll throw together a quick droplet and test that way.
Ok, got this working on Digital Ocean, had the same error. But this plugin won't work if you use post_id rather than pretty permalinks. I couldn't change this on koding as wordpress didn't have write access to htaccess. However this now works on Digital Ocean.
Thanks a lot.
-
I'm working on a new version that will be cross-compatible with any CMS, etc. It won't be for a while because I'm a bit busy with the new theme and stuff, but yeah, I'm glad that you figured it out
EDIT: I'm not 100% sure what you mean tbh, I only had a chance to test it out on my own WP blog. So if you don't use pretty permalinks, this will not work?
-
The default permalink in Wordpress is postID, when you try to post to nodebb, it errors out at title too short (3). It seems to only take the ID in that case, but most people use proper permalinks anyway.
It's also rather difficult to rebrand. but it's a good plugin, so I'll let you off, I guess.
-
haha right. I saw your issue. Will look into it at some point
-
@psychobunny No rush, it works, I'm happy.
-
it works
Well that's a refreshing change.
-
Updated this plugin to allow you to use NodeBB's category and author information rather than ghost/WP's, ex:
-
@psychobunny, excellent work. This makes my intended usage schema perfect.
-
It's strange, I can't get this to work with Ghost as it seems that they changed the way the API works. The placeholder API documentation says that it should return posts with status published for calls with NoAuth.
I am stuck on the "sign in to Ghost to enable the publish button." page.
The GET call to
/ghost/api/v0.1/posts/22/
returns a 401 Unauthorized, with the response{"type":"error","message":"Please Sign In","status":"passive"}
In the meantime I opened an issue on the nodebb-plugin-blog-comments Git repo as well as submitting a pull request to enable protocol relative links in the comment embed scripts to stop displaying mixed content warnings when the blog is served via https.
-
afaik, I've always had to be signed in to publish. I'm assuming that if you're signed in it does work? thanks for the PR btw
EDIT: nvm, read your issue, I guess this is a problem on our end then - time to upgrade our blog to v0.5
-
@psychobunny the problem is that I am signed in when that message appears. Going to spin up an instance of Ghost 0.4 (the same that you're using on the nodeBB blog) and try that. From what I see the API responses have changed between 0.4 and 0.5 (which I'm currently running).
-
yeah, looks like it might be an easy fix actually
-
@psychobunny glad to hear that.
I also stumbled upon a bug when testing with that Ghost v0.4 instance. If you delete the thread in the NodeBB instance the blog embedded comments section still thinks it has a thread in which to post comments. Any way to manually unlink the two after purging a thread from the forum that is linked to a blog post?
-
@psychobunny said:
Not today. Ghost has a long way to go in terms of development - if you see their ACP you can tell that they are missing a lot. And more importantly, Ghost is currently single account only; they do not have multiple sign-ups yet.
When the time comes, I'm down for writing a deeper integration
Hi I'm new to the NodeBB and I'm interested in the current/future state of "ghost comments" integration?
I'm asking because multiple user support has been "finally" added this month to the Ghost 0.5The thing is I would like to design a theme for Ghost and NodeBB with this integration in mind