More changes in Vanilla 2.8 (coming Feb 6) [update: delayed]
I previously announced SSO changes coming in 2.8.
What else is new?
Our new Rich Editor will be the new default for new forum installations. You can manually enable it under Plugins after upgrading. I've now enabled it on this forum for a test drive! It brings automatic link previews, improved content embedding, better accessibility, better shortcut key support, and a more intuitive interface (inline menus instead of a menu bar). It includes full native emoji support and drag-and-drop image uploading.
Our new Keystone theme, based on the new Boilerplate theming system, will be the new default for new forum installations. It will be available under Themes for all forums after upgrading. We'll be swapping our existing theme on this site for it not long after release. It brings native responsiveness to Vanilla for the first time. No more separate mobile theme is needed! It works on all devices at all sizes. We've been experimenting with this for a couple years on our cloud service, and it's time to bring the refined results to everyone.
We're also making a number of security improvements for the 2.8 release. I'll be honest: We got a bit overwhelmed by the response to our HackerOne campaign in 2018, so we have a backlog of mid-level issues we want to get out. High-level reports have been released for 2.6 already, but less urgent improvements will only be available in 2.8. We'd love to be able to backport every single report, but it simply requires a higher level of resources than we have today. So, an important upgrade from a security perspective too.
Under the hood, we continue to make improvements to our code for better performance and setting up future features. We continue to prioritize the transition from framework-based integrations to API-based integrations, and we've started deprecating a large number of "helper" functions that were really just slowing down the product. Addon developers will especially notice the deprecation of the
val() functions, among many others. We're not going to break compatibility by removing them for quite some time, but please be on notice to start removing them as you work on code. If you need help with suggestions, start a discussion and we'll be happy to answer.
There should be very few compatibility breaks in this release. What that means is whatever breaks we created we hope are very rare edge cases that few developers if any would notice. If you note an addon you created breaks in the upgrade to 2.8 (which we strongly recommend testing not on your live sites), feel free to request assistance making needed changes by posting relevant errors and information on this forum.
Feel free to post general questions here, but ALWAYS start a new discussion for assistance troubleshooting technical issues.