Gamers

What is your current setup?

Here the post queue is used for all new users. I think the spam-be-gone plugin provides a captcha as well.

Yeah the integrated restart / reload etc only works when you use our loader (./nodebb start etc).

I don't think there is one but you can write a plugin using the hook filter:router.page. This hook gets called before the actual topic route handler.

In your plugin you can just do this:

myPlugin.filterRouterPage = function (req, res, next) {
	const myAnnouncementTopicId = 111;
	if (req.params && req.params.topic_id && parseInt(req.params.topic_id, 10) === myAnnouncementTopicId) {
		req.query.sort = 'newest_to_oldest';
	}
	next();
};

You may be confused: this is the community forum for a Node.js-based forum software called "NodeBB". It is not a general Node.js discussion forum.

Personally I think we should merge About Me, Website, and Location into a single field. I don't see a particular use in separating them. I know the location mapping plugin uses that field, but it could just as well search for a location following ### Location or whatever.

While I'm throwing out ideas, I think it would be nice to be able to pin a particular post on your profile. Then "About Me" could just be the pinned post.

@sweetp said in Formatting is all jacked up when I login to your forum?:

I had the same issue, and fixed it by changing the Skin in my user settings

That worked! Switched it to “Default” and seems to be fixed. Thank you!

When I login using Chrome or Opera, all of the formatting gets jacked up and I can't see anything.

https://github.com/julianlam/nodebb-plugin-session-sharing

@scottalanmiller mind opening an issue detailing your specific problems?

It's funny to me that the biggest performance hit to the main page of my NodeBB instance isn't JS, but images There are a lot of categories with image as an icon there with their number increasing with time and I don't think all images are correctly resized and optimized, so I'll have to start doing it automatically...

So yeah, it's an example of how being JS heavy doesn't make a website slow - it's only bad code that makes a website slow