my users keep asking me about the above features. "Mark all read" seems to have disappeared entirely, whereas quoting has become quite cumbersome and inconvenient, especially when threads with arguments on religious and political issues grow exponentially in size with every new post.
I'm aware of the workaround.
Now for a post with short to medium length that works okay. But a long post, to which three or four people have already contributed, building the above structure becomes a bit complicated, whereas before it was possible to just quote the entire post, just write in between the lines, and the quotes wold be attributed the the appropriate user automatically.
>> @user1 said:
>> quote 1
> @user2 said:
> quote 2
user3's response goes here
Bottom line: inline quotes are a feature greatly missed in the otherwise quite awesome new editor
This is a very big release! You can read more about this release in our pre-announcement.
Instructions to install, upgrade, and troubleshoot Vanilla are linked in the README file included in the download.
For help troubleshooting, start a new discussion and include what steps you have already taken from our troubleshooting list.
This is the FINAL release that will support PHP 7.0. It is our policy to drop support for PHP versions that have ended security support (PHP 7.0 support ended in December), and thus our next version will require PHP 7.1. (Note that the current PHP version is now 7.3 and we strongly recommend upgrading to it.)
Support for Vanilla 2.6.x has now ended.
There are a number of addons with important security updates. Please audit your addons against this list:
In 2018, we also deleted the Whispers and Customize Text addons. We strongly suggest removing them from your site if either is still there. The last known versions had security issues.
We removed these addons from the directory because they are now available within Vanilla 2.8:
You can manually retrieve addons we have sunset from core from our GitHub repo until they are deleted later this year:
These addons are now open source for the first time:
These addons were recently deleted from the directory due to lack of use:
These addons are likely to be removed in the near future:
These addons have been added to the directory, but were already open source:
More addons are being updated as well, but have no current security patches or status changes to announce.
As many of of you might have noted, the 2.8 release is around the corner. https://open.vanillaforums.com/discussion/36959/more-changes-in-vanilla-2-8-coming-feb-6#latest
There are a few things I'd like to note for addon developers in this release.
We've added quite a few new subsystems that are not fully ready for public consumption. I'm trying to mark them with the
@internal annotation, but I may not get all of them. With that in mind:
Don't use new undocumented classes, especially ones with the
@internal annotation, unless you are ready and prepared to update them in the next release. We are actively iterating on these new parts of the framework, and some may have their public APIs, and classnames adjusted in the next release.
A few examples of of classes or namespaces like this.
When these new pieces are completed we will document them publicly, deprecate old alternatives, and provide a clear path forward. Thank you for your understanding.
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.