Thanks a lot! It works if it's a relative path, not if it's an absolute path with a domain name...

I think I'm having issues related to this plugin after update to very latest 1.2.1. Node restart crashes with:

error: Error: ENOTEMPTY: directory not empty, rmdir '/root/nodebb/public/templates'

That directory contains .tpl files for static pages.

1.4.0 at least appears to just work.

Nevermind. Fixed by repo reset..

Only error I see is:

2019-11-24T11:47:32.340Z [4567/1551] - error: db.initSessionStore is not a function

on trying to run it, but I presume this is caused by incomplete build..

And I seem to have this hanging on multiple commands:

./nodebb build
[benchpressjs] Unable to build or find a suitable native module, falling back to JS version
  started

(hangs)

I'm trying to upgrade nodebb to 1.13 from 1.6 and the update process updates schema (yay!) but then gets stuck on assets:

Updating NodeBB...

1. Updating package.json file with defaults...  OK

2. Bringing base dependencies up to date...  started
npm WARN nodebb-plugin-emoji-android@2.0.0 requires a peer of nodebb-plugin-emoji@^2.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN textcomplete.contenteditable@0.1.1 requires a peer of textcomplete@^0.14.2 but none is installed. You must install peer dependencies yourself.

audited 4084 packages in 9.988s
found 15 vulnerabilities (4 low, 2 moderate, 9 high)
  run `npm audit fix` to fix them, or `npm audit` for details

3. Checking installed plugins for updates...  OK
4. Updating NodeBB data store schema...[benchpressjs] Unable to build or find a suitable native module, falling back to JS version

Parsing upgrade scripts... 
OK | 0 script(s) found, 82 skipped
Schema update complete!


5. Rebuilding assets...  started

Is there any way to ask for more logs to understand what is going on?
Thanks!

Did you by any chance have another look at the discord widget?

@HolyPhoenix

I'd be still super interested in a discord plug-in that works sort of like the site chat (in a drop-bar from the menu).

No chance you had a look at it meanwhile? Or at integrating?

@PitaJ said in v1.4.0 startup error:

@MJ try this sequence of commands:

./nodebb stop
npm install nodebb-plugin-composer-default@4.3.1
./nodebb build
./nodebb start

For me this results in:
4/12 04:11 [14399] - warn: One or more of NodeBB's dependent packages are out-of-date. Please run the following command to update them:
4/12 04:11 [14399] - warn: ./nodebb upgrade

After running nodebb upgrade, I'm back to 4.3.0.

1.4.0 at least appears to just work.

Yes, it's an upgrade blocker for us but then we don't really need upgrading.