Release Highlights, as of February 16, 2017
We have also delivered a workaround for one of the most hated bugs in the new platform.
On top of that, we released new notification features and search improvements.
So without further ado, let’s take a look at the current STAUS UPDATE for features and fixes…
- An interim solution for the biggest, baddest bug is in place. When members spent many minutes writing an answer, they would receive an error message (shown below) when attempting to post — and they would lose their work. This bug has been reported in several places throughout the community, such as in this discussion and in this one (and perhaps most monkey-fightingly in this Monday-to-Friday Coffee Corner conversation). While a permanent solution is a few months away (as it’s based upon a major upgrade coming from the vendor that provides the core product), this current fix should mitigate the problem for now.
- The last release introduced a new option that allows you to choose the tags you follow as the primary and additional tags when creating a question. This functionality has been expanded to include an option for selecting your favorite tags — meaning the tags that you use frequently — as well.
- The option that allows you to choose your followed and favorite tags as the primary and additional tags isn’t just available for questions. With this release, you can also choose the tags you follow or use most when preparing a blog post.
- Another previously released feature for questions is also available now for blogs. Specifically, you can filter blog posts by the tags that you follow — just as you can with questions.
- A new notification type has been added. You will now receive notifications when any of your answers get accepted.
- The notification counter previously displayed the number of unread notifications in your notifications inbox. With this release, this counter now shows how many new notifications you have received since you last accessed this inbox. Accessing the inbox will clear the number from the counter. We realize that this new functionality leaves a gap, as users now can’t see the number of their unread notifications. To tackle this problem, we are working to implement a message in your inbox that also shows the number of unread notifications.
- Based on discussions criticizing our site search, we adjusted the fuzziness level to improve the number of results. Other new search enhancements include crawler optimizations and better auto-completion when entering search terms.
- Some members (primarily Firefox users) were reporting that they were receiving error messages when attempting to add comments to a blog post. This bug has been resolved.
As always, please continue to report bugs and share feedback, as your input helps us prioritize features and fixes. We particularly interested in hearing your opinions about features that, if made available, would help us recapture the sense of community that members miss most. We are especially interested in hearing about your top 2 things that most important to you (such as a missing feature you think is needed). Again, this type of feedback helps us prioritize.