Testing blog comment v0.1.19 by @psychobunny for nodebb 0.5.2 and it seems to be broken. Changing the settings and clicking on save does nothing. As a test, I switched over to markdown settings and clicked save, it shows a popup message.
@peter Try filing an issue here, it may not be compatible with latest version of NodeBB. You could try running ./nodebb dev and saving it then, see if anything pops into the console, or anything at all.
@julian Where can I find the generic code for using NodeBB as a commenting system? My blog is static, and I'm looking for a commenting system -- being able to use my current install of NodeBB would be great!
It seems when we embed google font from acp it works. But if we use google font in our style file it does not work well.
The weird thing I experienced is when I changed my font setting in phpstorm to "Ubuntu" and then I pushed my changes in git using built in plug-in in phpstorm and later udpated my live file, I found that my font-family was overwritten in body, h1, h2, h3, h4, h5, h6, .h1, .h2, .h3, .h4, .h5, .h6
I work in an environment where there are two nodeBB instances : integration and production.
Integration is where I've tested all features, graphic design, etc.
My commmunity is now ready to go into production. I would like to dump all the configuration I've fine tuned in the config platform without the content, i.e. users and posts (which are all dummy, made for testing purpose).
I've searched the nodeBB forum, and I've only found ways to dump the entire database (config AND content).
This will also help me in the future: I would like to keep my integration platform to test new configurations and push them to the production once tested.