After some more code digging and experiments I can answer my own question. A theme is a normal plugin and as such does not inherit any behavior from other plugins.
So you need to copy everything you need from the base theme library.js to your child theme. And of course, you need to declare client scripts explicitly.
Loading of missing templates from base theme is the only link between the base and the child theme.
[nodebb-plugin-shoutbox] Shoutbox plugin
-
kk, in this case it's just a problem of @manuel s configuration
I just usednconf.get('url')without knowing anything about nconf
-
@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
-
@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 thenconf.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 replaceemojiPath=nconf.get("url")+"/plugins/nodebb-plugin-emoji-extended/images"byemojiPath="/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
-
Like @julian said it's better to set "use_port" within your nodbb-root/config.json to false, that will remove the port from the paths without destroying possibility to update plugin or installation within sub-directories (don't know if it's even fully supported by nodebb yet)
-
Been a while since an update... Luckily a lot has been done since, and version 0.1.0 will be released soon!
The most notable change? A new design!
This is a screenshot of the latest version running over at our forum
Some other notable changes:- User status is reflected by the green border around their avatar. This is stylable by theme creators.
- Inline editing! Instead of the annoying edit popup, editing is now done in the input box.
- Skype like editing of your last shout! Just press the up arrow to start editing your last shout!
- User settings -- you can change your Shoutbox settings in your user settings now!
- Admins can turn off features in the admincp (like archive and the gist button).
- Also the admincp, complete redesign! Screenshot can be found a few posts up.
- (Almost) completely refactored client code! It's a lot more maintainable now!
- A load of bugfixes and tweaks that enhance your experience!
- Compatible with the very latest NodeBB!
Also, if you haven't noticed yet: I now go by a different username
-
@Schamper Looks amazing! Nice work. Is this possible to be on a standalone page or modal?
This reminds me of like some sort of group chat. -
@trevor It's already on a standalone page! There's a setting in the admincp that will add a menu link for it, and clicking the title of the shoutbox panel will bring you to /shoutbox.
It's also defined as a widget, so you can place it in any widget area you have in your theme -
Awesome, love the skype-like editing feature. Wonder if that could work on the chat system as well
Also, if you haven't noticed yet: I now go by a different username
haha yeah, need the backstory there (ex. nobody wanted to hire a "MrWaffle" - well imagine my username then!)
-
@psychobunny said:
Awesome, love the skype-like editing feature. Wonder if that could work on the chat system as well
Also, if you haven't noticed yet: I now go by a different username
haha yeah, need the backstory there (ex. nobody wanted to hire a "MrWaffle" - well imagine my username then!)
Nothing interesting, Schamper has always been my more personal username. Was recently told that Github is fairly important in job interviews so I went ahead and changed it to a more professional username
While I was at it I changed it over at this forum and BitBangers. -
Was recently told that Github is fairly important in job interviews
Yes... I firmly believe this is why nobody will ever poach @psychobunny from NodeBB.
dat username. -
You'll always be my Mr_Waffle
-
@julian said:
Yes... I firmly believe this is why nobody will ever poach @psychobunny from NodeBB.
dat username.yeah. my last job interview:
"So, do you have a GitHub account?"
"err... nope."
-
any chances to be updated for nodebb 0.4.0?
-
@manuel said:
any chances to be updated for nodebb 0.4.0?
Current master branch on Github is 0.4.0 compatible, I'll try to push an update to npm this weekend.
-
Here's a suggestion @schamper ; On the shout box the area should be greyed out if you're not logged in. Or should give off a friendly message indicating that you must be logged in to use the shout box.
-
@trevor this was the previous method, but instead of graying it out, the input area would be hidden. However I've chosen to completely hide the shoutbox when you're not logged in.
-
-
0.1.0 published! Requires NodeBB 0.4.0.
Main new features:
- Complete redesign.
- User status is reflected by the green border around their avatar. This is stylable by theme creators.
- Inline editing! Instead of the annoying edit popup, editing is now done in the input box.
- Skype like editing of your last shout! Just press the up arrow to start editing your last shout!
- User settings -- you can change your Shoutbox settings in your user settings now!
- Admins can turn off features in the admincp (like archive and the gist button).
- Also the admincp, complete redesign! Screenshot can be found a few posts up.
- (Almost) completely refactored client code! It's a lot more maintainable now!
- A load of bugfixes and tweaks that enhance your experience!
- Compatible with the very latest NodeBB!
Todo:
- It's possible that settings and stuff don't work correctly with redis yet. I'll be fixing this soon.
- Adding the timestamp back.
-
@Schamper Take a look at how I save settings here
No need to use
Settings.prepareanymore. -
@julian Cheers, will take a look at that!
