Been offline for a bit but it looks like this has been addressed. This has been fixed by @julian in commit d33d965 to nodebb-theme-persona and commit 9d202d9 to nodebb. Thanks Julian!

the answer is in this topic : https://community.nodebb.org/topic/11906/add-a-class-to-the-body-if-the-template-is-404/3

nah, not gonna do this.

@insuusvenerati try running ./nodebb build and then start NodeBB

if you'd like to base your theme as a child theme of Persona When you see such output in console, it overwhelms you... My theme isn't a child theme, but in order to upgrade forum, you have to upgrade theme also, and incorporate changes from Persona. Your branch is behind 'origin/master' by 240 commits, and can be fast-forwarded.

@Mega said: config['theme:id'] Thanks!

Thank you so much!

NodeBB's cache buster is based on its current git hash (so if you've upgraded it will try to send you the new CSS and JS, which works well, but it remains the same if switching themes, which results in your issue) I suppose the dev team hasn't run into this because we usually run with cache disabled while testing (and because Persona is so awesome so why switch? Kidding) https://github.com/NodeBB/NodeBB/issues/3573 psychobunny created this issue in NodeBB/NodeBB closed Update cache buster when switching themes #3573

Post your plugin.json maybe it has a syntax error. Also did you put your theme in node_modules and activate it from the ACP?

@Codejet said: can you still manually change to lavender in ACP after install / upgrade ? and run it this way what is the benefit of adding a hook listener, or are u removing vanilla/lavender functionality Yes, this change doesn't affect how you use NodeBB, it only affects you if you're a theme developer (with a Lavender-variant or vanilla-based theme) and you want to maintain compatibility post v0.8.x

Agree, just have to get used to the differences between what you have in NodeBB and PHP temptate engines like Smarty and vBulletin's built in engine.

@julian the inherited themes didn't work before, but is it possible that now you've made this commit: https://github.com/NodeBB/nodebb-theme-lavender/commit/7f8e9e4df0f0d20e8b83ab096c1443544df9bd4c There is scope for the template inheritance to be used there instead of the hardcoded rule 'nodebb-theme-vanilla/templates'? Right now I'm maintaining an entire theme that's a fork of lavender just so I can restyle one or two pages. 0 julianlam committed to NodeBB/nodebb-theme-lavender added preload hook listener to re-set the base_templates_path to vanilla

@psychobunny nice, It's very helpful.

Noooo, they would have been so cool!