Loading...
 
Architecture / Installation

Architecture / Installation


Tiki v1.92 tiki-install.php takes me to a blank screen

posts: 2

my enivronment: red hat linux 4, mysql 4.1.12, php 4.3.9, apache 2

Installation does not complete.

After entering database info on the initial "tiki-install.php" Tiki Installer page, hitting enter takes me to a blank page.

I have tried all the sugestions on this forum. So far, no luck. PEAR is visible (I got the Swoobadoo display), I've raised php.ini mem limit to 32MB, the mysql 4.1 db
install recognises old-passwords (set in my.cnf).

Any help resolving this is appreciated.

posts: 2

> my enivronment: red hat linux 4, mysql 4.1.12, php 4.3.9, apache 2
>
> Installation does not complete.
>
> After entering database info on the initial "tiki-install.php" Tiki Installer page, hitting enter takes me to a blank page.
>
> I have tried all the sugestions on this forum. So far, no luck. PEAR is visible (I got the Swoobadoo display), I've raised php.ini mem limit to 32MB, the mysql 4.1 db
> install recognises old-passwords (set in my.cnf).
>
> Any help resolving this is appreciated.

Ok let me make my question simpler:
Has anyone been able to install v1.9.2 on redhat linux 4 using php 4.3.9 and mysql 4,1,12? I have installed 1.9.2 on linux 3 with mysql 3.23 with no problems. Using the same steps on my current platform returns a blank screen.


posts: 1

> my enivronment: red hat linux 4, mysql 4.1.12, php 4.3.9, apache 2
>
> Installation does not complete.
>
> After entering database info on the initial "tiki-install.php" Tiki Installer page, hitting enter takes me to a blank page.
>
> I have tried all the sugestions on this forum. So far, no luck. PEAR is visible (I got the Swoobadoo display), I've raised php.ini mem limit to 32MB, the mysql 4.1 db
> install recognises old-passwords (set in my.cnf).
>
> Any help resolving this is appreciated.

I have exactly the same problem with redhat 4 and the versions you have used. An install on gentoo linux works just fine.

Note that there are no errors logged in the apache log at all regardless of what logging level I enable