... then find out again what the problem is.
@Pablo-Macaluso What is the error when you start NodeBB with ./nodebb dev?
Perhaps the merge did not work. You have to give me more information.
Keeping in line with our pledge to release more often, v0.7.3 has shipped today. It contains mostly bugfixes as well as some enhancements towards favicon and improved IE support.
One big change is the update to the NodeBB Package Manager, which was updated to accommodate changes to the npm api. To combat perceived "brokenness" of plugins, we're introducing the following changes to the package manager:
package.json, your plugin will no longer appear in ACP/Plugins
PUT https://packages.nodebb.org/api/v1/suggest?package=nodebb-plugin-yourpluginif you want nbbpm to refresh its record for your plugin immediately.
v0.6.xbranch users, your copy of NodeBB does not pass the current NodeBB version to nbbpm, so nbbpm won't know what plugin list to send you, as a result, your ACP/Plugins page will be empty. You are advised to upgrade to v0.7.x.
I am receiving this error upon updating:
1. Bringing base dependencies up to date 2. Updating NodeBB data store schema module.js:340 throw err; ^ Error: Cannot find module 'nconf' 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> (/home/simonq/bbirdie/app.js:23:13) 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) Error: undefined
I always seem to get a mini heart attack whenever I run these updates lol
Why does this always happen
Can you move
node_modules/ out of the way, run
npm install, and then
node app --upgrade? That's
./nodebb upgrade in a nutshell (except for the first part).
@julian Move out of the way as in delete it?
rm -rf node_modules/?
Yeah, or just
mv node_modules/ node_modules_bak
This update went flawlessly for me, Great work.
I'm sure redis is installed...
Clustering enabled: Spinning up 1 process(es). 18/8 15:28  - info: Time: Tue Aug 18 2015 15:28:14 GMT-0400 (EDT) 18/8 15:28  - info: Initializing NodeBB v0.7.3 18/8 15:28  - error: Unable to initialize Redis! Is Redis installed? Error :Cannot find module 'connect-redis' [cluster] Child Process (8904) has exited (code: 0, signal: null)
Edit: finally got it to work
I'm currently on 0.7.2 and want to upgrade to 0.7.3. Never done this before. After backing up everything, is this what I should do?
$ cd nodebb $ ./nodebb stop $ git pull $ ./nodebb upgrade
@henrywright Ah, good of you to check.
./nodebb upgrade isn't working as it should at the moment. Instead, please run
npm i && node app --upgrade.
The problem is being investigated...
@julian Thanks for replying so quick. I'll hold off just for the moment until you guys put out the fire
@henrywright Ok, latest commit in
v0.7.x branch contains the fix for the broken
./nodebb upgrade call.
If you want to upgrade, those are the steps, although also
cp -r node_modules/ node_modules_bk just to back up the node_modules folder.
Let me know if it works
@julian Upgrade seems to have gone smoothly (including
./nodebb upgrade). Now running 0.7.3. Thanks!
One thing I did have to do was clear my browsing data because I was getting some 502 Nginx error pages show up. Since clearing all browsing data everything has been fine.
Setting homepage as recent renders the following error
Internal error. Oops! Looks like something went wrong! / Object # has no method 'recent'
Navigating to URL/recent renders the page just fine.
18/8 18:27  - error: / TypeError: Object #<Object> has no method 'recent' at Controllers.home (/home/a_5mith/35hz/src/controllers/index.js:45:27) at Layer.handle [as handle_request] (/home/a_5mith/35hz/node_modules/express/lib/router/layer.js:95:5) at next (/home/a_5mith/35hz/node_modules/express/lib/router/route.js:131:13) at /home/a_5mith/35hz/src/middleware/middleware.js:74:3 at Object.async.each (/home/a_5mith/35hz/node_modules/async/lib/async.js:118:20) at middleware.pluginHooks (/home/a_5mith/35hz/src/middleware/middleware.js:70:8) at Layer.handle [as handle_request] (/home/a_5mith/35hz/node_modules/express/lib/router/layer.js:95:5) at next (/home/a_5mith/35hz/node_modules/express/lib/router/route.js:131:13) at middleware.pageView (/home/a_5mith/35hz/src/middleware/middleware.js:62:4) at Layer.handle [as handle_request] (/home/a_5mith/35hz/node_modules/express/lib/router/layer.js:95:5)
@a_5mith nice catch fixed on master and 0.7.x
nbbpm.compatibility is using semver syntax, correct?
nbbpm.compatibility is using semver syntax, correct?
Yes, a semver range.
If your plugin works with 0.7.0 and up, use
^0.7.0, you'll have to trust us not to introduce breaking changes in the
If it is compatible with 0.6.1 and up, for example, use
>= 0.6.1 ^0.7.0
error after upgrade. im using mongo database.
[cluster] Child Process (6671) has exited (code: 0, signal: null) at Function.Module._load (module.js:278:25) at Module.require (module.js:365:17) at require (module.js:384:17) at module.init (/root/nodebb/src/database/mongo.js:52:18) at /root/nodebb/node_modules/async/lib/async.js:653:23 at fn (/root/nodebb/node_modules/async/lib/async.js:638:34) at Immediate._onImmediate (/root/nodebb/node_modules/async/lib/async.js:554:34) at processImmediate [as _immediateCallback] (timers.js:367:17)```
I have always git pull master, and always has this
Error : cannot find module .... I did try
npm install, but nothing works. Even changing branch
git checkout v0.7.2 still showing
cannot find module.
The only thing work for me is, to remove all node_modules then install it back. After that, I did npm install redis and connect-redis.
// remove all node_modules rm -rf node_modules/ // re-install dependencies npm install // install redis and redis-server npm install redis npm install connect-redis