https://github.com/MakerStudios/nodebb-plugin-vbexporter
https://github.com/akhoury/nodebb-plugin-import
Should be all you need. Maybe psychobunnys vbcode converter found here: https://github.com/psychobunny/nodebb-plugin-vbcode-to-markdown
@julian said:
@scottalanmiller said:
Even running NodeBB naked, you could just handle this at the OS firewall layer.
From an admin empowerment point of view, I can see the appeal of having it built into core (or via plugin), however.
Yes, would be handy. Just thinking that there is a solution today as well. Overall I agree, a plugin would be best.
Like,
forum1.yourdomain.com and
forum2.yourdomain.com ?
You just need to setup NodeBB on two different ports, and have nginx serve them to your appropriate subdomain. What's your current setup like?
@julian said:
When I finally get around to creating the daily digest email, it'll most likely be a compilation of the "unread" topics at the time of posting. If there aren't any, then I figure there's no reason to email
But isn't filtered to one or more categories?
So a watch category could be useful We use that feature at our smf forum (is to be replaced by a NodeBB in the future...)
I can't find this setting, but it would be great if it were possible to disable the chat feature.
Edit: deleting because this is already being discussed elsewhere.
So was this issued or no?
EDIT: Apparently not, unless I missed it when searching high and low for it, so I created one.
https://github.com/NodeBB/NodeBB/issues/1973
Great, thanks @baris. How about /recent and /popular? I'm trying to make a private forum but it doesn't seem current core is conducive to that.
Edit: I realize that I can block guests from seeing posts by setting the access control parameters in the ACP, but I'd like to block the /recent and /popular (and all other) pages from guests just in case anything is missed, or at least blocking them access on principle.
That would make a lot of sense. Some people don't like FontAwesome or use another icon set entirely - making it more modular would allow for more freedom to choose how you wish.
Limiting posts to people with certain badges is one thing, but groups and their permissions is definitely something that needs to be flushed out a bit more in the future.
@Tanner yup, just slightly more work as you'd have to wire up the save/load calls when the homepage is loaded.
You could get away with doing the save only, if there were a hook for home page retrieval, but to my knowledge, we don't have one... (yet?)
Thanks guys. Looking forward to tag based plugin grouping in the ACP page.
I'm not looking forward to the eventuality that in the first version of this, all the plugins will be lumped under the nodebb tag, because that tag is in practically every plugin
Definitely plugin territory. If you want to commission the plugin there's plenty of plugin authors in the community who might want to take a stab at it
