Please upgrade to 2.1.x here.
The 2.0 branch is no longer being updated.
Important security fix: 2.1.10
, released 4 May.
Vanilla 2.0.17 has been released!
This discussion is related to the Vanilla
This is a feature release which also contains a number of bugfixes for issues in the 2.0.x family. You can read a bit more about these features on the blog
- Statistics! Vanilla now ships with a powerful built-in statistics / analytics tool. We've written an in-depth blog post about this new feature, explaining how it works and what you need to know.
- Homepage! The Homepage feature allows you to change what people see when they land on your site.
- Wordpress Plugins! We have developed a suite of WordPress plugins and widgets to help you better integrate Vanilla Forums with WordPress.
- Revamped Categories! We have completely overhauled the Categories feature to help you better manage your discussions and to provide better support for bigger forums with more Categories.
- Utility/Update! We've added a new way for the forum's database structure to be updated after upgrades. The path '/utility/update' is now accessible to any user and will automatically execute all pending structure changes. The return is always simply 'Success' and no database information is ever exposed. This allows plugins to manually update the structure if needed. This method is throttled and will silently fail if called too often.
Bug Fixes / Changes
- Fixed bug where plugins and themes could fail to enable due to extra whitespace.
- Fixed bug where search results were not properly sorted by date after relevance.
- Fixed bug where links in profile status cause the profile to clear when clicked.
- Fixed bug where signing in from the comment form button would not refresh the page.
- Fixed bug where administrators could not change user's picture without 404 errors.
- Fixed bug where stack trace would display when testing plugins, even if not in DEBUG mode.
- Fixed bug where editing a role was erroneously selecting the default permission in the UI when editing.
- Fixed bug where discussion autorefresh would sometimes disable itself.
- Fixed bug where when markdown is enabled urls would not get auto-converted to clickable links.
- Fixed bugs in OpenID and GoogleSignIn where redirect targets were not getting sent to the signin.
- Fixed bug where mobile theme would sometimes display incorrect "last comment date".
- Optimized Announced Discussions query to improve performance.
- 184.108.40.206 - Fixed bug where analytics hooked before Garden.Installed=true, causing a fatal error on install
- 220.127.116.11 - Fixed bug where analytics registration would occur repeatedly if config file was read-only
- 18.104.22.168 - Repackaged distribution without OS-Specific meta data, and fixed ajax information exposure bug
- 22.214.171.124 - Fixed problem with dashboard structure file where Activity and Profile permissions were not granted automatically on fresh install
- 126.96.36.199 - Fixed problem with category permissions where some configurations would result in too restrictive defaults
- 188.8.131.52 - [SECURITY] Fixed potential querystring XSS and cookie HMAC Timing vulnerabilities in core
- 184.108.40.206 - Updated analytics client and server software to fix a bug in stats transmission and rendering
- 220.127.116.11 - Fixed a packaging problem that caused the contents of index.php to be duplicated
- 18.104.22.168 - [SECURITY] Fixed cookie theft vulnerability.
- 22.214.171.124 - [SECURITY] Fixed Facebook, Twitter, and Embed plugins' access control.
Keeping track of new releases
You can follow our releases by pointing your favorite RSS reader at:
This feed will automatically update whenever we release a new version of Vanilla Core.
Troubleshooting the Vanilla 2 Installation
If you run into any issues during the installation, you may see the "Bonk" error screen. In order to get past this screen, you can remove the following line from your conf/config.php file:
$Configuration['Garden']['Errors']['MasterView'] = 'error.master.php';
This will show you a more detailed screen of information about the actual problem you've encountered. Please include this information when reporting issues (copy & paste exact errors, please).
Upgrading Vanilla 2.0 Forums
- Sign into your existing forum with the user that was created when you FIRST INSTALLED Vanilla (the root admin user)
- Back up your database.
- Back up all of your existing files.
- Unarchive the new files and copy them over your existing files. Make sure that your hidden files (ie .htaccess) are copied to your server.
- Make sure the conf/config.php from your old version has been copied over to the new version.
- Delete all *.ini files in your cache/ folder
- CHANGED STEP! Navigate to the page in your forum that updates your database (this will not work if you did not sign in as UserID = 1): www.yourforum.com/utility/update (or www.yourforum.com?p=/utility/structure)
- Navigate to your forum and test away!
For more help with upgrading, check out the Upgrade Documentation
and the Upgrading Tips and Tricks
DO NOT REPORT ISSUES ON THE COMMUNITY FORUM
Please report all issues on the GitHub Issue Tracker
. Remember to do a quick search through the issues to make sure your issue has not already been added or resolved.
See the add on page for additional instructions.
53 · ·