I published v1.11.0 for v3. Still has a lot of work to do.

• Styles aren't quite right.
• Widgets don't work at all.
• Using a custom template doesn't work.
• Pagination is weird.

Adding, deleting, and editing lists works. The default news and blog pages work. Shouldn't crash too often.

I'll be keeping an eye on this page.

Interesting idea

Version 0.10.0

Scuff update for nodebb 2.x
A bit late, but better than never.

0.10.1 should fix I think.

@phenomlab Sorry for that! I'm in the middle of updating everything for v2.0.

What version of NodeBB are you running?

They had more money.

@baris oooooooh I see now.

@baris having the same issue with bootbox.

I can call it globally, but it says that's deprecated.

@baris Thanks, just parsing a template, so app.parseAndTranslate worked.

app.require('benchpress')

Error: Cannot find module './benchpress'

Is there a branch we can test against?

@julian

Not really a breaking change (yet), but the module definitions in plugin.json are kinda, odd...

I would expect the key to be the module name, but it's actually the filename. That makes sense in RJS world, where the file name needs to end in .js, but not so much in plugin.json world. You end up with this weirdness:
https://github.com/NodeBB/NodeBB/blob/master/src/meta/js.js#L90-L113

Where you could just use the module name and add the .js in the build step:
https://github.com/NodeBB/NodeBB/blob/master/src/meta/js.js#L178

destPath: path.join(__dirname, '../../build/public/src/modules', relPath + ".js"),

It would make this more readable too since both the json and js would use the string 'jquery'.
https://docs.nodebb.org/development/plugins/libraries/

Yes, I am very nit-picky.

@phit You got it boss!

Naisu!

nginx.confs

server {
  server_name serenitymc.net;

  location / {
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header Host $http_host;
        proxy_set_header X-NginX-Proxy true;

        proxy_pass http://127.0.0.1:4567;
        proxy_redirect off;

        # Socket.IO Support
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
  }

  listen [::]:443 ssl ipv6only=on;
  listen 443 ssl;
  include serenitymc.ssl;
}

server {
  server_name onpu.serenitymc.net;

  location / {
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header Host $http_host;
        proxy_set_header X-NginX-Proxy true;

        proxy_pass http://127.0.0.1:4566;
        proxy_redirect off;

        # Socket.IO Support
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
  }

  listen [::]:443 ssl;
  listen 443 ssl;
  include serenitymc.ssl;
}

config.json

{
    "url": "https://serenitymc.net",
    "secret": "xxx",
    "database": "mongo",
    "mongo": {
        "host": "127.0.0.1",
        "port": "27017",
        "username": "nodebb-serenity",
        "password": "xxx",
        "database": "nodebb-serenity"
    },
    "port": "4567"
}

{
    "url": "https://onpu.serenitymc.net",
    "secret": "xxx",
    "database": "mongo",
    "mongo": {
        "host": "127.0.0.1",
        "port": "27017",
        "username": "nodebb-onpu",
        "password": "xxx",
        "database": "nodebb-onpu"
    },
    "port": "4566"
}

I just tried injecting some stuff, and it looks like it stopped everything unnormal out of the box.

@gotwf Good point. They are sanitized on the NodeBB side, so whatever sanitize plugin you use should account for anyone trying to put something sneaky into your ghost.

I decided to install a fresh copy of ghost and NodeBB to see what's up.

The plugin does technically work, but you need to use the script in the README/git and not the one on this page which is outdated.

Correct script:

<a id="nodebb-comments"></a>
<script type="text/javascript">
var nbb = {};
nbb.url = '//your.nodebb.com'; // EDIT THIS
nbb.cid = 1;	// OPTIONAL. Forces a Category ID in NodeBB.
				//  Omit it to fallback to specified IDs in the admin panel.

(function() {
nbb.articleID = '{{../post.id}}';
nbb.tags = [{{#../post.tags}}"{{name}}",{{/../post.tags}}];
nbb.script = document.createElement('script'); nbb.script.type = 'text/javascript'; nbb.script.async = true;
nbb.script.src = nbb.url + '/plugins/nodebb-plugin-blog-comments/lib/ghost.js';
(document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(nbb.script);
})();
</script>
<script id="nbb-title" type="text/markdown">{{../post.title}}</script>
<script id="nbb-markdown" type="text/markdown">{{../post.markdown}}</script>
<noscript>Please enable JavaScript to view comments</noscript>

After that, commenting it works great.

HOWEVER, the bigger issue is, ghost no longer uses Markdown, but HTML. So the article content doesn't show up on NodeBB.

You can change the script to use {{../post.content}} in place of {{../post.markdown}} to feed the HTML to NodeBB, but you will also need to turn Allow HTML on in the Markdown plugin.

Then it works.

@omega said in [nodebb-plugin-ns-embed] NS Embed:

Newborn calf takes first clumsy steps to get milk from his mother

Bernice is a beautiful cow with a wonderful personality. She lives on a gorgeous farm in the hills of Millbrook, Ontario. Its one of the most perfect farms in Canada, with hundreds of acres of lush, g

Rumble (rumble.com)

I don't think it's possible. There doesn't appear to be any direct conversion, or even metadata to grab. Would have to scrape the whole page.

Or apparently, use iframely

@omega said in [nodebb-plugin-ns-embed] NS Embed:

(?:www.)?bitchute.com/video/([a-zA-Z0-9_-]{4,11})(?:.*?/a>)?

Both of those worked for me.

Are you replacing with the embed link?

<div class='embed-wrapper'><div class='embed-container'><iframe src='https://www.bitchute.com/embed/$1' frameborder='0' allowfullscreen></iframe></div></div>