@julian said in forum is not behaving normal on firefox: You likely have some cached client-side files on Firefox. Please clear the browser cache and try again. yeap, apparently this was the problem. Thanks

@julian said in Blog comments on external blog website: @crazycells ah sorry, I didn't respond because I wasn't sure... But I think it should be fine. Technically according to browser security policy, nodebb.org and community.nodebb.org are essentially different sites. So if you used a different domain the same restrictions apply, but the plugin should still work. Thank you very much, we will try it and report the outcome then...

@crazycells Agree - you can have as many or as few as you'd like though.

@phenomlab thank you very much, this works like a charm...

@baris thank you very much.

@baris said in codes for the skins: The css for these are coming from https://bootswatch.com/, you can find them in nodebb/node_modules/bootswatch/dist Thank a lot... I searched the GitHub and found them here: https://github.com/thomaspark/bootswatch/tree/v5/dist

It would indeed be helpful to make the public chat rooms more present. At the moment it's unfortunately a dead feature in our forum. Maybe we don't have the use case, but it's definitely too hidden. The current situation is that users have to go to the chat overview and, with luck, discover the chats by chance.

@crazycells ah, not at all.. but... Man, that's cool. I think there's definitely a lot of utility in seeing popular uncategorized posts. I'll take a closer look. Edit: This is resolved now. Uncategorized topics should no longer appear in /popular unless that category is explicitly selected.

@baris thanks this is much better.

Deck the Node with Custom Code fra la la la laa la la la laa Merry Christmas

In case anyone else might be intrested, I fixed this color problem using these codes: .category-1 , .category-70 , .category-120 { .category-children-item .fa-caret-right { color: #ff9800 !important ; } } .category-111 { .category-children-item .fa-caret-right { color: #e91e63 !important ; } } .category-2 , .category-77 , .category-78 , .category-126 , .category-127 , .category-132 , .category-93 , .category-115 { .category-children-item .fa-caret-right { color: #4caf50 !important ; } } Basically I had to name each category separately... So, if there is any suggestion to shorten the code, I would love to hear...

It will be available in 3.6.0

@mschwartz thanks yes, we already have these categories... but unfortunately the topics I mentioned cannot be moved here because they belong to another category/sub-category.

@crazycells yup. You can find integration docs here (tl;dr you need to implement WOPI protocol for file access. Which will also work for most other web-based document editors, since that's basically the industry standard. OnlyOffice offers their own API as an alternative, but also supports WOPI. You can find an example server in Node here) Install docs are here - from my understanding their primary distribution method is docker, but they do offer native packages if you prefer (looking at you Discourse with your docker-only yet for some reason linux-only installation using bash scripts)

Hi, @phenomlab and @crazycells and @DownPW . Has someone time and the expertise for this that you know? My programmer is pretty buissy and a bit slow

2.0.1 for nodebb 3.x 1.0.3 for nodebb 2.x

@baris i know it is nothing urgent, but looking forward to having this addition https://github.com/julianlam/nodebb-plugin-mentions/issues/244

@baris updated to 3.7.2 and now just waiting for the plugin to be updated.

@phenomlab said in How to change Font type? (serif vs. sans-serif): @crazycells they can only be used on websites if they are installed and included in the site you are viewing. This basically means that unless the font is available on he remote server, it won't display to other users if they do not have it installed (but would for you if you have it installed) This is why CSS on most websites will use system as a fallback so that the text is rendered even if the font cannot be found rather than the default of Times New Roman being displayed. System essentially uses whatever font is the default on the system viewing the website. In essence, under Windows, this would be SegoeUI. Under a Mac, it's of course different. Importing a font into your website isn't a difficult task. It's explained very well here https://stackoverflow.com/questions/14676613/how-to-import-google-web-font-in-css-file However, if you'd like to include a font that isn't from Google this is still possible, but the process differs slightly - and the caveat here is that not all fonts are created equal. Some do not lend themselves very well to rendering within web pages, and so it's always best to go for "web safe" versions. For example, just try "master of puppets" (yes, Metallica) and see what happens ! In an seriousness, if you need help with fonts etc, happy to help. thank you very much, this was helpful! I will let you know about the progress

Looking at those numbers, definitely. We typically opt for a horizontally scaled solution the moment we see the "concurrent users" metric hit 100. This is a conservative estimate, NodeBB can easily handle more, as you've experienced, but it is a good point to start thinking about solutions.