The themes are mixed - Now Nodebb don't work - Help Me.

Master-Antonio

@hek Yes i know, but it does not solve anything.
With each refresh must clear the cache.

julian

Have you restarted your NodeBB after changing themes? To my knowledge, this is still required

Master-Antonio

Have you restarted your NodeBB after changing themes? To my knowledge, this is still required

Yes.
So i returned to version 0.6.1
Help me here please.
https://community.nodebb.org/topic/4389/same-plugin-don-t-work-also-emojii/2

julian

If you've downgraded back to v0.6.1, please reinstall the dependencies:

$ rm -rf node_modules/
$ npm i --production
$ ./nodebb setup

a_5mith

I thought you couldn't drop back major versions? Especially 0.7.x to 0.6.x.

teh_g

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.

EDIT: It looks like the easiest way to reproduce this is to change the theme. Any user that has the old theme cached on their system will run into this issue.

julian

@a_5mith You're right, you can't downgrade.

KingCat

Yep, I had the same problem. I had to uninstall all but the main theme I was using otherwise It kept colliding with the chosen theme. The main issue was the main container was being switched to container-fluid by some javascript that was loaded by an unused theme.

julian

I don't see this happening when switching from Lavender to Vanilla and back... under what themes does this switching bug out?

KingCat

I'm using persona and i had lavender, vanilla, and a few of the other non-stock themes installed. I did a grep for "container-fluid" in the javascript of all the theme folders and found that some of them have code to change container to container-fluid (which is what my issue was) so I simply deleted them figuring their code was being included somehow and it immediately fixed the issue.

? Offline

@KingCat said:

I'm using persona and i had lavender, vanilla, and a few of the other non-stock themes installed. I did a grep for "container-fluid" in the javascript of all the theme folders and found that some of them have code to change container to container-fluid (which is what my issue was) so I simply deleted them figuring their code was being included somehow and it immediately fixed the issue.

Could you describe in more detail how you did it?

This bug brings a lot of inconvenience.
It is strange that it has not yet been resolved.

KingCat

@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.

? Offline

@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.

KingCat

@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.

? Offline

@KingCat

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.

I want to edit the theme (add or remove any items)
I turn to the folder: /www/node_modules/nodebb-theme-persona
Change necessary elements to me. For example, delete button "reply"
Then reboot the forum.
As a result - If you go to any topic, the button 'reply' it will be in place, even though we have removed it.
...but worth to refresh the page - the button is removed.

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.

KingCat

@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.

? Offline

@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.

KingCat

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.

? Offline

@KingCat said:

development environment

development environment - what exactly is it?

KingCat

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.