[Solved] Lavender Theme Issues after 0.5.1 Upgrade?

[Netto Hikari]

Hello, folks.

Lately I didn't have much time to work on NodeBB docs and my own projects, sorry. (same reason I didn't respond to any topics here)

I finally got some time to upgrade my still unfinished website to version 0.5.1 and got these issues on the main page:

The categories are being displayed weirdly and I'm also having problems with the width of the main page. The "dynamic / fixed width" button isn't there any more. Also, the sidebar container and the categories are very close together (not visible on the screenshot).

Any clue? I wonder what I did wrong this time...
~ Netto

[a_5mith]

Can you try running the following

npm install nodebb-theme-lavender@latest
npm install nodebb-theme-vanilla@latest

Then clear your cache & reload NodeBB.

[A Former User]

I'd remove the themes, then reinstall them. I had an issue yesterday with the themes after upgrading and these were the commands I needed to run.

npm rm -rf nodebb-theme-lavender
npm rm -rf nodebb-theme-vanilla
npm i

Installing the @latest themes pulled incompatible files with the 0.5.1 build.

[a_5mith]

@Ted said:

I'd remove the themes, then reinstall them. I had an issue yesterday with the themes after upgrading and these were the commands I needed to run.

npm rm nodebb-theme-lavender
npm rm nodebb-theme-vanilla
npm i

Installing the @latest themes pulled incompatible files with the 0.5.1 build.

You would have needed to use -rf with that command as they're folders, not files. But fair enough. I'm attempting an upgrade on my test server to make sure.

[A Former User]

@a_5mith I have no idea what you mean by that

[a_5mith]

@Ted If you're removing a folder in Ubuntu, you would need to add -rf or it won't work. The -r part means recursive, so it would remove the nodebb-theme-lavender folder, and any folder inside it. Without the -r part, you would get file is a directory, not deleting. Or words to that effect. The -f is just to do it without needing you to ok each folder.

[A Former User]

@a_5mith, Oh I knew that haha. I was trying to play coy and ninja edit.
Of course, that's impossible when you're 11 minutes late to the party.

[a_5mith]

@Ted said:

@a_5mith, Oh I knew that haha. I was trying to play coy and ninja edit.
Of course, that's impossible when you're 11 minutes late to the party.

Fashionably late.

Edit: It's rayman.

[Netto Hikari]

@a_5mith @Ted

I tried those solutions already. Sadly, they didn't have any effect. Cache is cleared, NodeBB is restarted. Maybe I dun goofed again. To be honest, I find git very confusing and I don't like the upgrade process of NodeBB. Maybe I made a mistake somewhere.

Even though I'm a Java and .NET developer, I never came around using git for some reason.

[a_5mith]

@Netto-Hikari said:

@a_5mith @Ted

I tried those solutions already. Sadly, they didn't have any effect. Cache is cleared, NodeBB is restarted. Maybe I dun goofed again. To be honest, I find git very confusing and I don't like the upgrade process of NodeBB. Maybe I made a mistake somewhere.

Even though I'm a Java and .NET developer, I never came around using git for some reason.

So you did the ./nodebb upgrade bit? What widgets/plugins are you running?

[Netto Hikari]

@a_5mith Yes, I did do the upgrade bit.

I'm using no widgets currently. They have been deleted / disabled when I tried switching themes a few days ago (my website is more a testing ground than an actual production website). These are my current plugins. I'm gonna try and disable them to check if one of them is causing the issues.

Edit: Yes, a plugin is causing it. Let's check it...

[Netto Hikari]

Double post for solution: Shuffle Signature is the culprit.