[nodebb-plugin-blog-comments] Blog Commenting Engine (Ghost, Wordpress widget)

Jay Shaffstall

I have a possibly unusual use case that shows I probably don't understand how NodeBB integration is working with this plugin. I'm on Wordpress.

Here's what I thought happened: the plugin uses the Wordpress article id to use to create a new NodeBB topic with that same id when the Publish button is pressed. Afterward, since the topic already exists, you see the posts and comment form instead of the Publish button.

My use case is that the topic already exists (it was created in NodeBB) and I'm trying to tie a Wordpress post to it. I'm using the general approach and setting nodebb.articleID to the NodeBB topic id.

What I expected was to see the comment box and current posts in that topic. What I'm seeing instead is the Publish button.

Am I misunderstanding how things should be working?

Joykiller

@psychobunny said in [nodebb-plugin-blog-comments] Blog Commenting Engine (Ghost, Wordpress widget):

hey @Joykiller I'm quite certain this works with the latest version of NodeBB as we are using this currently on our forum: https://blog.nodebb.org/v1-5-0-a-long-awaited-release/

May not be up to date with the latest version of Ghost though, so that might be the issue here. It's come up pretty recently that we should consider upgrading our blog to latest, and when that happens I'll certainly make sure that the plugin works with it

Cool, I'll be waiting there has been alot of changes in Ghost lately.

Joykiller

@jay-shaffstall said in [nodebb-plugin-blog-comments] Blog Commenting Engine (Ghost, Wordpress widget):

I have a possibly unusual use case that shows I probably don't understand how NodeBB integration is working with this plugin. I'm on Wordpress.

Here's what I thought happened: the plugin uses the Wordpress article id to use to create a new NodeBB topic with that same id when the Publish button is pressed. Afterward, since the topic already exists, you see the posts and comment form instead of the Publish button.

My use case is that the topic already exists (it was created in NodeBB) and I'm trying to tie a Wordpress post to it. I'm using the general approach and setting nodebb.articleID to the NodeBB topic id.

What I expected was to see the comment box and current posts in that topic. What I'm seeing instead is the Publish button.

Am I misunderstanding how things should be working?

You need to click the publish button before comment box shows up.

Jay Shaffstall

You need to click the publish button before comment box shows up.

What does the publish button do, exactly? I had been assuming it created the topic in NodeBB. But if the topic already exists, what does publish do?

Jay Shaffstall

I confirmed on a test site that clicking the button does create a new topic, so clearly I am not understanding what the Javascript articleId variable really is doing.

Can anyone shed any light on that? I can cope with the button creating the topic, but I do need to know what role the articleId plays in the process. I'm using this plugin to power comments on virtual pages, pages that don't actually exist as separate Wordpress pages, so I don't have a post id to use.

Does the articleId need to be a unique value? Must it be an integer? What's the legal range of it?

Edit: For anyone doing something similar to what I'm doing, here are the answers:

The articleId must be unique, the plugin establishes a mapping between it and a new topic id. There does not appear to be a way to tie a Wordpress article to an existing topic.

The articleId does not need to be an integer, as long as you use quotes it can be any string. It's solely used to find the topic id in NodeBB.

So if you're using it like I am, for virtual pages that don't actually exist in Wordpress, you can safely coexist with comments on normal Wordpress pages by using an alphanumeric unique id for the virtual articleIds.

asyung

@psychobunny

I'm using Nodebb 1.6.1

I installed via npm install nodebb-plugin-blog-comments.
I have logged into the ACP and activated the plugin. However when I go to Plugins->Blog Comments, I get this message in the nodebb log:

23/10 23:18:20 [11464] - warn: [plugins/load] The following plugins may not be compatible with your version of NodeBB. This may cause unintended behaviour or crashing. In the event of an unresponsive NodeBB caused by this plugin, run ./nodebb reset -p PLUGINNAME to disable it.

nodebb-plugin-blog-comments

23/10 23:18:20 [11464] - info: Routes added
23/10 23:18:20 [11464] - info: NodeBB Ready
23/10 23:18:20 [11464] - info: Enabling 'trust proxy'
23/10 23:18:20 [11464] - info: NodeBB is now listening on: 0.0.0.0:4567
23/10 23:18:26 [11464] - error: /assets/templates/comments/admin.js
Error: ENOENT: no such file or directory, open 'C:\Temp\NodeBB\build\public\templates\comments\admin.tpl'

If I copy and paste "comments" folder from:
C:\Temp\NodeBB\node_modules\nodebb-plugin-blog-comments\public\templates
To:
C:\Temp\NodeBB\build\public\templates

Then I can the access blog-comments. However I do not know if this is a proper solution as I am unable to get things to work so far.

Is there a test I can do to see if the plugin is setup correctly?

I'm trying to use just a javascript front end to display comments.

Your help is appreciated. Thank you!

PitaJ

Did you try running ./nodebb build before copying over the templates?

KyleTryon

Hoping this is still good Looks like there's a recent commit though so . I have a need for another plugin that integrates with GhostCMS so I hope this will be able to help me see how to do that as well. Thank you! If I can figure this all out I promise to release the plugin.

The Worms

After upgrade, i have this message :

      warn: [plugins/load] The following plugins may not be compatible with your version of NodeBB. This may cause unintended behaviour or crashing. In the event of an unresponsive NodeBB caused by this plugin, run `./nodebb reset -p PLUGINNAME` to disable it.
* nodebb-plugin-blog-comments

Juan G.

@psychobunny wrote:

It's come up pretty recently that we should consider upgrading our blog to latest, and when that happens I'll certainly make sure that the plugin works with it

I've just seen that the official NodeBB Development Blog has been upgraded to Ghost 1.21, and NodeBB comments are working on it.

So I've installed it with the current Ghost and NodeBB, and it works.

Sea Ansley

I'm trying to get this installed now on my Wordpress for https://digitalnomad.blog ... the JSON API recommended originally years ago, hasn't been updated in 3+ years. No comments in the support there, and says it may not be compatible with recent / coming Wordpress installations.

Will this nodebb plugin work with other WP JSON API plugins, such as JSON Content Importer - https://wordpress.org/plugins/json-content-importer/

dgarsys

While the comments entry field appears for me in one blog - Ghost version: 2.10.1 and nodebb 1.11 with the most recent version of the plugin from what I can tell - and links to the respective comments topic and makes entries, the comments in that topic do not appear below the blog post.

c3do

Hello, fresh install nodebb v1.11.1, i have this message:

warn: [plugins/load] The following plugins may not be compatible with your version of NodeBB. This may cause unintended behaviour or crashing. In the event of an unresponsive NodeBB caused by this plugin, run `./nodebb reset -p PLUGINNAME` to disable it.
  * nodebb-plugin-blog-comments

Can i have some help, please? Thank you.

PitaJ

@c3do it's just a warning. You can ignore it. Are you having any actual issues with the functionality of the plugin?

c3do

@PitaJ yesterday, i could not go on the settings page. i saw this warning, so i thought it was the problem.
I had run the command "./nodebb build" but the warning was always here. So, I was obsessed with the warning.
Finally, the command had solved the problem without me realizing it. I can access the settings page despite the warning.

c3do

I am on ghost. I can create the new topic and comment from ghost. But, last comments does not appear in ghost post.

Dave Jensen

I installed the plugin, setup comments.php on Wordpress and I see the following on Wordpress:

"Commenting has been disabled" with the "Publish this article to NodeBB"

However, when I push the button, I get this error:

Internal Error.
Oops! Looks like something went wrong!

/forums/comments/publish

Unexpected end of JSON input

Could this be a problem with my forum being installed in a subdir?

cc: @psychobunny @baris

Dave Jensen

I'm also seeing this in the logs:

2019-02-07T22:14:16.880Z [4567/23701] - warn: [nodebb-plugin-blog-comments] Origin (undefined) does not match hostUrls: https://www.axisandallies.org
2019-02-07T22:14:42.601Z [4567/23701] - error: /forums/comments/publish

SyntaxError: Unexpected end of JSON input
    at JSON.parse (<anonymous>)
    at Comments.publishArticle (/var/srv/nodebb/node_modules/nodebb-plugin-blog-comments/library.js:135:15)
    at Layer.handle [as handle_request] (/var/srv/nodebb/node_modules/express/lib/router/layer.js:95:5)
    at next (/var/srv/nodebb/node_modules/express/lib/router/route.js:137:13)
    at Route.dispatch (/var/srv/nodebb/node_modules/express/lib/router/route.js:112:3)
    at Layer.handle [as handle_request] (/var/srv/nodebb/node_modules/express/lib/router/layer.js:95:5)
    at /var/srv/nodebb/node_modules/express/lib/router/index.js:281:22
    at Function.process_params (/var/srv/nodebb/node_modules/express/lib/router/index.js:335:12)
    at next (/var/srv/nodebb/node_modules/express/lib/router/index.js:275:10)
    at rewrite (/var/srv/nodebb/src/controllers/home.js:33:10)

It's odd that Origin is undefined, right?

Also, here's the forum data being posted, it's not JSON and it's missing a bunch of stuff.

markdown=&title=&cid=&tags=&id=2930&url=https%3A%2F%2Fwww.axisandallies.org%2Fp%2Fvictory-new-wwii-game-columbia-games%2F&_csrf=l3iXstpC-aU9hckFGosqYZl2yAcIZ_ozQR98

Oddly I get the same error with and without the JSON API wordpress plugin activated. (It is currently activated)

Dave Jensen

This post is deleted!

Dave Jensen

Okay, the solution to this is that the comment in the Wordpress php that the categoryID is options is not correct. You need the category ID.

But there are still some subdir issues happening for me.