Furry stuff, oekaki stuff, and other stuff.
You are not logged in.
I'm trying to set up a fresh install of wacintaki 1.3.4 from this computer using apache2.2.2 and PHP 5.2 dev.
After i install php, i can a test page just fine, but when i view install.php i get a blank page (I was previously able to see the page, but now i cannot even after reinstalling PHP). I haven't installed MySQL yet, as i want to resolve this before adding anything else to my system.
Last edited by Ray (10-03-2006 18:52:09)
Offline
Do you remember what changes you made to your php.ini file after installing it?
Even though the page is blank, is there any code visible when you do a View Source in your browser? In all circumstances, regardless of what it is doing, the installer should at least print an HTML header and import a style sheet.
Apache needs to be set up properly to recognize PHP scripts, and it is a pain based on the [mis]directions given by both the Apache and PHP teams.
Check these settings in your httpd.conf file. "(...)" refers to default settings:
DirectoryIndex (...) index.php AddIcon /icons/script.gif (...) .php # # For PHP support: # ScriptAlias /php/ "c:/php/" AddType application/x-httpd-php .php AddType application/x-httpd-php .php3 AddType application/x-httpd-php .php4 AddType application/x-httpd-php .phtml Action application/x-httpd-php "/php/php.exe"
Make sure the "ScriptAlias" path above points to where PHP is installed on your hard drive.
Offline
Thanks for the reply.
I tried editing my httpd file again without luck.
I think the only thing i changed in my php.ini was the doc_root
I have included below a link my php.ini and httpd.conf files
(*snip)
When i view my /index page I am redirected to the install.php but cannot view the page. There is something in the source. (*snip)
Sorry but i'm really stumped as to how to get this working.
Last edited by Ray (10-06-2006 06:17:16)
Offline
More information about installing PHP on Apache2 can be found here: Installation manual from PHP.net
If PHP is installed as a module, you don't need to assign an action to tell Apache to load the PHP executable, so you end up with something like this:
LoadModule php5_module "d:/php/php5apache2.dll" PHPIniDir "d:/php" AddType application/x-httpd-php .php AddIcon /icons/script.gif .php
If you're using PHP as CGI, you need to explicitly point out where the PHP executable is located. It's easier to do this with a ScriptAlias:
ScriptAlias /php/ "d:/php/" AddType application/x-httpd-php .php Action application/x-httpd-php "/php/php.exe" AddIcon /icons/script.gif .php
In this case, references to "/php/" will instead point to "d:/php/". In your config file, you're using an Action assignment with a ScriptAlias ("/php/"), however, you're lacking a ScriptAlias command to set "/php/" to "d:/php/".
Now, I prefer to run PHP as CGI on my machine, so the log files work the way I like them, and it's more reliable, as a problem with PHP won't crash the web server. However, you will not be able to use/test ".htaccess" files if PHP is set up this way, which can be a bother. Setting up PHP as CGI is helpful for development, but setting it up as a module more closely reflects "real-world" usage, as that is what most servers use.
First decide whether you want PHP to run as CGI or as an Apache module, then use one of the appropriate code segments above, but not both at the same time.
Oh yeah, a ScriptAlias and a path must have identical slash usage, as follows:
Correct: /php/ "d:/php/" /php "d:/php" Wrong: /php/ "d:/php" /php "d:/php/"
Offline
Alright, it seems PHP and MySQL are installed okay now, but when i view the install.php i get the following error
Warning: Unexpected character in input: '\' (ASCII=92) state=1 in D:\wamp\www\oekaki\install.php on line 336
Parse error: parse error, unexpected T_STRING in D:\wamp\www\oekaki\install.php on line 336
Last edited by Ray (10-07-2006 17:09:37)
Offline
In your php.ini, change this line:
short_open_tag = Off
to this:
short_open_tag = On
Short tags are something that people have been doing for years, and the PHP team decided just not to support them anymore. As a result, a lot of scripts won't work properly. The PHP team did this with registered globals, too, and it took me a week to track that problem down.
Offline
Thank you very much . Everything is in working order now.