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.
IIS Vanilla 1.0 Install Problem
I am attempting to evaluate Vanilla. Yesterday I installed Version 0.9.2.6 without incident. Everything worked fine.
When I saw that some of the new extensions require Version 1.0, I decided to install that. Since I am still in the evaluation stage I decided to simply do a full install of 1.0, rather than an upgrade. I created a new folder. Uploaded the software. And tried to run installer.php. I get the first page, but when I press enter to proceed to the second page the system hangs and I get a blank HTML page back.
When I view the source of the HTML page I find this -
The following error occurred: [code=CANT_CONNECT] Could not connect because of networking problems. Contact your system administrator.
Strange that 0.9.2.6 installs cleanly on my server. 1.0 does not. I never get to the point in the installer where I can enter my server and database information. Nothing.
I am hosted thru Host Excellence. My information is as follows.
PHP 4.4.1
Windows NT IIS7 5.0 build 2195
Any ideas?
Thanks
0
This discussion has been closed.
Comments
Vanilla 0.9.2.6 and Vanilla 1 are very VERY different applications. The first step in Vanilla 0.9.2.6 just checked permissions, but the first step in Vanilla 1 actually creates configuration files on your server. It is likely something to do with that.
The installer has a lot of debugging stuff thrown in there so that you get verbose error messages, but whoever configured your server has the power to override inline php configuration settings and make it so that errors don't get treated properly and instead you get strange things like a blank page. Some hosting companies will do this so that even if there are errors in applications, their customers won't see them and therefore they won't get as many support requests. Other companies do it because they just don't know any better.
Either way, the only way to figure out what's going wrong is to go into the file and add echo('test');. Then run the script and see if it echos. Then keep moving that echo statement down in the file until it stops coming out. That way you can identify which line actually causes the script to hault. My guess is that it will be somewhere between line 127 and 165.