Fork me on GitHub
Current releases are 2.1.3 (9 Sept 2014) and 2.0.18.13 (5 Aug 2014)

Ready for 2.1? Find out if your favorite plugins are compatible. The 2.0 branch will no longer receive updates after Dec 2014.

Ok, what does this instruction mean in upgrading?

edited August 2010 in Vanilla 2.0 Help
I understand I sign into the forum as admin and follow the steps to upgrade but on my last upgrade I did not find the upgrade button. What does the following mean?

"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.yourdomain.com/path/to/vanilla/utility/structure"

Is this done in another browser window? What is the vanilla utility structure? Say my forum is at www.imstumpted.com. How do I get to this upgrade button?

May be obvious to someone more familiar with forum software but I am stumped!

Thanks

Comments

  • Go to :

    http://www.imstumpted.com/utility/structure

    & login using your admin username.

    If Vanilla is in a sub-directory, use:

    http://www.imstumpted.com/vanilla-folder/utility/structure

    (replacing "vanilla-folder" with the name of your folder)
  • fr1dayfr1day New
    edited August 2010
    Or in my case the only way I can get it to work is by going to http://www.imstumpted.com/index.php?p=/dashboard/utility/structure/

    Might be worth a try if clean url's are not enabled.

    [EDIT] Perhaps asking you to navigate to the page is not the best way of phrasing it. All you have to do is copy the above URL's into a browser window and it should give you a page where you can update the database.
  • Thanks guys! Will the further explanation on the procedure I was able to get to the update page.

    It was fr1day's method that worked for me. JeffDunne's method produced a page error but it must be the way the path to my forum is configured i guess.

    Thanks again
  • Using friendly URLs is a good idea.

    Personally I've found far less problems when using them.

    In the config, change $Configuration['Garden']['RewriteUrls'] to equal TRUE
  • Thanks JeffDunne but when I set that line to TRUE I cannot sign into the forum. The popup sign-in window stalls. Any ideas why and a way to get friendy URLs working?
  • Or in my case the only way I can get it to work is by going to http://www.imstumpted.com/index.php?p=/dashboard/utility/structure/

    Might be worth a try if clean url's are not enabled.

    [EDIT] Perhaps asking you to navigate to the page is not the best way of phrasing it. All you have to do is copy the above URL's into a browser window and it should give you a page where you can update the database.
    This worked for me, thank you!
  • edited September 2010
    @JeffDunne: The reason you see far less problems is because a lot of the Vanilla code (and tons of the plugins) assume people are using friendly URLs. By doing so, they break things for everyone who isn't.

    In order to use friendly URLs currently, you have to be using Apache as your web server. I'm using Lighttpd and have been unable to come up with rewrite rules that work universally for the site.

    So sometimes, friendly URLs are just not an option. The fact that so much of the documentation and code relies on this (and they aren't even on by default) is certainly confusing.

    @Dan Devine: In order for friendly URLs to work out of the box, you need to make sure your .htaccess file is located in your base Vanilla directory. This requires that you're running Apache. If you're using a different web server, you'll have to find or write some rewrite rules that mimic the .htaccess functionality.

    In Linux, the . in front makes it a hidden file. Depending on how you copied things over, you might not have the .htaccess file in place.
  • TimTim Lord of Servers Vanilla Staff
    @Lykaon On the topic of Lighttpd and ModRewrite... I am surprised that you've had so much trouble getting a working set of rules.

    I have never used Lighttpd, but I just checked out this documentation page on their site and at first glance it seems like our Apache rules are almost copy-pasteable as Lighttpd rules, with different formatting.

    Have you tried something like this:
    url.rewrite-if-not-file = ( "^(.*)$" => "/index.php\?p=$1" )

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

  • edited September 2010
    @Tim: Somehow I missed your post yesterday. That's pretty much what I've tried (though you have an extra slash after php).

    It *mostly* works. But when I click on "Change Picture" I get "The page you were looking for could not be found." This seems to be the case for almost all of the pop-ups. It must be something about the rewrite rules that aren't getting applied on those sorts of requests.

    I thought that 2.0.6 might fix it, but it doesn't seem to have. If I right-click and "open link in new tab" then it seems to work fine. That part is even stranger imo.

    The link /profile/picture works fine when not in a pop-up. It's almost as if when requests are made from Javascript, the rewrite rules aren't working or something weird like that.

    I also can't do mundane things like enable plugins. It pops up a "page not found" red box after I try to do so.

    If anyone wants to see the effects of this, you can register and check it out on my test site: http://forums.lykaon.com. I have it set up with lighttpd rewrite rules that *mostly* work but cause the problems listed above. This test install has no plugins or customization.

    Current rewrite rules are:

    url.rewrite-once = (
    "^/(applications|cache|conf|js|library|plugins|themes|uploads)/(.*)$"=>"/$1/$2",
    "^(.*)$"=>"/index.php?p=$1" )

    I couldn't get the "rewrite-if-not-file" directive to work at all in lighty. Could be my version.


    Edit: It means nothing to me yet, but this code in jquery.popup.js (line 68):

    $.get(target, {'DeliveryType': settings.deliveryType},...
    is what is returning the 404. I alert-boxed the data that comes back and it's a big fat 404.
  • edited September 2010
    Ok. I give up. Sorry for the novel above.

    If I remove the arguments and just pass {} then I get the entire page (rather than just the upload picture part) in the pop-up, which I guess one could say is progress. It's better than file not found. It looks like the DeliveryType is being set to VIEW and for whatever rewrite-related reason, this causes a 404 to be sent back to jQuery.

    I'm out of ideas.
Sign In or Register to comment.