[nodebb-plugin-shoutbox] Shoutbox plugin

psychobunny

haha, where have I seen this design before...

Schamper

@psychobunny I had some inspiration from recent developments

kelso

How do I obtain the new version? I attempting to 'npm install nodebb-plugin-shoutbox' again, but nothing has changed.

Schamper

@kelso said:

How do I obtain the new version? I attempting to 'npm install nodebb-plugin-shoutbox' again, but nothing has changed.

It's not available yet, I want to implement more updates first.

Sp4rkR4t

Being able to disable gists & archives is good, I did that manually.

Schamper

@Sp4rkR4t said:

Being able to disable gists & archives is good, I did that manually.

Funny, because I hate it when forums disable the ability to view the shoutbox archive... Really tempted to create a guide to bypass it...

julian

^ 100th post

manuel

i have an issue with images path for emoticons (i am running nodebb behind nginx )

paths generated by this plugin are like http://xxx.xxx.com:4567/plugins/nodebb-plugin-emoji-extended/images/grinning.png
to be correct the port 4567 should be removed

Scuzz

@manuel I think you have the wrong plugin thread?

manuel

@Scuzz this is happening only into the shoutbox

frissdiegurke

@manuel Sure? what path do the other emotes have?

manuel

i tried a git pull and restarted nodebb, now i have the problem everywhere, so it's the emoji plugin sorry
can some1 move my post to the correct topic please?

Scuzz

@manuel I get the same link to an image no matter where the image is, shoutbox and the forums. They all have the port numbers. I am using nginx too

manuel

@Scuzz said:

@manuel I get the same link to an image no matter where the image is, shoutbox and the forums. They all have the port numbers. I am using nginx too

i run nginx on public ip port 80 and it forwards to nodebb on 127.0.0.1:4567
the only "fix" i could do is to add a listener on 4567 but i don't understand why the emoji plugin adds the port when nodebb does not for all the other urls

Scuzz

@manuel probably for the people who do not run it behind a reverse proxy.

frissdiegurke

@manuel It's because I use nconf.get('url') to get the domain (in fact this remains from @julian).
I need any way to get the absolute path of NodeBB-root. I guess the nconf.get('url') is ment to avoid problems with sub-directories (that would appear if I use / instead).
Since I cannot see any automatic way around this for all use-cases you may just replace emojiPath=nconf.get("url")+"/plugins/nodebb-plugin-emoji-extended/images" by emojiPath="/plugins/nodebb-plugin-emoji-extended/images" within your/nodebb/root/node_modules/nodebb-plugin-emoji-extended/index.js
you'd need to redo this every time I update the plugin until this may get supported.
Maybe a url-prefix field will occur within the ACP/emoji-extended next update

julian

@frissdiegurke What's the problem here, port shows up in the url? As far as I know, nconf.get('url') should not give the port unless use_port is true in config.json

frissdiegurke

kk, in this case it's just a problem of @manuel s configuration
I just used nconf.get('url') without knowing anything about nconf

manuel

@frissdiegurke

@scuzz have this too but I don't know if he is running nodebb @ 4567 voluntarily

I don't think to have any particular configuration on my server, I've just used the tutorial on github to setup the ngnix proxy

afaik port number is appended only on emoji's urls

manuel

@frissdiegurke said:

@manuel It's because I use nconf.get('url') to get the domain (in fact this remains from @julian).
I need any way to get the absolute path of NodeBB-root. I guess the nconf.get('url') is ment to avoid problems with sub-directories (that would appear if I use / instead).
Since I cannot see any automatic way around this for all use-cases you may just replace emojiPath=nconf.get("url")+"/plugins/nodebb-plugin-emoji-extended/images" by emojiPath="/plugins/nodebb-plugin-emoji-extended/images" within your/nodebb/root/node_modules/nodebb-plugin-emoji-extended/index.js
you'd need to redo this every time I update the plugin until this may get supported.
Maybe a url-prefix field will occur within the ACP/emoji-extended next update

removing nconf.get("url") worked but it was config.json use_port = true

during setup and watching online documentation this effect on urls was not clear to me, sorry