I don't think so, probably something to do with cookies changing. I'm guessing you need to call redirect or status.send to avoid the error.

https://github.com/NodeBB/NodeBB/blob/master/src/controllers/authentication.js#L292-L296

It should totally be possible. Rest APIs are available for everything you would need.

Is there a reason you are using such an old version of NodeBB?

@dinendal It's in the req.body object.

@dinendal Sure. It would be an unusual method of logging in, but there's nothing stopping your plugin from calling the login controller with the request object.

https://github.com/NodeBB/NodeBB/blob/master/src/controllers/authentication.js#L302

NodeBB Widget Game-Server-Query

Fork Me

This plugin adds one widget. The widget is a wrapper for game-server-query.

In the widget settings, you can define a game server to query and a template to parse using the returned status.

Queries run on a separate process, so as not to slow down the main process.

@jjsagan No, everything would go on the first page. The second page's js would just read ajaxify.data.yourvariable

I'm assuming you want to both render the variables in the second page's template, and use them in the second page's JS. If you just want to read them with JS, passing them in the url as baris says above is the easier option.

One option, if you listen to action:ajaxify.dataLoaded, any changes to the data parameter are passed to the template render. For example, running this script below will change the first category to TEST

let myNewCategory = 'TEST'
$(window).one('action:ajaxify.dataLoaded', (e, params) => {
  if (params.data && params.data.categories) params.data.categories[0].name = myNewCategory
})
ajaxify.go('categories')