It's not news to say 2020 has been... challenging. In Toronto, the home of NodeBB HQ, we've gone from a spring lockdown to a cautious summer reopening, to lockdown again — sigh. But the team has never stopped working, and have managed to squeeze out one last release before we thankfully turn over the calendar.
no errors in logs.
I have found the issue. After digging into the nodebb routing and rendering I found this line in ajaxify.js
and understood that I am using my custom theme without element with id = content, that was a problem.
After adding 'id=content' to my body tag in header template everything become Ok) @PitaJ Thanks for support
It should cache for an hour, I think (based on a quick look at nodebb package manager code). So yes - you have to wait a bit before the nbbpm refreshes. You can just install the updated version manually by using npm install <package name> from the command line in NodeBB folder.
@julian No worries. It's just slightly alarming upgrading a production instance only to find out you've accidentally gone all the way to a pre-release. We've only recently taken over our current NodeBB forum from someone else and I'm not familiar with the workflow yet.
I've made a note in our internal docs so it doesn't happen again. I was just wondering if I'd mis-read the docs or if that was the intended workflow.
Still could use assistance if anyone can offer. The new forums we are developing using nodebb is delayed until the next release, but if someone cant point me in the right direction I would highly appreciate it.