New features in 2.3.0.beta4
ignored_users when merging two users
This is part of the Ability to ignore a user feature.
When we merge two users, we need to account for merging their list of
Header based auth for API requests
Now you can also make authenticated API requests by passing the
api_username in the HTTP header instead of query params.
The new header values are:
Here is an example in cURL:
curl -i -sS -X POST "http://127.0.0.1:3000/categories" \ -H "Content-Type: multipart/form-data;" \ -H "Api-Key: $API_KEY" \ -H "Api-Username: system" \ -F "name=7c1c0ed93583cba7124b745d1bd56b32" \ -F "color=49d9e9" \ -F "text_color=f0fcfd"
Allow users to easily track/watch/mute topics via email
If you reply to an email with the word “mute” a topic will be muted
If you reply to an email with the word “track” a topic will be tracked
If you reply to an email with the word “watch” a topic will be watched
These ninja command can help advanced mailing list ex-users, saves a trip
to the website
There is also support for
instead of specifying the username along with the key.
Special call-out for new / returning posters.
A banner message appears when a new or a user who hasn’t posted in 2 months posts to encourage those users to continue to post.
2.3.0.beta4 and UX fixes
This release also includes a number of small bug and UX fixes from our 2.3.0.beta3 release. Sites on the beta and tests-passed branches are encouraged to update to resolve these issues, including:
- Missing translations when “en” set as fallbackLocale
- Do not display add/remove participants if you can’t actually do it
- Sanitize theme settings properly before injecting into stylesheets
- Bugs in safari where select-kit is not expanding on iOS
- Fix post notice on mobile
- Text content search warning if more than 50 results