Posts made by baris

This could be relevant https://github.com/lovell/sharp/issues/1428

sorvani created this issue in lovell/sharp

closed CentOS 7: Node 10.12.0 requiring zlib 1.2.9 #1428

Hi @snahedis take a look at https://community.nodebb.org/post/74689

The cache stays as long as it is not full and it is not invalidated. Sounds like you need to setup pubsub so changes you make on one server are propagated to the others.

No built in way to do this right now, although I think it would be useful as a core option in the group settings, like Disable join requests. Can you open an issue on our tracker?

If you don't want to wait till it's implemented on hacky way to do it is to use the hook 'action:group.leave' and add the user back to the groups they just left.

app.use(session({
		store: db.sessionStore,
		secret: nconf.get('secret'),
		key: nconf.get('sessionKey'),
		cookie: setupCookie(),
		resave: nconf.get('sessionResave') || false,
		saveUninitialized: nconf.get('sessionSaveUninitialized') || false,
	}));

The default is already off, you can put sessionSaveUninitialized: false in your config.json to make sure.

It's already fixed on latest master.

Thanks for reporting, I will fix it.

Updated link to me more family friendly

Translations are handled here https://www.transifex.com/nodebb/nodebb/, anyone can contribute.

The language string is probably not translated to all languages yet.

@alfazaz said in Proper way to render error page (404...):

app.get('/uploads/myfiles/:file(*?)', function (req, res) {
// Things TODO with req.params.file for permissions (after work on it)...
var longfilename = path.resolve('public' + req.url);
if (fs.existsSync(longfilename)) {
res.status(200);
res.sendFile(longfilename);
} else {
console.log('Fichier non trouvé');
res.status(404);
res.render('404', {path: req.path});
}
});

The proper way is to call next and let the core 404 handler do it's magic.

app.get('/uploads/myfiles/:file(*?)', function (req, res, next) {
		// Things TODO with req.params.file for permissions (after work on it)...
		var longfilename = path.resolve('public' + req.url);
		if (fs.existsSync(longfilename)) {
			res.status(200);
			res.sendFile(longfilename);
		} else {
 			next();
		}
	});

NodeBB probably treats that url like a normal page since it doesn't start with /uploads or /assets/uploads and it tries to ajaxify to that page. https://github.com/NodeBB/NodeBB/blob/master/public/src/ajaxify.js#L395

You also have to be careful with allowing access to the filesystem and make sure users can only download from the myfiles folder. Ie if someone manages to pass in req.params.file = ../nodebb/config.json they might download your config.json file.

Are you getting any errors in the browser console or ACP?

Please see https://community.nodebb.org/topic/11510/boxes-on-the-side

You need to modify this file or overwrite it in a plugin. So it looks like this

<div class="row forum-stats">
	<div class="row">
		<div class="col-md-3">
			<div class="stats-card {statsClass}">
				<h2><span class="stats" title="{online}">{online}</span><br /><small>[[global:online]]</small></h2>
			</div>
		</div>
		<div class="col-md-3">
			<div class="stats-card {statsClass}">
				<h2><span class="stats" title="{users}">{users}</span><br /><small>[[global:users]]</small></h2>
			</div>
		</div>
		<div class="col-md-3">
			<div class="stats-card {statsClass}">
				<h2><span class="stats" title="{topics}">{topics}</span><br /><small>[[global:topics]]</small></h2>
			</div>
		</div>
		<div class="col-md-3">
			<div class="stats-card {statsClass}">
				<h2><span class="stats" title="{posts}">{posts}</span><br /><small>[[global:posts]]</small></h2>
			</div>
		</div>
	</div>
</div>

'cid:' + parentCid + ':children' is cached so that's why the changes aren't reflected realtime. You need to clear the cache after adding to that sorted set with

const cache = require.main.require('./src/cache');
cache.del('cid:' + parentCid+ ':children');

Do you have nodebb-plugin-markdown enabled on the forum?

This should fix your issue.

Clicking on the topic title should work. Needs better UX though since other tools work by clicking the user avatar.

Try with nodejs 8/10/12