@KingCat said:
@XenTerSeO All I did was look at which themes were installed, if they weren't the active one, I deleted them. By deleting I mean I did an npm uninstall nodebb-theme-lavender, etc after disabling them in the ACP.
Unfortunately it does not help the change already established template.
Whenever you add or change the code installed themes have to clear the cache.
Have to wait for the official fix.
@XenTerSeO said:
@KingCat said:
@XenTerSeO All I did was look at which themes were installed, if they weren't the active one, I deleted them. By deleting I mean I did an npm uninstall nodebb-theme-lavender, etc after disabling them in the ACP.
Unfortunately it does not help the change already established template.
Whenever you add or change the code installed themes have to clear the cache.Have to wait for the official fix.
I'm not exactly sure what you're saying here but whenever you restart nodebb it should re-generate all the css and javascript used. Removing those themes and then doing a restart should take care of the issue.
If you're having the exact same issue as me with the container being turned into container-fluid I can help with that, just let me know.
I try to explain step by step:
Installed two themes:
nodebb-theme-persona
nodebb-theme-vanilla
I use persona.
Remove vanilla leads to errors. Probably, they are connected with each other.
Something like
I am running into this mixed theme issue on my forums. I have restarted them via the admin UI after changing the theme. It works fine when you navigate to https://www.thesaltypotatoes.com, but if you click the top left icon to navigate back to home, it looks like another theme (the Lavender theme maybe?) hops in partially. It can also be seen when going into topics. A refresh of the page fixes it, but it is not ideal for most users.
The only solution would be - clear your browser cache. But I can not make everyone force users to clear the cache when any change.
@XenTerSeO First, I believe you are correct, vanilla may be required for persona, I didn't delete that one.
Second, that issue is only temporary, It should fix itself once you close the browser window and revisit the site. Also hitting shift+refresh will force your browser to re-download all the assets. I'm pretty sure nodebb has it setup to cache the assets on the browser for a day or two.
@KingCat said:
@XenTerSeO First, I believe you are correct, vanilla may be required for persona, I didn't delete that one.
Second, that issue is only temporary, It should fix itself once you close the browser window and revisit the site. Also hitting shift+refresh will force your browser to re-download all the assets. I'm pretty sure nodebb has it setup to cache the assets on the browser for a day or two.
The problem remains even after you close your browser, and shift+refresh.
I have chrome browser.
I'm pretty sure nodebb has it setup to cache the assets on the browser for a day or two.
Unfortunately, it also remains uncomfortable, especially if you frequently change the structure of the template.
Ah yea, then I'd recommend using a development environment. It's never smart to make design-breaking changes to your production installation.
Also, I have many problems with the theme I used so I utilized the custom CSS option in the ACP. It gets included on every page after the other css files so you can overwrite and directives and it applies immediately, no cache necessary.
A development environment is a secondary install of nodebb that your users don't know about. Maybe it's installed on your local computer or on a cheap VPS somewhere on the internet. It's primary purpose is to contain volatile changes to your site. You can do whatever you want, break it, tear it down, reinstall from scratch, etc and your users are unaffected.
So you do your changes to your templates, get them looking exactly how you want and everything working right. Then you push those changes to your production server and display them to your users.
@KingCat
All right. Thanks for the help!
You're welcome. I hope you get it working how you want it 
I thought about why the problem appeared only in the new version 0.7.0-dev?
The stable version 0.6.1 of the problem was not observed.
Was added function that creates this inconvenience?
If so, I would like to delete it. Unfortunately, I am not good.
@yariplus said:
Yeah, this is definitely an issue that needs fixing. I'm sure they'll fix it before release though.
Clearing cache of course works, but it's completely unrealistic to expect users to do this. (I had to look up a tutorial just to figure out how to clear cache in chrome.
friggin' hate chrome.)
Why do you use Chrome if you hate it?
@rMBP I just use it for testing my plugins. 
