@Lingyong-Zhang said:
@baris I see, my site use the mongodb , 1 core/1G VPS, but it alway go wrong
previous , I use the redis , but now I use the mongodb. I don't know which is good
I have latest version of nodebb pulled from master.
This happends when I try to click on register ( sign in works good):
TypeError: Converting circular structure to JSON
at Object.stringify (native)
at ServerResponse.res.json (/Users/user/Code/Projects/forum/node_modules/express/lib/response.js:185:19)
at ServerResponse.res.render (/Users/user/Code/Projects/forum/src/middleware/middleware.js:321:15)
at Object.<anonymous> (/Users/user/Code/Projects/forum/src/controllers/index.js:214:7)
at Object.Plugins.fireHook (/Users/user/Code/Projects/forum/src/plugins.js:362:14)
at Controllers.register (/Users/user/Code/Projects/forum/src/controllers/index.js:210:10)
at callbacks (/Users/user/Code/Projects/forum/node_modules/express/lib/router/index.js:161:37)
at param (/Users/user/Code/Projects/forum/node_modules/express/lib/router/index.js:135:11)
at pass (/Users/user/Code/Projects/forum/node_modules/express/lib/router/index.js:142:5)
at nextRoute (/Users/user/Code/Projects/forum/node_modules/express/lib/router/index.js:100:7
@a_5mith hm this does not help. I have reseted all plugins, cleared cache as well and can not register into my app w/o plugins. I am on master with latest commit 2e49fe9 2014-05-18
Same problem happens to me. Clicking on "Register" link in navigation results in error message "Error
Converting circular structure to JSON". Using latest from github
Thanks for reporting.
Ok, so... is this fixed? I'm a bit confused because both issues are closed.
https://github.com/designcreateplay/NodeBB/issues/1540 is open, so not fixed.
@baris Hmm, okay. I guess I misread the labels. >.<
Until #1540 is resolved, and if you are on master
branch, please either downgrade to v0.4.x
branch, or use the following stable(-er) hash: 6ec36a00ad7828041346f55013374f2eee579480
git reset --hard 6ec36a00ad7828041346f55013374f2eee579480
Switching to the hash version given, fixes it. Thanks.
@julian said:
git reset --hard 6ec36a00ad7828041346f55013374f2eee579480
In my case, the given hash does not seem to fix the problem
Or am I doing something wrong? I entered git reset --hard 6ec36a00ad7828041346f55013374f2eee579480
, then git pull
(?) and lastly ./nodebb upgrade
@markkus Just run the git reset
command. If you run git pull
and ./nodebb upgrade
, you'll just bring yourself right back up to the latest (unstable) commit!
This is fixed on latest master btw.