This is something I use in my custom css on the admin panel, it looks to see if you are either in a category or topic of a certain category, in this instance the "Red vs Blue Discussion" category (but using the slug)
I'll soon be creating a custom theme and some plugins for a forum that is already in use and I'm thinking about running second instance on beta.forum.url with the new theme and plugins enabled when it's close to being ready (but in need of testing), that I'd like to work with the same database as the main forum - so that users can just use beta if they want to preview new features while still using the same forum as others.
Now, I know that the list of themes/plugins enabled is stored in database, so I'd probably need to do something about that, but is there anything else that would stop me from running two instances with a bit different configs off one database? Some sync issue with posts/topics or something like that?
EDIT: actually, since I might as well help others, would it be a good idea to add an option to add some instance identifier to db plugin entries to core? Perhaps in config.json? So that if it's set NodeBB would look for plugins:<instance>:active for example.
I'm newbie to the Nodebb and currently I'm trying to play around with creating a new theme.
I've downloaded the repo from Quickstart theme.
I've added the nodebb-them-quickstart folder to the node_modules folder.
When I go to the admin page and load all the available themes, my new theme is listed under the installed themes.
After selecting it, it says that I should restart NodeBB to fully activate the selected theme.
After I do that and after I refresh admin page, I'm in situation where previously active them is still the active one.
In other words new custom theme is not activated.
This is the case with every theme I made.
But when I switch to the nodebb-theme-lavander, everything goes fine.
I'm really struggling to make this happen with my own custom theme.
I would be very thankful if some would tell me what is going on.