So I've been working with NodeBB for a while now and am familiar with several concepts, but one thing I'm not sure about.

If I want to add data to the "global scope" before render. How would I do that?

I know how to get data to the page templates, but that doesn't carry over into the global templates, like the sidebar menu.

How can I, for instance, fetch my categories and place them in the sidebar?

I'm getting all available categories for a user with categories.getCategoriesByPrivilege. Then I append to it with
categories.getRecentTopicReplies. I'm not getting what I want, only the top post (reply).

What I want is the following; a list of all topics with recent posts (preferably with a max limit in time range), within my available categories. What the client I'm working for want is a feed type thing with all recent activity displayed in one single flow. Then I will also drill down into specific categories but I think I've got that covered.

This is where I'm at so far:

Controllers.renderFeedPage = function (req, res) {
	if (!req.uid) {
		res.render('feed', {});
	}
	let categoriesData;
	let tree;

	async.waterfall([
		(next) => {
			categories.getCategoriesByPrivilege('categories:cid', req.uid, 'find', next);
		},
		(_categoriesData, next) => {
			categoriesData = _categoriesData;

			tree = categories.getTree(categoriesData, 0);
			categories.getRecentTopicReplies(categoriesData, req.uid, next);
		},
		() => {
			const data = {
				title: meta.config.homePageTitle || '[[pages:home]]',
				categories: tree,
			};
			res.render('feed', data);
		},
	]);
};

I haven't found a good example from the forum and I'm reading source code at this point.

If anyone has done something similar I would really appreciate the input and a nudge in the right direction.

Thanks!

Turned out I was fetching the post data wrong. I was using getPostData when i should've been using getPostsByPids.

@baris Just what I needed. Thanks a lot!!

Hi all!
I've run into an issue that when I deploy a new version of my theme/plugin, most users don't get any changes done until they do a hard refresh. This only seems to affect the client side Javascript, so everything looks updated, but in reality functionality gets lost.

Has anyone stumbled upon something similar? Is there a better way to release code?

The background in this is that I have forked Persona and built upon it, so all changes to the platform is basically in the theme. Is there a way to make sure all clients receive all updates?

Thanks!

Thanks for the clarification @PitaJ! I did a lot of experimenting but I guess I didn't get the right combination. I think I never tried naming the module with its extension. That might have been it. For anyone who might be interested in the actual solution, here it is:

In file-explorer.js:

define('azure/file-explorer', ['components'], function (components) {
	const FileExplorer = {};

	FileExplorer.init = function () {
		// Init stuff here	
	});

	return FileExplorer;
});

In plugin.json:

"modules": {
	"azure/file-explorer.js": "static/lib/file-explorer.js"
},

In admin.js:

define('admin/plugins/azure', ['settings', 'azure/file-explorer'], function (settings, fileExplorer) {
	fileExplorer.init();
});

In main.js:

$(document).ready(function () {
	require(['azure/file-explorer'], (fileExplorer) => {
		fileExplorer.init();
	});
});

Thanks for the clarification @PitaJ! I did a lot of experimenting but I guess I didn't get the right combination. I think I never tried naming the module with its extension. That might have been it. For anyone who might be interested in the actual solution, here it is:

In file-explorer.js:

define('azure/file-explorer', ['components'], function (components) {
	const FileExplorer = {};

	FileExplorer.init = function () {
		// Init stuff here	
	});

	return FileExplorer;
});

In plugin.json:

"modules": {
	"azure/file-explorer.js": "static/lib/file-explorer.js"
},

In admin.js:

define('admin/plugins/azure', ['settings', 'azure/file-explorer'], function (settings, fileExplorer) {
	fileExplorer.init();
});

In main.js:

$(document).ready(function () {
	require(['azure/file-explorer'], (fileExplorer) => {
		fileExplorer.init();
	});
});

Only thing that seems to work is using define and placing it in either scripts or acpScripts, but not in both.

@julian, I tried what you suggested and I'm not sure I made a mistake but it doesn't seem like it's accepted as a module. I tried:

"modules": {
	"file-explorer.js": "static/lib/file-explorer.js"
},

and the require it require(['file-explorer.js'], (fileExplorer) => {...}, require(['file-explorer'], (fileExplorer) => {...} and require('file-explorer.js', (fileExplorer) => {...} but nothing seems to work.

It's defined like this:

define('azure/file-explorer', ['components'], function (components) {...});

also tried to do module.exports = fileExplorer without the define part.

Tried to require it with it's defined name azure/file-explorer, but no cigar. The fileExplorer comes out as undefined.

So I'm having an issue which I hope you, the community, can shed some light on. I'm currently building a plugin to incorporate a external storage solution on Azure (not replacing post and topic file storage).

I made a client script that I want to be able to use both in the admin panel and in the forum views. I use define('my-thing/the-script') and add it to plugin.json under scripts.

But I cannot require it in the admin script. Not with require or by placing it in the define function.

I tried to add it in acpScript in plugin.json, but then everything broke.

My last attempt was to make a clone of the original script and appending it with -admin. So, script name, define name, everything. And it worked.

So I guess my question is: Is it not possible to add the same script to both backend and frontend. They both serve the same purpose so just duplicating it doesn't really make sense.

That was it. Had no idea that this was a thing. Thanks a lot @baris!

So my problem is this. I have a theme in which I want to edit composer.tpl. I added my own in my templates folder and made some changes. Nothing major at all, just moving some buttons to other places and such. Then added some styling to match the theme.

When I do local development I run grunt, and the composer template is used.

We have two different cloud environments but it only works on one of them. The weird thing is that they are clones. So exactly the same code base. One one of them the composer template is used, on the other the base one from the composer is there. We're using the redactor composer.

On both environments the CSS created is bundles so the theme is active, it's just that because the template is missing, things are not where they're supposed to be.

So I'm looking for some kind of answer regarding how the templates are built into the build folder, I guess. As I understand, this is how templates are prioritized:

Base --> Theme --> Plugin --> Build

What I find weird is that it's working locally and one one of the cloud environments. Please help, I have spent the better part of a day with a colleague to figure this out, but no cigarr.

Great, then there shouldn't be any issues when the digests are sent for real.

So, we have some modifications to the visual style of the template. Since emails can be a bit tricky to work with I just changed the template tag to [[email:digest.title.{interval}]]. But instead of showing up as digest.title in the emails sent, it now shows up as digest.title.alltime.

I only tried to send a test email so maybe that's the issue. Should I report this as an issue? I guess email:digest.title.alltime should be added to the appropriate language file.

I don't believe you can do that since what you're asking for is using server side code on the client. To do that, the entire stack would need to be available on the client and everything it does. Basically running NodeBB on the client.

What you could do is set up your own socket and return the desired data that way.

In your library.js file:

const pluginSockets = require.main.require('./src/socket.io/plugins');

// This will add to the sockets object used by NodeBB core
pluginSockets.customFunc = ((socket, dataDoToFetch, done) => {
	const response = 'This response is only a string but it can be whatever you want';
	done(null, response);
});

Then client side:

socket.emit('plugins.customFunc', dataDoToFetch, (err, data) => {
	if (err) console.log('My socket customFunc', err, data);
	else console.log('Do stuff with this', data);
});

I cannot guarantee that this will work out of the box since my setup involves a bit more complexity, but this is the basic idea. Give it a shot!

Hi all!
I've run into an issue that when I deploy a new version of my theme/plugin, most users don't get any changes done until they do a hard refresh. This only seems to affect the client side Javascript, so everything looks updated, but in reality functionality gets lost.

Has anyone stumbled upon something similar? Is there a better way to release code?

The background in this is that I have forked Persona and built upon it, so all changes to the platform is basically in the theme. Is there a way to make sure all clients receive all updates?

Thanks!