NodeBB v0.4.1 Released

[frissdiegurke]

@manuel Isn't it listed here?

[psychobunny]

Yup, it's on the official instructions. But sometimes even I forget to run it myself Glad you got it up and running though

[manuel]

Upgrading between patch revisions

e.g. v0.1.0 to v0.1.1

Patch revisions contain bugfixes and other minor changes. Updating to the latest version of code for your specific version branch is all that is usually required.

Execute steps 1 through 3.

always 1 through 4 then

[psychobunny]

Good catch. I'd say you should do all 4 steps for upgrades regardless of what version you're upgrading from, as a precaution - it doesn't hurt either way. Should update the wiki

[g6123]

I got performance degradation after upgrading to 0.4.1.
It has become terribly slow.

[julian]

@g6123 I believe we've fixed this, and re-published v0.4.1. Please do a git pull to retrieve the fixes. Sorry about that!

[Sp4rkR4t]

Noticed on this site when I click the Unread button the mark all read icon is black with a Mark_All_Read text that does nothing, if you then F5 the page it loads normally.

[finid]

@Sp4rkR4t

There's a magic solution to that: Clear your browser's cache. In the latest code, clicking on it should give you a dropdown menu.

[manuel]

remember that we couldn't ask anyone to clear browser cache after any upgrade

[julian]

@manuel Actually, I thought we were done with having people clear their caches -- not quite sure why it persisted this time.

[manuel]

@julian i have some issues too after upgrade. some users are getting error 403 when going to notifications page, i asked them to clear browser cache, tomorrow i'll know if it worked
i also noticed that when i open a user profile the first time i don't see the "edit" button, if i refresh it appears

[g6123]

@julian Oh, thanks.. Even though I had upgraded to 0.4.1, the problem remained, but when I completely removed all the files (not mongoDB) and reinstalled it, it has been fixed!

[Leonardo Galani]

Now its working on my company proxy