We did that and it worked. Thanks a million.
Could be possible that your template is up to date but the JS isn't. Maybe its cached? What does your
yourdomain.com/src/forum/admin/themes.js look like, is there a
Maybe update to this (or just make the change yourself): https://github.com/designcreateplay/NodeBB/commit/c5cae312d7efa7f755609668e58c4ed0dd0f36a7
What's the output?
Hey @geoffb! Welcome back.
I ran into similar issues on my dev environment -- in my case, vanilla and lavender needed to be updated.
Post install I had to nuke the
I'll try your patched version of themes.js and check the versions of vanilla and lavender.
EDIT: Here are the versions of Vanilla and Lavender that I've got installed:
firstname.lastname@example.org /home/ec2-user/nodebb ├── email@example.com └── firstname.lastname@example.org
@geoffb You're using Lavender, right? Not a fork? If you are, you would have to bring that theme up to date to the latest changes in Vanilla and/or Lavender, since overwritten templates aren't updated.
Post install I had to nuke the public/templates directory to fix other issues.
Noticed this on our end as well...
If vanilla and lavender are up to date, then the only remaining culprits would be the NodeBB core code itself, and possibly widget-essentials (v0.0.21-1)
I updated to the latest v0.4.x code today (which includes the fixes mentioned by @psychobunny) and all seems to be well! Thanks for the help
@geoffb, can you update again? A couple speed improvements were added... (or rather, reversals for a speed degradation)
Just updated to the latest 0.4.x and the loading is much faster, thanks for the heads up!