Blog Documentation Book a Demo
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.15 Released

TimTim Vanilla Staff
edited November 2010 in Vanilla 2.0 - 2.8
Vanilla 2.0.15 has been released!
This is primarily a bugfix release for issues in 2.0.14.

v2.0.15 Changes

  1. Fixed bug where dismissed announcements would disappear forever
  2. Fixed bugs with Vanilla API
  3. Fixed bug with Gdn_Cache throwing a fatal error for keys that didn't exist
  4. Fixed bug with Permissions where PermissionModel::Save() wouldn't always update the user's permissions
  5. Fixed bugs with Twitter auth for rewrite urls
  6. Fixed several other low priority bugs

Keeping track of new releases

You can follow our releases by pointing your favorite RSS reader at:
http://www.vanillaforums.org/addon/vanilla-core/follow.rss
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

  1. Sign into your existing forum with the user that was created when you FIRST INSTALLED Vanilla (the root admin user)
  2. Back up your database.
  3. Back up all of your existing files.
  4. Unarchive the new files and copy them over your existing files. Make sure that your hidden files (ie .htaccess) are copied to your server.
  5. Make sure the conf/config.php from your old version has been copied over to the new version.
  6. Delete all *.ini files in your cache/ folder
  7. 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
  8. Scroll to the bottom of the page and click the button to run the update scripts.
  9. Navigate to your forum and test away!
For more help with upgrading, check out the Upgrading Tips and Tricks thread.

Reporting Issues

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.

Vanilla Forums COO [GitHub, Twitter, About.me]

Tagged:

Comments

  • LincLinc Admin
    http://www.youtube.com/watch?v=JwZwkk7q25I
  • SubJunkSubJunk ✭✭
    Thanks, it's a good release
  • keeshakeesha ✭
    an auto update function à la "wordpress" would be nice, 7 steps (without backups) to update a forum is kinda ugh in these easy peasy plug'n'play days.


    other than that, thanks for the update. :)
  • TimTim Vanilla Staff
    an auto update function à la "wordpress" would be nice, 7 steps (without backups) to update a forum is kinda ugh in these easy peasy plug'n'play days.


    other than that, thanks for the update. :)
    Its coming in 2.1. Probably the next update we do will contain an updater. With backups.

    Vanilla Forums COO [GitHub, Twitter, About.me]

  • cdavidcdavid New
    and when is 2.1 scheduled for release? an estimate would be great :)

    /cd
  • LincLinc Admin
    @cdavid Next. :D
  • keeshakeesha ✭
    Cool Tim, thanks for the info :-)

    @Lincoln could you specify "next" please? :-)
  • RajioRajio ✭
    @Lincoln hopefully nobody posts that "the system is down"!
  • candymancandyman ✭✭
    I never imagined that Vanilla would be improved so much in so little time. Congratulations for all the work done so far.
  • abrownabrown New
    edited November 2010
    4. Unarchive the new files and copy them over your existing files. Make sure that your hidden files (ie .htaccess) are copied to your server.
    *Will just dumping files in copy over hidden files?

    5. Make sure the conf/config.php from your old version has been copied over to the new version.
    *Okay if this is the case why is this step mentioned after step 4.

    6. Delete all *.ini files in your cache/ folder
    *The new *.ini files or the old .ini files. Is this step also out of order?

    Would someone please rewrite these instructions but assuming I'm a noob. They are seriously not sufficiently helpful. Also, please specify what folder(s) contain the files in question. Finally, were I to follow your steps explicitly wouldn't I lose some of my non-default plugins?
  • SriSri
    Vanilla is great. Thanks Tim & the team!

    PS: Are you guys looking for developers / contributors?
  • TerminalAddictTerminalAddict New
    upgrade went well .. no issues
  • TimTim Vanilla Staff
    4. Unarchive the new files and copy them over your existing files. Make sure that your hidden files (ie .htaccess) are copied to your server.
    *Will just dumping files in copy over hidden files?
    This is primarily a concern for people who are uploading via FTP. Some stupid FTP clients, in an attempt to hand-hold their users, neglect to copy files with the 'dot prefix' -- for example, .htaccess. If you're using FTP, make sure this doesn't happen.
    5. Make sure the conf/config.php from your old version has been copied over to the new version.
    *Okay if this is the case why is this step mentioned after step 4.
    After copying all the files in the new (freshly downloaded) archive over to your existing installation, copy your old CONFIG FILE back on top of THAT, thereby retaining your settings. Where else would this step go? :p
    6. Delete all *.ini files in your cache/ folder
    *The new *.ini files or the old .ini files. Is this step also out of order?
    The downloaded archive should not contain any INI files, so... delete them *all* just as it says.
    Would someone please rewrite these instructions but assuming I'm a noob. They are seriously not sufficiently helpful. Also, please specify what folder(s) contain the files in question. Finally, were I to follow your steps explicitly wouldn't I lose some of my non-default plugins?
    You need to pay closer attention to the instructions. Or perhaps you're overthinking things a *lot*.

    > Also, please specify what folder(s) contain the files in question. Finally, were I to follow your steps explicitly wouldn't I lose some of my non-default plugins?
    I'm not sure what you mean by this. If you've gotten Vanilla running already, it should be in a folder somewhere on your webserver. For example's sake lets say this folder is called "vanilla/". Then you download an updated version in the form of a zip file. This zip file is analogous to the install folder in that it contains all the files for a vanilla installation. We want you to COPY the contents of this downloaded "folder" (really a zip file) ON TOP of your existing vanilla/ installation. The nature of the COPY operation in pretty much every operating system allows this to result in replacing any files that exist in both locations, adding any files that exist only in the new archive and LEAVING UNTOUCHED any files that do not exist in the new archive (such as your non-default plugins).


    Vanilla Forums COO [GitHub, Twitter, About.me]

  • TimTim Vanilla Staff
    Todd is allegedly wicked

    Vanilla Forums COO [GitHub, Twitter, About.me]

  • ddumontddumont ✭✭
    edited December 2010
    @Tim After update to new version, I can no longer click on my profile (upper right) link in the header. It says permission denied to view my profile page.

    There was an error rendering this rich post.

  • TimTim Vanilla Staff
    Do you have access to your SQL server directly? Or maybe via PHPMyAdmin?

    Vanilla Forums COO [GitHub, Twitter, About.me]

  • ddumontddumont ✭✭
    @Tim phpmyadmin

    There was an error rendering this rich post.

  • TimTim Vanilla Staff
    We'll be releasing 2.0.16 tomorrow which will be a patch for this specific bug. Sorry about the trouble :/

    Vanilla Forums COO [GitHub, Twitter, About.me]

Sign In or Register to comment.