Possibly related to the new verified-users, unverified-users groups. If your forum had the require email confirmation setting on and you upgraded then registered-users no longer have posting privileges. This is done by the upgrade scripts. But if you reverted without doing a database restore then registered-users won't have the privileges back.
Upgrading and semver
po last edited by
We have a live deployment at concourse.expii.com (forums for www.expii.com, which has 1100 accounts ). I hesitated to upgrade because I was afraid of breaking something and disrupting the userbase, but it's high time to upgrade now.
I am running v0.4.3, and I followed the instructions to migrate to the v0.5.x branch:
git checkout v0.5.x
git merge origin/v0.5.x
I then encountered errors around "semver". I first saw:
npm http 200 https://registry.npmjs.org/socket.io/-/socket.io-0.9.17.tgz
npm ERR! Refusing to delete: /var/nodebb/node_modules/.bin/semver not in /var/nodebb/node_modules/semver
File exists: /var/nodebb/node_modules/.bin/semver
Move it away, and try again.
npm ERR! System Linux 3.14.23-22.44.amzn1.x86_64
npm ERR! command "node" "/usr/bin/npm" "install"
npm ERR! cwd /var/nodebb
npm ERR! node -v v0.10.26
npm ERR! npm -v 1.4.6
npm ERR! path /var/nodebb/node_modules/.bin/semver
npm ERR! code EEXIST
npm http GET https://registry.npmjs.org/type-is/-/type-is-1.5.3.tgz
and later, I also saw:
Error: Cannot find module 'semver'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object.<anonymous> (/var/nodebb/app.js:28:11)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Function.Module.runMain (module.js:497:10)
Is there a step that I am missing? Or is it just not possible to upgrade from v0.4.3 -> v0.5.5?
Thanks very much for building this awesome software! It's great!
po last edited by
Update: I seem to have fixed this with
npm install semver
Glad to hear it
Hope everything's going well over at Expii!