Common Errors
As of right now, the 0.5.1 branch no longer exists. It and the more recent changes have been merged into the master branch.
NodeBB v0.4.1 Released
-
It's been almost two months since v0.3.2 but we hope it's been worth the wait! The NodeBB team is proud to announce the release of version 0.4.1, chock full of performance upgrades, new features, and as always, a ton of new languages!
What's new in NodeBB v0.4.1
Click here to see the full blog post
-
First! Nice new features
except this one:Improved support for older browsers (IE8)
-
ahah. IE should be in it's own category.
- New browsers
- Old browsers
- Internet Exploder.
-
i've just run (from v0.4.0) stop + git-pull + start and the admin stopped working
ReferenceError: utils is not defined app.js:37
require.js:8
TypeError: socket is undefined footer.js:30
TypeError: socket is undefined app.js:227
TypeError: socket is undefined app.js:227
Error: Script error for: forum/admin/events
I had to add a ./nodebb upgrade and now it works
Should the upgrade wiki on github be upgraded then?
-
-
Yup, it's on the official instructions. But sometimes even I forget to run it myself
Glad you got it up and running though -
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
-
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
-
I got performance degradation after upgrading to 0.4.1.
It has become terribly slow. -
@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!
-
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.
-
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.
-
remember that we couldn't ask anyone to clear browser cache after any upgrade
-
@manuel Actually, I thought we were done with having people clear their caches -- not quite sure why it persisted this time.
-
@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 -
@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!
-
Now its working on my company proxy
