General Discussion

@Nguyen-Nga That particular problem is due to a query we want to run against socket.io being unavailable in the latest version. It presents when used in a clustering setup, and the latest changes to NodeBB always have clustering active (even in a cluster setup of 1 process), so in the meantime it is difficult to get the data in question. This is why those graphs are not working at the moment.

@Reik Thanks for the tip. It seems to have converted the config to a different format (ie: instead of base_url it now uses url) and it's working. Seems odd that everything would fail all of a sudden without any changes. @psychobunny @julian Is there some kind of automatic update in v0.5 that is outside of normal nodebb operation?

@RazorAxis the only thing I can think of is that some CSS style aren't being recognized by Firefox and IE for whatever theme you're using. I wouldn't expect this to happen though, since we're using bootstrap.

Should make some more noise when you update an amazing piece of software such as NodeBB

The sm-3 or 4 did not change the tablet in vertical but at least it now changes in horizontal. Gus that will have to do for now. Thank you for the help @yariplus

Darn, screwed that up huh.... Thanks @a_5mith

@baris Much pending, I put some of my own cash in too though.

Oh yeah just realized reading it again sorry Check out this is you need better hosting https://community.nodebb.org/topic/3630/nodebb-hosting-option-for-people-interested

Very Good but HapHost is very very BAD. NodeBB don't work. 128 Mb of RAM are to few. Already installing plugins the site crash, because VPS arrives at the maximum of RAM. OMG. Very Bad. Without do NOTHING. RAM : http://i.gyazo.com/2b0fcbb3c8a36dd3d0b40199393c59c3.png CPU : http://i.gyazo.com/33656ee25ef23e9fec43dce06458caaa.png FUCK.

@Schamper hi ! Have you found where this problem come from ?

I found a fix. It was an error in nodebb. When I did ./nodebb setup I made a typo in the port.. oops .-. Anyway its all good now.

Hi, I need some advice in connecting small sails.js app with nodeBB. In my sails.js application I need to get current logged user. I set sails.js session id key to express.sid (as in nodeBB), and configured it to use nodeBB collection as session storage. Then I can query for user id by session id (also from nodeBB storage). It is almost what I need to, but I can't get through some problems nodebb and sails app have to be on same domain when user visits sails app first, then nodeBB sets another session id and sessions are different on both apps when user logs in nodeBB, gets new session id and also, sessions are different on both apps Maybe OAuth is best way to go? Thanks PS. Thanks for nodeBB, great work!

The popup is a bootstrap modal.

@Technowix there are performance gains related to the new structures in ES6 (generators, async functions, classes, ect.) There also may be performance gains since they are updating the internal version of V8 to the latest stable version (Node is still on an older version from what I understand).

I'm learning something new here everyday! Muchas gracias Señor

Possible through session sharing... if the cookies both have the same secret...

In a nutshell, because database abstraction layers make compromises...

@baris, will that fix it so the drop down comes back?

@a_5mith said: git checkout v0.6.x git pull ./nodebb upgrade that worked. let me backup and then check out the master.

Learn Javascript first, then head onto Node.js