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.

Extended How-to install Vanilla 2

13

Comments

  • Thanks!
    I sent the install to a friend who has another Nexcess account (the FastCGI version), and he was able to get it working.
    If this doesn't work, I'll pore over our info dumps, and see if there is anything that could explain it.
  • Well, it sorta works:

    http://magshare.org/vanillaforums-Garden-cced7d8/settings

    On first blush, it tried to direct me to

    http://magshare.org/settings

    Which gives you my excellent 404 page. I'll dig around the config, later, to see if I can figure it out.
  • Actually, looking at this, it may be the same as before, except with the wrong baseURL.

    I'll look over our infos, and see if I can determine the issue.
  • I think I may know what the problem is. I think it's battling mod_rewrites.
    I'm installing this at the main level of a WP site with pretty permalinks.
    I'm gonna set up a separate account with a subdomain. I'll bet it works. It will be a while before I can report back, as the DNS needs to seed out.
  • Nope. Back to the drawing board.

    http://forum.magshare.org/
  • It works with the new fix on the new domain.
    There may be an issue with the base directory.
    In any case, this is enough for me to go with now.
    Thanks!
  • blizeHblizeH ✭✭
    edited May 2010
    I've just upgraded - but I can't reply to existing topics? :/

    New topics are fine. Existing ones not so much.
  • Hi there!

    Call me a soar loser or whatever else you can think of. I get everything that is written in the post and its very well written I will say. Kudos to iamkeir!

    My question is: Where is the install folder located? Its not really standing out and "Waving" its hands at me right now.

    Thanks for the input in advance.

    Thanks,
    Tim
  • Well I finally found out where the "install" folder was. Of course this was the folder I created when I unzipped the file.

    Another question: I now get the error "No input file specified." with no other errors or anything else on the screen. How? When I go to install the vanilla forum from the folder I created "Forum" then I get this error message. I have gave the 3 files 777 permission. Im not sure if this helps but here is the url that I get when try to install the forum. First: www.forum.xxxxxxx.com/Forum then it changes to this: www.forum.xxxxxxxxx.com/Forum/index.php/dashboard/setup

    Can anyone please assist me?

    Greatly Appreciated.

    -Tim
  • edited May 2010
    For whomever it may concern, here's how I setup Vanilla.

    --Download the latest vanilla
    http://github.com/vanillaforums/Garden/downloads or
    http://download.github.com/vanillaforums-Garden-Vanilla_2.0_rc1-0-gcb12ba2.tar.gz

    --I had to change the .htaccess file for the site to work (it wouldn't even show up until
    I did this

    #RewriteEngine On
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteBase /com.mysite/development/vanilla/vanillaforums_rc1/
    RewriteRule ^(.*)$ index.php/$1 [QSA,L]

    --Set permissions the right way (instead of 777)
    > cd /path/to/my/vanilla/install
    > sudo chgrp -R www conf cache uploads
    Note that "www" is my apache's group. In other servers it may be "apache" or something else.
    See you /etc/httpd/httpd.conf file to find your group.
    > chmod -R 775 conf cache uploads

    --Create a mysql DB and user

    --Load Vanilla and configure.
  • Hello!

    Is it possible to install Vanilla on nginx?
  • LincLinc Admin
    edited June 2010
    I've figured out the permissions issue on Linux. You should never set 777. Use 775 instead.

    If 775 doesn't work, you'll need to either:

    A) Add the 'apache' user to the group that owns your web directory.
    -or-
    B) Change the group of the file/directory in question to 'apache'
    -or-
    C) Change the owner of the file/directory in question to apache (in which case you can even use 755)


    Either way you'll need shell access or open a support ticket to do this.

    To do A, use this on Red Hat/CentOS:
    # usermod -a -G groupnamehere apache
    To do B, use this:
    # chgrp -R apache /path/to/file/or/directory
    To do C, use this:
    # chown -R apache /path/to/file/or/directory
    Careful with chown! You can break things by chown'ing the wrong files. Double-check your paths before hitting enter.

    Note that apache sometimes gets run as another user or group name; 'apache' is simply the default.

    You mileage may vary, but if you have tech support worth a damn they'll be able to help you figure it out.

    Remember kids: '777' permissions will get your box hacked. :D
  • I just installed Vanilla2. I am able to sign in with the user and password I created using google chrome and everything appears ok. When I try to sign in with firefox, basically nothing happens. I am not signed in and there is no error message.
  • I figured it out. Removed cookies for the site and I got signed in.
  • Trying to import Vanilla 1 data into Vanilla 2. I've got all the tables in the same database (the GDN_ and LUM_). The import screen makes no sense to me. It says "Use this page to import data from another forum that was exported using Vanilla's exporter." Vanilla 1 doesn't have an exporter as far as I know. It wants to upload a file. Makes no sense. The Vanilla 1 files I want to import are in the same database. Why do I need to upload anything?
  • LincLinc Admin
    We're building a standalone app to export any forum into a special Vanilla 2 file. That's the file the importer is looking for. Almost done!
  • Bugger! didn't realise that we were not in a position to import the Vanilla 1 forums yet, I've just upgraded my busy forum and am too now sitting at the import page.

    Any news or even a beta I can try and use for now?
  • LincLinc Admin
    @rockwaldo Sent you a message.
Sign In or Register to comment.