NodeBB Development

I figured you could do this the same as this category.description = validator.escape(category.description); When I comment this out, it allows the parsing of HTML in category descriptions. I would like to do this because if you have plugins such as the YouTube Lite, or a bunch of images, it shows all of that when you have mainPost.content implemented in your template. Looks messy.

I know I made a promise to have the 0.5.x branch last more than 2 releases, but we added more breaking changes again, and 0.5.0 hasn't even been released yet In any case, for those plugin developers who are interested: Notification pushed action hook (action:notification.pushed) incoming data has changed: From: An object containing the notification data To: This object -- {notification: notification, uids: uids}); As always, this list will be updated as new breaking changes are added. In the case of this list -- don't commit and publish your change to npm yet, as 0.6.0 has not launched. We recommend you maintain these changes in a separate branch until then.

@Ted yeah, and also the way I'm using the chat is not necessarily for casual conversations; statistics/logs from chat are needed

You'd probably have to write an SSO plugin to share authentication. @julian has a ton of SSO plugins that you could use as a sample in writing your own one https://github.com/julianlam?tab=repositories As far as user management... somebody was asking for a WP user management plugin. Kind of like if you upgrade a user's privileges in WP, it updates it in NodeBB as well. It's doable but the client didn't end up going for it so we never ended up building it

@Joseph-Mordica What features of pm2 do you use? If it's just to allow for horizontal scaling by having NodeBB instances use up all cores, then it's possible that we will bake that into our loader executable in future releases of NodeBB...

Sounds like great news, looking forward to seeing NodeBB bloom using it

Thanks I'll give it a shot!

Totally, the more the merrier In the end we're just a community helping each other build something cool and free to use

@baris thanks! I don't like to brag but I kinda figured this out 16h ago I was checking uid==0 and skipping that out from deletion, but kept getting deleted. My admin uid kept incrementing for every node app --setup, so I looked at the schema again. but thanks your helper methods were extremely helpful.

In my topic.tpl I made some changes using @first to separate first post in topic from others. It worked, but there is now next problem. When i create a new post it doesn't show it instantly, I have to refresh page to see that post. This is how my topic.tpl looks now http://pastebin.com/jYNQ1WVr Also, I noticed this http://screencast.com/t/jESEIi9GiY . Instead of just creating one more <li> in .otherPosts div it creates another .firstPost and .otherPosts div. I think that maybe I made some mistake with using @fist but I can't figure out what is it. Someone help?

@a_5mith @psychobunny Thank you both. So the error is removed and cache is cleared, so now it works like it should. ^^

This is coming in 0.5.1. Previously this hook was passed a topic id and an array of posts. It was assumed that all the posts are from the same topic but this is no longer the case. So the topic id is removed. If you are using this hook you can get a list of the topic ids from the posts array. See this commit for the change. In your plugin you can just retrieve the tids if you need them from the posts array like so function (data, callback) { var tids = data.posts.map(function(post){ return post.tid; }); ... }

Yes, the polling 200 status indicates nothing is wrong. Everything you're seeing is completely normal of nodes Socket.IO. Furthermore, polls are done on port 80 http, so it would never be blocked. Webscoket traffic in general is done ona range of ports, none of which ISP's filter (I've worked for an ISP). The only port I know that SOME NorthAmerican ISP's block is SMPT incoming and even that is rare.

@trevor @esiao Yes, I need that for user's profile page, but tnx anyway The thing is that I don't know how to make plugins, because I am focused on design for now. Is anyone else interested to help with this? @psychobunny @julian or any other developer?

How to add more widget locations on home.tpl? I want add widget at the footer / header of home.tpl Not global footer.

@esiao That didn't worked, it looks like it doesn't even loads masonry.js for some reason. How can I see is the scirpt loaded and is it loaded correctly? Maybe some cmd command? I followed all instructions in setting up plugin.json and theme.json and I am pretty sure that I did it right. I can't figure out what can be the problem. Any other suggestions? Tnx anyway ^^

@Jelena You're welcome, didn't look in the plugin file. glad you've got it working,

Related issue: https://github.com/NodeBB/NodeBB/issues/1978 This is another breaking change. It effects anyone using the hook filter:user.custom_fields and filter:register.build to add custom data to users on registration. If you were using filter:user.custom_fields to add new entries into the user object you can just switch the hook you are using to filter:user.create. No need to change anything else. If you are using filter:register.build to add new entries into the registration form and want these entries to get added into the user object you need to use the hook filter:user.custom_fields. In your plugin that adds new entries into the registration form just add a listener for filter:user.custom_fields and add the fields that you added to the form into the array passed in, here is a sample. // plugin.json { ... "hooks": [ { "hook": "filter:user.custom_fields", "method": "addCustomFields"} ], ... } //plugin code function addCustomFields(fields, callback) { fields.push('newCustomField1'); // must match the input name you added to regForm fields.push('otherCustomField1'); callback(null, fields); } After this when a new user registers they will have newCustomField1 and otherCustomField1 entries in their user object. @bentael nothing needs to be done for spam-be-gone since we don't want the captcha form entries in the database anyways. Before this change it was possible to add any field into the registration form client side and it was inserted into the database. Now only the fields that core and plugins specify are inserted.

@esiao it works，Thank you very much!