Please upgrade here. These earlier versions are no longer being updated and have security issues.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
Vanilla 2.0.6 released
Tim
Vanilla Staff
Vanilla 2.0.6 has been released and uploaded.
This is primarily a bugfix release that takes care of some issues reported with v2.0.3.
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).
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.
This is primarily a bugfix release that takes care of some issues reported with v2.0.3.
Changes
- Fixed AJAX issues that broke functionality when RewriteUrls was disabled
- Fixed issue where posting would lag due to slow email server response
- Updated Authenticator support framework
- Cleaned up CSS throughout various areas in the core
- Official release of new Dashboard theme
* Note - this is a re-release of v2.0.4 with a correction to the version number in index.php which was erroneously marked as '2.0.4a'. The version jump is normal.
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 has UserID = 1
- 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
- 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/structure
- Scroll to the bottom of the page and click the button to run the update scripts.
- Navigate to your forum and test away!
Reporting Issues
DO NOT REPORT ISSUES ON THE COMMUNITY FORUMPlease 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.
6
Comments
Vanilla Forums COO [GitHub, Twitter, About.me]
Vanilla Forums COO [GitHub, Twitter, About.me]
Vanilla Forums COO [GitHub, Twitter, About.me]
Vanilla Forums COO [GitHub, Twitter, About.me]
git push origin :tagname
Then recreate it at the new commit.
"Wow, up to 2.0.36 in only 6 months?"
"Yeah, and we only had 12 releases so far!"
//edit: Could just claim it's some esoteric system you've developed. "We only increment in multiples of 3 in accordance with the Gunter Method™."
Then I was like 'fuck it, new version', and tagged 2.0.5. But I hadn't incremented the version number yet again, from 2.0.4 to 2.0.5, so I had a tagged release for 2.0.5 whose internal version was 2.0.4. FUUUUUUUUUUUUUUUUU
So i fixed the internal number at 2.0.6 and re-tagged AGAIN.
Vanilla Forums COO [GitHub, Twitter, About.me]