(node) warning: possible EventEmitter memory leak detected. 11 nodebb:ready listeners added. Use emitter.setMaxListeners() to increase limit.
at EventEmitter.addListener (events.js:179:15)
at Object.<anonymous> (/.../node_modules/nodebb-plugin-recent-cards/library.js:8:9)
at Module._compile (module.js:460:26)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Module.require (module.js:365:17)
at require (module.js:384:17)
at Object.Plugins.requireLibrary (/.../src/plugins.js:40:33)
at registerHooks (/.../src/plugins/load.js:82:13)
some users can't use reset password just on Chrome because of invalid csrf token but they are fine with firefox.
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