@dogs thank for this plugin 👍
Here is the way i installed it :
Hope this help.
@StuartH said:
Only when my wife is near
no on nodebb 2.1
Only edge is supported right now. I suppose you can do `npm install [email protected] to still get basic shoutbox functionality on your version.
let me know what I got to do to fix that @Mr_Waffle
Working fine for me.
@psychobunny said:
we need to ditch the
$(document).bind('DOMNodeInserted', function(event) {
p.s. I have no idea how badly that performs but I would imagine it sucks.
it does suck - but you should see this, i've used it before, works like a charm (minus IE8)
http://jsfiddle.net/PkYb9/2/
EDIT: time for a jsfiddle/jsbin embed plugin
haha well since you just said my codez suck your opinion is irrelevant
kidding
anyways ajaxify.onchange is the best solution to detect what page we're on, needs to be implemented, I'll make an issue
0.0.4 has been published.
Global changelog:
@Mr_Waffle +1
@xCausxn Not yet. @psychobunny was talking about a 'widget' feature he's planning where plugins can be designated to from the AdminCP, so you'll have to wait for that. To keep max compatibility I'm only supporting top and bottom of the page now.
@StuartH said:
@mr_waffle I have the shoutbox installed but it says I must be logged in to post but I am logged in!! I logged out then in, cleared cache, on nodebb 2.1, I can break anything
I think I know what the issue is with this. When it's taking too long to execute some piece of code (don't know which) that's responsible for logging you in, you'll appear as not being logged in (also in the header). The shoutbox then checks if you're logged in, and hoozah, you're not -> message is displayed. A page refresh often fixes this.
0.0.5 published
Changelog:
Hey @Mr_Waffle I feel like your shoutbox should just apply a hide
class on the whole thing outright when logged out, since you're not allowing users to view the actual content anyways (just takes up space on your home page)
@psychobunny said:
Hey @Mr_Waffle I feel like your shoutbox should just apply a
hide
class on the whole thing outright when logged out, since you're not allowing users to view the actual content anyways (just takes up space on your home page)