0.9.0 Breaking Changes

<baris>

Hook changes

Filter

action:email.send and filter:email.send renamed see this commit
filter:user.settings has been renamed to filter:user.customSettings see this commit

Other changes

src/postTools.js and src/threadTools.js removed. They are under posts.tools and topics.tools
privileges.topics.canEdit and privileges.topics.canMove removed
User.exists no longer takes a userslug, it's parameter is uid now. New method User.existsBySlug takes in a userslug. See this commit.
notifyOnlineUsers , sendNotificationToPostOwner , sendNotificationToTopicOwner and emitToTopicAndCategory moved see this commit.
posts.getPidIndex signature changed see this commit
posts.flagPost signature changed see this commit
Template changes for topic view. commit1, commit2, commit3
User Icons introduced (see: https://community.nodebb.org/topic/6583/0-9-0-breaking-changes/12)

lulzdev

Ahhh, the humanity!

<baris>

Updated with user.exists change

https://github.com/NodeBB/NodeBB/commit/b616e69070afccc3137827ba1d7ca20e8dcbd2dc

<baris>

Username/email and password change moved to their own pages, this requires custom themes to be updated.

Relevant issue https://github.com/NodeBB/NodeBB/issues/1637 and changes on persona https://github.com/NodeBB/nodebb-theme-persona/commit/db5dd6c5a03ec67df1388803297dce0d01d1e717

PitaJ

A better wording for

action:email.send and filter:email.send renamed

Would be

action:email.send renamed to filter:email.send

Or it at least appears that way from the commit changes

<baris>

Yes that's correct action:email.send became filter:email.send and there is a filter:email.modify hook to change the data.

<baris>

posts.flagPost signature changed.

Messages on flags · Issue #3107 · NodeBB/NodeBB

I would like to see on the future the option to include a message when you submit a flag form a post so the moderator can see the problem easy

GitHub (github.com)

<baris>

This ones a small change effecting custom themes.

description class and time change · NodeBB/nodebb-theme-persona@e351430

Persona - A modern and responsive NodeBB theme. Contribute to NodeBB/nodebb-theme-persona development by creating an account on GitHub.

GitHub (github.com)

relativeTime changed to timestamp

<baris>

If you have a custom theme make sure you apply these changes.

https://github.com/NodeBB/nodebb-theme-persona/commit/0b015a85d78450e1d9b0a82469d2e835b4c31dad
https://github.com/NodeBB/nodebb-theme-persona/commit/b545b00c9d652cea6a7c0df843603ba3b4a6b809
https://github.com/NodeBB/nodebb-theme-persona/commit/2739c08a14a688f8473123ca47d18965ff5767ca

We moved the dropdown menus into partials and only parse them when the user opens the relevant menu ie posttools or thread tools. This reduces the amount of parsing done in topic view.

trevor

So replace everything that has relativeTime with timestamp ?
Or only in certain places...

<baris>

@trevor Just in templates/partials/categories/lastpost.tpl

julian

What's this User Icons business?

In short, NodeBB used to use Gravatar to generate default icons for guests and users. However, while this approach was novel in terms of forums, there were some concerns over extensibility and user privacy, and so we set out to revamp the system to remove our dependency on Gravatar.

How does this affect me, as a forum owner?

It shouldn't. Next time you upgrade...

~~All of your users currently using gravatar will remain using gravatar.~~ See below
Any new users will have a user icon generated
If you had a custom default avatar set, the default should still be properly set.

How does this affect me, as a plugin or theme developer?

You'll need to update your themes and plugins and change every invocation of the user avatar to include a conditional.

For example, investigate this diff:

-	<img src="{groups.members.picture}" />
+	<!-- IF groups.members.picture -->
+	<img src="{groups.members.picture}" />
+	<!-- ELSE -->
+	<div class="user-icon" style="background-color: {groups.members.icon:bgColor};">{groups.members.icon:text}</div>
+	<!-- ENDIF groups.members.picture -->

Instead of an single image tag, there is now a conditional ().
The div contains the user icon in lieu of a picture.
The user-icon class is required

Adjust as needed for your own plugin.

psychobunny

All of your users currently using gravatar will remain using gravatar.

This statement won't be true for 0.9 - if you wish to keep gravatar support do not upgrade until we build the equivalent gravatar plugin that will allow you to continue as normal. We will highlight this in the release notes / blog post in case you miss it here.

julian

Updated my post, thanks.