NodeBB Development

If you have any plugins that use action:topic.save, action:topic.restore or action:topic.edit please read below on the changes coming in 0.6.0. If you have any questions about how to update to the new hooks please feel free to ask. The parameter passed to all three hooks has been changed from a topic id to a topicData object. plugins.fireHook('action:topic.save', topicData); plugins.fireHook('action:topic.restore', topicData); plugins.fireHook('action:topic.edit', topicData); topicData object contains at least the following data. { tid: 3, title: 'test topic', mainPid: 5 }

Is there a way to enable a Moderator with superpower of editing all the sections, ban users, find user for ip address, see user ip, change user's signature, change user's avatar. A sort of Sub-Admin user (or if you prefer a Super-Mod:)

@baris thanks a bunch..!

/facepalm added 1 year ago https://github.com/NodeBB/NodeBB/commit/ba89285c748e0573b0bfeb5ce4c49b29dcd15b17

I'm unsure if I'm seeing a regression or an undocumented? change here. I'm currently getting: TypeError: undefined is not a function at /mnt/Extra/home/dbolack/Projects/nodebb-plugin-rscloudfiles/index.js:203:4 Which maps to: callback(null, { url: rsCloudFilesCDNSecure + '/' + image.name, name: image.name || '' }); Which is equivalent to the current imgur plugins bit: callback(null, { url: data.link.replace('http:', 'https:'), name: image.name || '' }); Any ideas?

After some playing about, i've settled on a redirect. If anyone wants to do something similar, create a new file in sites-available called subdomains, then do the usual sudo ln -s /etc/nginx/sites-available/subdomains /etc/nginx/sites-enabled Inside the subdomains file, create a server block like thus: # Mixes server { listen 80; server_name mixes.35hz.co.uk; rewrite ^ $scheme://35hz.co.uk/tags/mix$request_uri? permanent; } If you want the subdomain to ignore the request parameter, then remove $request_uri? portion of the rewrite. This basically means that if someone typed mixes.35hz.co.uk/parameter it would ignore /parameter and still go to the relevant tag page without causing a 404. This may be more beneficial. So I'd recommend leaving that portion out. However this would be useful if you wanted a fast way to navigate to a user profile via something like user.35hz.co.uk/a_5mith. Because you could add the request_uri after /user in the rewrite. Just add more server blocks as required for each rewrite. You can stack server_names so that multiple subdomains go to the same link, just add another server_name underneath the existing one. server_name mixes.35hz.co.uk; server_name mix.35hz.co.uk;

@baris said: We had no reports of anyone altering socket.uid its a server side only value. A while back there was a certain vulnerability (not NodeBB specific), I don't exactly remember what it was, but it allowed a user to mimic another user, even an admin, and do pretty much everything as that user. Now you have one report

@baris Yep, that's the ticket, cheers buddy. Can be marked as solved.

@julianlam is already working on this, see this topic.

yup. Posting a fix for that when I get a chance: https://github.com/NodeBB/NodeBB/issues/2319

Hi, Is it possible to customise og: tags without editing NodeBB core? Thanks

I don't think we have that documentation right now, couple months ago I started a doc in the github wiki about the db structure but I don't think it got moved over to the docs website. Either way the best way to store your plugin data is to prefix the name of your keys with the plugin id so it doesn't conflict with other plugins. Also you need to be careful to not break any of the core objects, ie if you delete the key users:joindate you will have problems.

@trevor I think they recently implemented that when a user is deleted/banned, that their socket get closed. Or words to that effect. Don't quote me on that though.

@Master-Antonio I still offer free NodeBB hosting right here: https://community.nodebb.org/topic/2291/offering-a-couple-nodebb-instances-for-free/11

@agarcia17 I'm glad I could help you. And I want to say thanks for the solution I'll probably do something along those lines for my forum too

Here sir, take my vote.

Glad you figured it out with @arasbm's help @trevor, sorry I had to go to bed

@a_5mith :poutine:

I think it may be possible. FontAwesome has LESS support, so we could possibly work that into the vanilla theme so it can be easily removed instead of removing it from the header.tpl

Nice, thanks for point me in the right direction!