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 Just works as intended.
The approach here totally works.
As you kindly suggested, it's my mistake not to have set subdomain by DNS.
I somehow misunderstood Ngynx takes care of subdomainsDNS IP routing, my bad.
Thanks a lot.
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
@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!
But perhaps I should add a not in the sign up agreement that "by signing up you agree to receive emails from us" or something like that, to be safe.
If you're in the EU, this wouldn't constitute as opt-in. The EU states that a user must specifically click a button that states "I want to receive these emails". Unless it's regarding their account. So, if the daily digest included notifications, it would be fine, but if it was just new topics, I'm not so sure. It should be fine either way, as you've said.