@Hưng-Thành-Nguyễn are you using Wordpress or Ghost?

Just a heads up for anyone else using this with Wordpress. After the latest update the categoryID variable in comments.php of your theme isn't optional. If it isn't defined publishing doesn't work.

Experiencing this issue on Wordpress as well.

Yep, and that's indeed what I've ended up doing. It doesn't feel as nice as it could be but it will do.

If there is a hook to use during connection/cookie check on the server side I'll gladly use it. That hook though doesn't seem to fire on its own.

When a player accesses our forums we're checking if a cookie exists on the client and if it does we send a post to /login to log the player in using our existing accounts system. The login works but it requires a refresh to show the player as logged in. Is there some event I should be listening for, or some signal I should be sending to the client to force it to update?

Likely going to take an existing one and modify it for now. Hitting Greenlight on Thursday with a show in Mississauga this weekend.

Thanks @psychobunny!

Seems to ignore the login override I have in place. Perhaps POST is better. To use POST I need CSRF included but no combination of require, define, etc with ['csrf'] as an argument is loading csrf.

require(['csrf'], function(csrf) {
	console.log(csrf);
}

If anyone has a better suggestion I'm all ears. Looking for deep integration into our site/system without needing to login multiple times. Login will happen on our accounts page/main site. If someone visits the forums I want to grab their info (id/authkey) stored in a cookie and pass it onto the forums to verify their login without any user interaction. I'd like to use as much of the existing framework in nodebb as possible and simply plugin to our existing API to verify the info. I've managed to do the last part no problem using action:auth.overrideLogin.

Rather than send the required data via socket?

Sorry, another question.

Once the data hits the server I want to be able to call login. Logging into the forums needs to be invisible to the user and is tied into our existing login system. Is this a possibility? What function do I need to call on the server to begin the login process, with the data sent via the socket.

Perfect, thanks!

Quickstart plugin helps a lot, thanks!

Looking through its code I've now got another question.

socket.emit('admin.reload');

It is possible to emit a custom signal from the client side upon "action:connected" and have the server listening for it?

That's exactly what I'm looking for, do I use the action:connected hook for that? How do I register my plugin with the client?

Attempting to use the "action:connected" hook but can't seem to get this simple plugin to execute. I'm guessing I've done something wrong in my plugin.json or the code itself.

plugin.json

	"id": "nodebb-plugin-clienttest",
	"name": "NodeBB Client Test",
	"description": "NodeBB Plugin",
	"url": "http://www.osnapgames.com",
	"library": "./library.js",
	"hooks": [
		{ "hook": "action:connected", "method": "connected" }
	]
}

library.js

var	plugin = {};
 
plugin.connected = function() {
	console.log("CONNECTED");
};
 
module.exports = plugin;

http://community.quasargame.com

I do!

Uncaught SyntaxError: Unexpected token &
nodebb.min.js?0eb3d036:14

Uncaught TypeError: Cannot read property 'maxReconnectionAttempts' of undefined
socketIOConnect @ nodebb.min.js?1431043735683:18915
(anonymous function) @ nodebb.min.js?1431043735683:19495
(anonymous function) @ nodebb.min.js?1431043735683:19509

Uncaught TypeError: Cannot read property 'loggedIn' of undefined
(anonymous function) @ nodebb.min.js?1431043735683:19260
jQuery.Callbacks.fire @ nodebb.min.js?1431043735683:3087
jQuery.Callbacks.self.fireWith @ nodebb.min.js?1431043735683:3199
jQuery.extend.ready @ nodebb.min.js?1431043735683:433
completed @ nodebb.min.js?1431043735683:104

[email protected] /home/overlawled/nodebb
└── [email protected]

[email protected] /home/overlawled/nodebb
└── [email protected]

Using nodejs v0.10.37, redis 3.0.0, and nodebb 0.6.1 through a nginx proxy. I've run npm up, cleared nginx cache and restarted it.

6/5 20:50 [3348] - error: /login
ForbiddenError: invalid csrf token
at verifytoken (/home/overlawled/nodebb/node_modules/csurf/index.js:268:11)
at csrf (/home/overlawled/nodebb/node_modules/csurf/index.js:96:7)
at Layer.handle [as handle_request] (/home/overlawled/nodebb/node_modules/express/lib/router/layer.js:82:5)
at next (/home/overlawled/nodebb/node_modules/express/lib/router/route.js:110:13)
at Route.dispatch (/home/overlawled/nodebb/node_modules/express/lib/router/route.js:91:3)
at Layer.handle [as handle_request] (/home/overlawled/nodebb/node_modules/express/lib/router/layer.js:82:5)
at /home/overlawled/nodebb/node_modules/express/lib/router/index.js:267:22
at Function.proto.process_params (/home/overlawled/nodebb/node_modules/express/lib/router/index.js:321:12)
at next (/home/overlawled/nodebb/node_modules/express/lib/router/index.js:261:10)
at Function.proto.handle (/home/overlawled/nodebb/node_modules/express/lib/router/index.js:166:3)