[Solved] Weird behavior with the blog comments plugin

jdp23155

I've got the blog comments plugin integrated on my ghost blog and have some unexpected behavior in http://blogs.tapestrymaker.net/welcome-to-tapestrymaker/

Things were fine when I first posted it; I left a couple comments and it looked great. Since then I deleted a comment and edited the post in both ghost and nodebb. Now, The blog's text is getting echoed back as a comment. But when I go directly to the nodebb forum at http://forums.tapestrymaker.net:4567/topic/3/welcome#4 there is no such comment.

Suggestions welcome on how I can make it go away?

julian

Hey there @jdp23155 -- thanks for the bug report, looks like a serious problem, so I'll have @psychobunny take a look at it if I can't figure it out (as it is his plugin :))

Edit: Feel free to follow its progress here: https://github.com/psychobunny/nodebb-plugin-blog-comments/issues/5

jdp23155

Thanks! And sorry for putting this in the wrong category. I realize it should have been in the plugins.

psychobunny

hey, your blog looks pretty neat. I think you're the first person besides us that is using this plugin on a live environment (afaik)

I'll have a look soon

<baris>

Moved to bug reports, <- maybe this message needs to be automated :squirrel:

trevor

@baris said:

Moved to bug reports, <- maybe this message needs to be automated :squirrel:

Automated along with when a topic was forked. Lol.

julian

Personally? Not a fan of the automated messages when a topic is opened/closed... lowers SNR.

psychobunny

I would say not an actual post but something similar to how GitHub does it:

post

(Totally offtopic, lol)

a_5mith

@psychobunny Works for me.

julian

Hahaha... looks like it's time for nodebb-theme-github

jdp23155

Any progress on this? Even a workaround to clean up that one post would be useful ...

psychobunny

https://github.com/psychobunny/nodebb-plugin-blog-comments/issues/5

(I think you're the person who replied here but just in case - fixed!) : )

jdp23155

Yep that was me ... this did indeed fix the problem, thanks much!