I was using "build & restart". I've done that many times since deactivating the chat. Now though, it's not showing that error about the chat either.

I first disabled the chat immediately after installing it over a week ago. I've done the rebuild and reload more than a dozen times since then. So that's really weird. I didn't see the icon for it after disabling it, but I was getting those errors in the browser console.

Only thing I can think is that most of the "rebuild & reload" where clicking the notification in the bottom left that said to do so rather than from the main dashboard page.

I'm using 1.7.5. The only thing was a warning
warn: [plugins/load] The following plugins may not be compatible with your version of NodeBB. This may cause unintended behaviour or crashing. In the event of an unresponsive NodeBB caused by this plugin, run ./nodebb reset -p PLUGINNAME to disable it.

• nodebb-plugin-composer-default

But it turns out I do see the configuration in the admin panel for the "wordpress SSO" a day later.
I had caching disabled with cloudflare, so I'm not sure what the deal was/is there. But I guess it works now.

I do get a ton of errors on the client in the console like
"Error: Script error for "mousetrap", needed by: forum/chats" despite having the chat disabled, which is odd. But I guess it kind of works now for some unknown reason.

First I tried a poll plugin. It was old and broken. Oh well.

Next, I need to make an SSO login plugin. First I wanted to look at how others do it and hook into and override the login as a starting off point.
First I tried nodebb-plugin-ns-login, as it seemed closest to what I was looking for. And it was last updated 4 months ago, so seems current enough.
I check the login page, and it's the same nodebb login.
So next I try nodebb-plugin-sso-wordpress, one by a nodebb founder. Same thing.

I've made sure they're set as active.
I've rebuilt and reloaded multiple times.
I tried removing the slick theme and using the starting "Persona" theme, thinking that might be the problem.

@julian I see. Well I'm trying to basically port Vanilla's plugin to Nodebb, but I'm not sure if I'll be able to so it'd be cool if you devs had some official, simpler solution like it.

Vanilla's is really easy. You give it the url for your registration and login page, and a url where it expects JSON to return for a users name, email, etc if they're logged in. If they're logged in, it creates a Vanilla forum user for them if one doesn't already exist. If they already on, it just logs them in normally as if they typed in their username and password on the Vanilla forums.
So no matter what auth system you use, you can use your own API to output the JSON it wants, so long as the client-id and secret key supplied matches up as well. I have my own accounts system and it took me like <1 hour to read the documentation for how to set it up with Vanilla's and do a custom implementation.
Reading the oauth plugins on the other hand, I'm rather clueless on what I need to do to make it work for my own, and what I need on my own site's end of things. Like looking at the BNET plugin, I can't figure out what "clientID: process.env.BNET_ID" and "clientSecret: process.env.BNET_SECRET" are, among other things. It's just too in depth for something that should be simpler.

edit: Actually I see what the process.env are. They're user environment variables. But well, still, the oauth sso is way more complicated than I think a lot of people will want.
Like if I want to replace the profile, I'd rather that have a separate plugin replacing the profile. Not part of the OAuth implementation. I imagine I can just cut that out while forking, but still. I wish there was something as simple as Vanilla's JSONP SSO.

And as I look through more, I'm not seeing why authorizationURL, tokenURL, clientID, clientSecret can't just be on settings pages instead of constants, with an oauth/oauth2 radial.

That was it.

Ah, I should have noticed that, looking at some other plugins. Thanks.

I must still be missing something, since I'm still getting the

/api/admin/plugins/json-auth Not Found

Maybe I'm missing something with the path itself. Let me copy more of it, so maybe it'll become clear

	Author.addAdminLink = function(custom_header, callback) {
		console.log('admin link call from json-auth...'); //logs fine
		custom_header.plugins.push({
			"route": "/plugins/json-auth",
			"icon": "fa-book",
			"name": "JSON Auth"
		});

		callback(null, custom_header);
	};

	function renderAdmin(req, res, next) {
		console.log('render called', req, res); //this is not getting logged, so it must not get called!
        res.render('admin/plugins/json-auth', {});
    }

	Author.init = function(params, callback) {
		console.log(' --- init hook called'); //logs fine

		params.app.get('/admin/plugins/json-auth', params.middleware.admin.buildHeader, renderAdmin);
		params.app.get('/api/admin/plugins/json-auth', renderAdmin);

		callback();
	};

It's my understanding that the "/api/admin/plugins/json-auth" error is from that page being requested. And "params.app.get('/api/admin/plugins/json-auth', renderAdmin);" should be called on its request, which should call that function to "res.render('admin/plugins/json-auth', {});". But that function isn't being called.
I can't see what I'm still missing, there.

Ah yes. I see that now. Thanks!

So, I'm trying to add some settings into the admin panel for a plugin I'm trying to make. But right away, I'm having trouble figuring out how to get a page to come up in the admin panel for the settings.

I looked at the dbsearch plugin among some others to try and figure out how, since I couldn't find much in the docs.

So from there, in my library.js I have this:

	Author.addAdminLink = function(custom_header, callback) {
		custom_header.plugins.push({
			"route": "/plugins/json-auth",
			"icon": "fa-book",
			"name": "JSON Auth"
		});

		callback(null, custom_header);
	};

The "JSON Auth" button comes up fine in the admin panel, but when I click it I get

/api/admin/plugins/json-auth Not Found

I set up the directory structure to match how dbsearch's is, with
nodebb-plugin-json-auth/templates/admin/plugins/json-auth.tpl

<h1>JSON Auth</h1>
<hr />

<form>
	<p>
		Auth Settings
	</p>
	<div class="alert alert-info">
		<p>
			<label>Client ID <br /><small>Unique ID for the site</small></label>
			<input type="text" data-field="json-auth:id" title="Client ID" class="form-control" placeholder="randomness123">
			<label>Secret Key <br /><small>Secures the authentication. Do not give it out to anyone.</small></label>
			<input type="text" data-field="json-auth:secret-key" title="Secret Key" class="form-control">
			<label>Site Name <br /><small>Displayed on buttons to users</small></label>
			<input type="text" data-field="json-auth:name" title="Site Name" class="form-control" placeholder="My Site">
			<br />
			<label>Auth URL <br /><small>URL that will be called that should supply the user information as JSON</small></label>
			<input type="text" data-field="json-auth:auth-url" title="Auth URL" class="form-control" placeholder="http://path.to/auth">
			<label>Login URL <br /><small>URL where someone logs in if they aren't already.</small></label>
			<input type="text" data-field="json-auth:login-url" title="Login URL" class="form-control" placeholder="http://path.to/login">
			<label>Registration URL <br /><small>URL for new user registration</small></label>
			<input type="text" data-field="json-auth:registration-url" title="Registration URL" class="form-control" placeholder="http://path.to/register">
			<br />
		</p>
	</div>
</form>

<button class="btn btn-primary" id="save">Save</button>

And in plugin.json I've included

	"staticDirs": {
		"templates": "./public/templates",
		"json-auth": "public"
	},
	"templates": "./public/templates"

I'm not sure what I'm missing here.

@a_5mith said:

The doc is over two years old. so does contain out of date info.

Refer to the documentation, it'll likely be more up to date. Link to Documentation

That's where I found that to begin with. It didn't mention needing a package.json https://docs.nodebb.org/en/latest/plugins/create.html so that needs to be added.

@a_5mith said:

@Sadtaco Use this as a guide, but you need library, plugin & package as a minimum usually.

That was it. nodebb does not recognize it without a package.json as well. The docs make no mention of that and only go over plugin.json and the js file.

@KingCat said:

@Sadtaco said:

Even if the solution is "use OAuth", there should at least be a NodeBB plugin that has those settings to input for those URLs for your OAuth landing.

Yea, there is, it's called nodebb-plugin-sso-oauth. It's what I finally ended up using to integrate my site. It works pretty well actually.

That's not a complete plugin, though. I don't fully get what I would need to fill in to have it work if I were to fork it. And if I were to fork it, then I'd have a public plugin for my private accounts.
A full plugin would have an admin page where you input what is needed, and more of a guide on how to set up the OAuth end of things where the accounts are.

I tried following this, and I can't even get the basic "hello, world" logging.

nobebb/node_modules/nodebb-plugin-json-auth/package.json

{
	"id": "nodebb-plugin-json-auth",
	"version": "0.0.1",
	"name": "NodeBB JSON remote Authentication",
	"description": "Replaces NodeBB login with a remote location.",
	"library": "./library.js"
}

nobebb/node_modules/nodebb-plugin-json-auth/library.js

console.log('hello, world!');

When I look in Advanced > Logs I can see the "reloading..." and such logged, but there is no "hello, world!". It doesn't appear in Extend > Plugins, either.

Thanks a bunch of this plugin.

I really like how Vanilla Forums does it. http://blog.vanillaforums.com/help/vanilla-jsconnect-single-signon-on/

You provide a page that gives it the information someone needs when they're logged in https://github.com/vanilla/jsConnectPHP/blob/master/index.php
Then it has a plugin for the forums itself where you give it the URL for your registration page, and URL for that auth page.

Even if the solution is "use OAuth", there should at least be a NodeBB plugin that has those settings to input for those URLs for your OAuth landing.