It looks like you're new here. If you want to get involved, click one of these buttons!
It is with great pleasure and pride that I announce the immediately availability of the Vanilla 2.1 stable release. Vanilla 2.1 represents a huge leap forward for our open source product.
If you are on our cloud platform, please note you already have all the enhancements in 2.1 (and have for quite a while) so you don't need to do anything - this announcement does not apply to you.
I want to thank our community members here for their unwavering support over the last several years. The issues filed, pull requests sent, and questions answered are invaluable and we truly appreciate it. The last year has definitely seen an increase in community participation in the product and that's very exciting.
To upgrade from 2.0.18 (any patch level)
default.master.tplwhich should also be in that folder)
$Configuration['Vanilla']['Views']['Denormalize'] = TRUE;from
/conf/config.phpif it is present, unless you are knowingly running memcached and have configured it. If that value is not in your config, you have nothing to do and may continue.
/index.php?p=/utility/updateto update the database. It may take a while. If it fails, run it again. It picks up where it left off if it doesn't complete due to a timeout.
These are some generic tips for addressing problems during an upgrade.
$Configuration['Debug'] = TRUE; in your
conf/config.php to reveal full error messages. Remember to remove it when you are done.
Clear your browser cache and cookies, then restart your browser.
conf/config.phpby setting the
conf/config.phpbut do not remove HTMLawed's line.
/utility/updateagain (see upgrade instructions).
/role/defaultrolesand confirm your default roles are set correctly.
Too much to list effectively. The 2.0 branch had 4,615 code commits. The 2.1 branch now sits at 8,639. That means we made nearly as many changes from 2.0.18 to 2.1 as we made cumulatively from the first 2.0 alpha build thru the 16 rapid 2.0-branch stable releases over three years. I cannot hope to distill down a list of 4000 changes into a comprehensive summary, especially given the amount of time elapsed. So the short answer to "Did X change at all?" is "yes". There's no such thing as a selective upgrade this time around.
Here's a broad overview of what we did:
2.1 is the revision that got away from us, and so this upgrade will be a little more painful than past ones. We've learned from the pain of getting this release out the door and have revised our strategies accordingly.
Test all plugins you're using before upgrading.
Any core hacks in 2.0 should be ditched (and, ideally, not recreated).
Those plugins will all be disappearing in the next version. We recommend deleting them from your server entirely.
We're going to let 2.1 percolate for a few months and release the inevitable patches as it reaches more and more folks. That should keep everyone busy thru the summer. Patches will use the third decimal (2.1.1, then 2.1.2, etc). We've abandoned using a fourth decimal for releases.
Our next major open source release will be 2.3 (we've changed our versioning scheme; see the new README) and we expect to begin that beta cycle by the end of the year. We're already more than a thousand commits beyond 2.1.
We will continue to support 2.0 with security patches thru the end of 2014. After that we shall bid it an overdue farewell.