Vanilla 1 is no longer supported or maintained. If you need a copy, you can get it here.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
Options

Checking for updates issue

edited March 2008 in Vanilla 1.0 Help
Just upgrade to Vanilla 1.1.2, went over to the update section, and I get a message that tells me: Error: First|Vanilla is up to date. I click okay, and then the rest of the page, everything just says "Checking for updates." I'm not even getting a spinning progress bar, so I'm a little confused. Tried emptying the cache, as I saw that fixed another issue with the updater from another thread, no go. Ran a quick search, didn't see anything that looked similar, so I figured I'd ask.

Comments

  • Options
    MarkMark Vanilla Staff
    edited March 2007
    That definitely sounds like you aren't using the most recent javascript file. Are you sure all of the files were uploaded successfully? (you'd be surprised how often this is the problem).
  • Options
    Is there a way that Vanilla could check itself (the core files) when you click a button? Checksum the files or something? That might prevent this?
  • Options
    Yet another reason to have more core file-level more checksums... (hint hint)
  • Options
    @Mark - just double checked and re-uploaded all .js files, same thing. Any other ideas?
  • Options
    I'm having this issue as well. I keep my Vanilla install updated with Subversion so I should have the newest versions of all the files. Same behavior on Firefox and IE6, regardless of cache.

    Saw that people resolved the issue by either restarting the browser or using a different browser, but no dice for me.

    Any other suggestions?
  • Options
    MarkMark Vanilla Staff
    edited March 2007
    Well, why don't you take a look at the javascript files you're using and compare them to the ones here: http://lussumo.com/svn/vanilla/trunk/js You should be particularly concerned with this one: http://lussumo.com/svn/vanilla/trunk/js/global.js If those don't match, that's your problem. If they do match, take a look at the framework's update check control in your installation and the one located here: http://lussumo.com/svn/framework/trunk/Framework.Control.UpdateCheck.php If those don't match, that's your problem. If they do match, take a look at the theme file for that control, located here: http://lussumo.com/svn/vanilla/trunk/themes/settings_update_check_validpostback.php If those don't match, that's your problem. If they do match, come back here and we'll look deeper :)
  • Options
    oh whoops - forgot to say i solved this just by re-installing. was probably some silly change i made that conflicted, in any case it's fixed now. maybe re-installing was a bit drastic, but it worked, so.
  • Options
    @Mark

    Thanks for the heads-up. Enabling the default theme made the update work just fine. Thanks!
  • Options
    MarkMark Vanilla Staff
    Yay!
  • Options
    been having this problem for a while again. came back here, tried to look at the files mark linked, got some 404's. i'm not keen on svn so perhaps i did something wrong. tried a full reinstall again (deleted everything, downloaded the latest copy of vanilla, then reuploaded all my old extensions/themes and pointed the fresh install to the old DB). same message: Error: First|Vanilla is up to date. i've seen a couple other threads with similar issues, and give that nothing i did to fix it last time worked and this is a brand new install, i'm stumped. maybe it's something server-side i should be looking at? any help is much appreciated, tia.
  • Options
    All the Vanilla svn paths now have an extra /src/ folder in them: http://lussumo.com/svn/vanilla/trunk/src/js/ http://lussumo.com/svn/vanilla/trunk/src/js/global.js http://lussumo.com/svn/vanilla/trunk/src/themes/settings_update_check_validpostback.php Framework and People should still be the same. Issue is a bit strange...
  • Options
    thanks WallPhone!

    sadly, even after replacing the files in my install with the ones from the svn, nothing has changed.

    this thread seems to show at least a couple others with this problem, maybe they can weigh in and offer some insights.
This discussion has been closed.