Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In with Facebook Sign In with Google Sign In with OpenID Sign In with Twitter
Sign In Apply for Membership

Categories

In this Discussion

Who's Online 13

GumCloudSafemanShadowdareericgilletteevdlucmattsandinosmwln +4 guests

Vanilla 2.0.6 released

TimTim
in Questions
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.

Changes

  1. Fixed AJAX issues that broke functionality when RewriteUrls was disabled
  2. Fixed issue where posting would lag due to slow email server response
  3. Updated Authenticator support framework
  4. Cleaned up CSS throughout various areas in the core
  5. 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

  1. Sign into your existing forum with the user that has UserID = 1
  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!

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 Senior Developer [GitHub, Twitter, About.me]

Tagged:
«1

Comments

  • Tomtom100Tomtom100
    Posts: 34
    BUG! By MiguelTarga
  • binhdobinhdo
    Posts: 64
    BUG!
  • LincolnLincoln
    Posts: 2,058
    image

    Vanilla developer [GitHub, Twitter]

  • MikhaelMikhael
    Posts: 93
    Copied over 2.0.3 and updated; all's fine so far. Thanks for all the hard work guys. @Lincoln; WTH?! :)
  • binhdobinhdo
    Posts: 64
    The version is defined at the beginning of 'index.php' in the root directory. It still reads '2.0.4a'.
  • TimTim
    Posts: 1,573
    @binhdo This has been fixed. I uploaded a new version just now. Sorry about that. So many little things to check and synchronize >.<

    Vanilla Forums Senior Developer [GitHub, Twitter, About.me]

  • binhdobinhdo
    Posts: 64
    Whatever happened to v2.0.5 ...
  • LincolnLincoln
    Posts: 2,058
    No one appreciates a good lightswitch rave anymore.

    Vanilla developer [GitHub, Twitter]

  • TimTim
    Posts: 1,573
    I'm bad at tagging with GitHub because it is stupid, and I screwed up :( It doesn't let you re-use old tags and point them at new commits, so I had to skip. Same thing happened with 2.0.2 :p

    Vanilla Forums Senior Developer [GitHub, Twitter, About.me]

  • TimTim
    Posts: 1,573
    @Lincoln dooodlodoooodo doodleoodoooodo doodleoodoooodo...

    Vanilla Forums Senior Developer [GitHub, Twitter, About.me]

  • daBradodaBrado
    Posts: 13
    I'm not sure of this is an 'issue' or I'm just not understanding something, but after upgrading from 2.0.3 as described above, my copied config.php still shows the versions of Conversations, Vanilla, and Garden as 2.0.3. Do I need to manually change these to 2.0.6? Are these values important?
  • binhdobinhdo
    Posts: 64
    Now we are getting somewhere...
  • TimTim
    Posts: 1,573
    @daBrado that value is something we've added and plan to use in the future. The real (current) version number is stored in index.php and we update that for you.

    Vanilla Forums Senior Developer [GitHub, Twitter, About.me]

  • MikhaelMikhael
    Posts: 93
    2.0.6? Nooooooo!! I just spent ages updating stuff and this happens. Sad face. :( I have another thought, but will make a new post.
  • MikhaelMikhael
    Posts: 93
    @Tim; Bottom-right corner of the Dashboard screen still says 2.0.4a after updating to 2.0.6 (Ah, just spotted the above reply to daBrado).
  • LincolnLincoln
    Posts: 2,058
    @Tim Remove the tag:
    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™."

    Vanilla developer [GitHub, Twitter]

  • TimTim
    Posts: 1,573
    Hahaha. I know about the tag removal method, however git has some kind of protection where if a client has already 'seen' a tag, it will remember the commit that was associated with that tag, even if the tag is removed and re-applied to a new commit. That's what happens to GitHub's download list. I removed and re-added the tag but it remembered the old commit.

    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 Senior Developer [GitHub, Twitter, About.me]

  • daBradodaBrado
    Posts: 13
    Tim said:

    @daBrado that value is something we've added and plan to use in the future. The real (current) version number is stored in index.php and we update that for you.

    Thanks for the info!
  • dejitarudejitaru
    Posts: 97
    after upgrading I cannot post at all. The progress indicators just sit there forever and spin. I can hit refresh and sometimes the post goes through but it doesn't bump the thread.
  • dejitarudejitaru
    Posts: 97
    dejitaru said:

    after upgrading I cannot post at all. The progress indicators just sit there forever and spin. I can hit refresh and sometimes the post goes through but it doesn't bump the thread.

    NVM cleared cookies and it works now.
  • DesmanthusDesmanthus
    Posts: 133
    This version is working MUCH better! Thanks for the update.
  • jeff_finleyjeff_finley
    Posts: 8
    I downloaded and installed it (upgraded from the 2.0 beta). I couldn't figure out an easy way to backup my database (Is there no DB backup tool from the Vanilla dashboard?) So I went ahead without backing up my db.

    Then I got hung up on this 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/structure"

    That led me to a page not found.

    The solution I found in another forum thread, it said to go to http://www.yourforum.com/index.php?p=/dashboard/utility/structure/ and then it will ask you to login. Once you do, you'll be taken to the upgrade database page in the new Dashboard.

    So far so good.

    It seems to have fixed a lot of the AJAX issues where it would just sit and load forever like when I'd send out a forum invite. It appears to have fixed our forum's double post problem as well.
  • droopalladroopalla
    Posts: 34
    ok, I havent used my forum much, as when I Installed it it was the day before version 2.0.1 came out. I tried update, like it was suggested, but got errors. Posted them here. Nobody could help. I still have those problems with updating. I am still on that version, do I need to update consecutively or straight to version 2.0.6. I am still thinking this will still have the same problem with the errors. Baring in mind, I am a novice here. so could somebody post in simple easy terms.
  • RajioRajio
    Posts: 177
    I've got a bug in mine - the number of 'answers' is not updating :S otherwise this is working a lot better.

    PS did a fresh install.
  • TimTim
    Posts: 1,573
    droopalla said:

    ok, I havent used my forum much, as when I Installed it it was the day before version 2.0.1 came out. I tried update, like it was suggested, but got errors. Posted them here. Nobody could help. I still have those problems with updating. I am still on that version, do I need to update consecutively or straight to version 2.0.6. I am still thinking this will still have the same problem with the errors. Baring in mind, I am a novice here. so could somebody post in simple easy terms.

    @droopalla You can update directly from 2.0 to 2.0.6. If you get more errors, post them and I'll try to help you.

    Vanilla Forums Senior Developer [GitHub, Twitter, About.me]

  • Sim2KSim2K
    Posts: 7
    Works for for me on my ASP.Net hosting (with php functionality) and my web.config instead of the .htaccess file.
  • iznkiznk
    Posts: 15
    Is there a place where I could see which files exactly and what have been changed in them so I can replace those files only? Because I modified the core files a little bit for my purpose.
  • LincolnLincoln
    Posts: 2,058
    @iznk I'd take the time to re-do whatever you did in core as a plugin. You're in for a world of hurt if you keep your site like that. If you need special hooks for what you're trying to accomplish, request them from the developers.

    Vanilla developer [GitHub, Twitter]

  • paigempaigem
    Posts: 8
    My update from 2.0 to 2.0.6 went smoothly except I have an SQL error in my utility/structure page after re-running the scripts:

    "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'where name = 'GDN_Discussion'' at line 1|Gdn_Database|Query|show table status where name = 'GDN_Discussion'"

    Any clue what is causing that and if it's affecting anything else in my forum?
  • raykrayk
    Posts: 183
    Edit: worked it out.
Sign In or Register to comment.