action:email.send and filter:email.send renamed see this commitfilter:user.settings has been renamed to filter:user.customSettings see this commitsrc/postTools.js and src/threadTools.js removed. They are under posts.tools and topics.toolsprivileges.topics.canEdit and privileges.topics.canMove removedUser.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 commitposts.flagPost signature changed see this commit
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
A better wording for
action:email.sendandfilter:email.sendrenamed
Would be
action:email.sendrenamed tofilter:email.send
Or it at least appears that way from the commit changes
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.
So replace everything that has relativeTime with timestamp ?
Or only in certain places...
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.
It shouldn't. Next time you upgrade...
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 -->
<!-- IF picture -->).div contains the user icon in lieu of a picture.user-icon class is requiredAdjust as needed for your own plugin.
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.
