HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.

Vanilla 2.0.18 is nearing End Of Life

Vanilla 2.0.18 will receive no more upgrades after the end of 2014. If you haven't upgraded to 2.1 yet, please do so as soon as possible after testing your theme and plugins against it.

The instructions for upgrading to 2.1 are in the new & improved README file that comes with it. There is also a long discussion on any compatibility issues you may run into: http://vanillaforums.org/discussion/26703/plugins-themes-that-work-and-don-t-work-in-vanilla-2-1

This is also a good point at which to note that we now release updates & security fixes at a much quicker rate than we did in, say, 2013, so it's important to keep an eye out for upgrades.

We'll be looking for someone to tackle a new-version notifier that can get backported to 2.1 to help keep folks updated. When we move to 2.3, we don't plan to continue backporting fixes to 2.1 as we have been for 2.0.18 this year. This is a unique circumstance due to how long 2.0.18 was in circulation and some of the unfortunate backward compatibility breaks we did.

Comments

  • Were you thinking http://vanillaforums.org/addons/update/find/* I see referenced in the settings controller?

    I suppose this would be part of the new addons repo?

    Search first

    Check out the Documentation! We are always looking for new content and pull requests.

    Click on insightful, awesome, and funny reactions to thank community volunteers for their valuable posts.

  • @hgtonight said:
    Were you thinking http://vanillaforums.org/addons/update/find/* I see referenced in the settings controller?

    I see AddUpdateCheck gathering information, but I don't actually see any callbacks to .org beyond the feed gathering for the news section. What am I missing?

    I do believe the new addons repo needs an appropriate callback for things like this, yes.

  • peregrineperegrine MVP
    edited October 2014

    as an aside on this page http://vanillaforums.org/

    then if you click on documentation link at top of page from that page,
    it goes here: http://vanillaforums.org/docs

    then if you click on top link documentation on http://vanillaforums.org/docs
    it goes here: http://docs.vanillaforums.com/

    it's actually nice to have both documentation links to old and new, until new is completed.

    But in case you weren't aware.

    I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.

  • @peregrine My immediate goal is to open source the .org repo and turn over issues like this to you guys. There are a few blockers I need to clear before that can happen (like private data that got committed).

  • @Linc said:
    I see AddUpdateCheck gathering information, but I don't actually see any callbacks to .org beyond the feed gathering for the news section. What am I missing?

    I am referring to this https://github.com/vanilla/vanilla/blob/2.1/applications/dashboard/views/settings/applications.php#L121

    I am not sure if it was just an unfinished feature, or stubbed out for the OS release.

    Search first

    Check out the Documentation! We are always looking for new content and pull requests.

    Click on insightful, awesome, and funny reactions to thank community volunteers for their valuable posts.

  • peregrineperegrine MVP
    edited October 2014

    one of the few instances when "end of life" can't come too soon and everyone upgrades. Amen,

    I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.

  • @hgtonight I never noticed that. I believe the technical term for that is "half a feature".

  • Hello.
    This week I took a "crisis" call/job to rescue two installs, one a "forum" on a failing server with the ex-webmaster MIA for months.

    I now know that it's Vanilla Forums, which I had never heard of in 15 years of basic website work (WP is bulk of it now). Version says at bottom of Dashboard/index.php ('APPLICATION_VERSION', '2.0.18b4')

    It is migrated to new up-to-date VPS server and working fine (now after hours on this site/also hosting techs).

    I see I need to upgrade it to current version asap, but am told that there is php customization - I have no idea where - I am not a php coder - understand some - copy/paste a lot.

    ? What docs should I start with, and ? once I have it working in a test install on same server, how do I avoid the "it's not working now" woes I read here when I attempt to implement on active install in another folder/another domain name?

    ? What is the best method to set up my test install? etc.

    Thank you!

  • peregrineperegrine MVP
    edited November 2014
    • one way for a test forum (replace versions and use vanilla 2.1.6 as your ultimate target).

    http://vanillaforums.org/discussion/24793/yet-another-vanilla-upgrade-and-duplication-tutorial

    there should be no php customization needed provided

    • the previous person didn't modify the vanill core coded (which they shouldn't do for the very same reason it is difficult to upgrade).

    -you use a vanilla 2.1 compatible theme (a few come with core).

    • you check the dicussions regarding compatible plugins and themes that work

    hints for everyone upgrading or installing. should cover just about everything.

    if you take the time to read these carefully and there were no cre changes (than it should be smooth sailing).

    • read the Readme

    https://github.com/vanilla/vanilla/blob/2.1/README.md

    • read the faq (all comments)

    http://vanillaforums.org/discussion/28420/faq

    • read 2.1 release notes discussion and comments

    http://vanillaforums.org/discussion/26685/vanilla-2-1-stable-released#p1

    • and this

    http://docs.vanillaforums.com/developers/troubleshooting/

    • and this

    http://vanillaforums.org/discussion/26703/plugins-themes-that-work-and-dont-work-in-vanilla-2-1

    • and this

    http://vanillaforums.org/discussion/comment/220308/#Comment_220308

    I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.

  • edited November 2014

    Create a data base backup of the existing forum

    Install vanilla on a test subdirectory

    Upload your database

    run utility/update

    run utility/structure

    you may need to run it several times

    Makes sure all of the plugins are up to date before you add them to the plugins folder and enable them, the same goes for themes

    Compare the two installs to find the customizations, if they are in a theme in the form of views, you will run into problems with compatibility.

  • I do see the top of this discussion that Linc authored.
    ? Is that IT?
    I will start there if questions above are addressed first-up in his great work.

    Whew.

    http://vanillaforums.org/discussion/28272/vanilla-2-0-18-is-nearing-end-of-life
    Linc
    Community Instigator
    Detroit Vanilla Staff
    October 22 in Releases

    The instructions for upgrading to 2.1 are in the new & improved README file that comes with it. There is also a long discussion on any compatibility issues you may run into: http://vanillaforums.org/discussion/26703/plugins-themes-that-work-and-don-t-work-in-vanilla-2-1

  • peregrineperegrine MVP
    edited November 2014

    its your choice what you decide to do. whatever works best for you.

    the links i provided give you additional information that is not in the opening post, so you might consider reading them if you have issues.

    the main problem I've seen on this forum is people skip steps or just ignore different things in the readme and release notes, and then come back to ask the same questions, that were already addressed in the links provided in the comments already given. You will see this on long drawn out discussions, where the same user comes back and asks the same question in a new post for which they already received the correct answer in their previous discussion. Or people who just ask a question, when they already made up their mind to do it a different way, then choose to do it their way, and then find out, they could have saved alot of time if they followed the advice in the first place.

    It may not be the case for you, but just my observations on people who have smooth upgrades and solve things quickly and people who continually stumble.

    I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.

  • Wise, peregrine. Your comments were many I gleaned/applied to this situation. I managed to pull it off just reading what I see and guessing. I was grateful that you and Linc kept at it given what you say. The rest of the audience gained, including the new hosting company where they are adept at reading the internal error messages. If those are good, it's one whack at the jungle after the next. It was really the little nuances.

    I searched mostly on error messages. "Bootstrap" was a challenge concept until I saw..... "Never ever mess with the boostrap.php file - did we mention never do it..." - nuff said.

    Thank you!

  • I NOW see all the information you both provided.

    Thank you peregrine and vrijvlinder (just now came up on another refresh of my page).

  • reminder that you have 30 days :)

  • edited December 2014

    Working on it as I write... I replied to email that plugins are the big hangup. ..... I mean learning opportunity. Almost ready to deploy as soon as I finish researching two. Will add my results to doc when final. THANKS.

Sign In or Register to comment.