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.
Installation woes
I found a link to vanilla late last night and immediately proceeded to download the thing. It looks great.
Unfortunately I can't install it. When using the installer and choose to continue from step 2 to what is presumably step 3, I get the error:
I can't do a manual install because I don't know how to process the vanilla.sql file - I don't have SQL command line.
Here's the proverbial phpinfo page
Thanks in advance
Stu
Unfortunately I can't install it. When using the installer and choose to continue from step 2 to what is presumably step 3, I get the error:
Fatal error: Call to undefined function: html_entity_decode() in /home/httpd/vhosts/zenapproach.co.uk/subdomains/boards/httpdocs/library/Utility.Constant.class.php on line 69...its all greek to me. Is my PHP version too old?
I can't do a manual install because I don't know how to process the vanilla.sql file - I don't have SQL command line.
Here's the proverbial phpinfo page
Thanks in advance
Stu
1
This discussion has been closed.
Comments
Okay, one step at a time:
My fix applies to that original error message you were talking about (html_entity_decode). My fix will not repair all of those "Warning: open_basedir restriction in effect." errors.
I think you are getting that "Warning: open_basedir restriction in effect." error because I am including all of my files absolutely from the root of your server. I bet that if you included everything relatively, it would fix the problem:
Open up appg/settings.php and edit line 21 from this:
define("agAPPLICATION_PATH", "/path/to/vanilla/");
to this:
define("agAPPLICATION_PATH", "./");
and see if that works.
Typically, an absolute path on a properly setup host will appear as one of the following two ways:
/home/lech/domain.com/wwwdocs/vanilla/
you'll notice that the domain.com bit in that example is bolded out. In many cases, this is a relative link to the real location (like in my case) in your home directory which points it to the actual path. Many times your ftp program will treat this as transparently as possible just to not confuse you. But that would look something like this in the servers actual file directory structure:
/www/domain.com/wwwdocs/vanilla/
In my case, It's safe to use either of those paths to get vanilla working. Now this is where you're head will probably pop trying to locate the actual path. On several large vhosts (I'll be using MT in this example) they truely try to mask the absolute and relative paths because many of them use virtual server environments. Simply to say, it acts like it's own machine.
However there's still the deal of the real absolute paths that go back to the REAL root file system. So what you might see like in my previous examples is only the end of the whole real path. This is probably the piece you need, and the only way to do it is by scraping through the error logs. The real path might look something like this:
/customer12938/vhost4/block10/lech/www/domain.com/wwwdocs/vanilla/
While it might be good for them, it doesn't really help you if you're trying to setup your own software I hope that helps someone.
thx lech.