Hello,
After filling in the correct system source dir in step 3 and pressing [next] i get a blank screen. I tried waiting but nothing happens.
I tried this both in konqueror and Firefox.
If I fill in a wrong dir it does give me the appropriate errors so it does validate my input.
Any ideas?
thx
rottie
Do you get the message 'System root has been set to xxxx' ? Is safe mode on for your server? If you remove the @ symbol out the front of 'fopen' on line 190, is an error output to screen?
>> Do you get the message 'System root has been set to xxxx' ?
No, no message. Just a blank screen.
>> Is safe mode on for your server?
I don't know. This is on a hosted server. I have no access to the configuration files of php.
>> If you remove the @ symbol out the front of 'fopen' on line 190, is an error output to screen?
Line 190 of which file?
I checked with phpinfo. Configure command has the value= './configure' … '–with-safe-mode' …
That's good right?
Unfortunatly. Under PHP CORE I find this value:
Safe mode Off Off
safe_mode_exec_dir no value no value
safe_mode_gid Off Off
safe_mode_include_dir no value no value
So I guess that's bad. Is there a way to avoid this?
[quote]>> If you remove the @ symbol out the front of 'fopen' on line 190, is an error output to screen?
Line 190 of which file?[/quote]
Looking through the installer files I think he means line 190 of [Matrix Installer Root]/steps/installdirectory.inc. 
[quote]I checked with phpinfo. Configure command has the value= './configure' … '–with-safe-mode' …
That's good right?
Unfortunatly. Under PHP CORE I find this value:
Safe mode Off Off
safe_mode_exec_dir no value no value
safe_mode_gid Off Off
safe_mode_include_dir no value no value
So I guess that's bad. Is there a way to avoid this?[/quote]
Actually, that's probably a good thing in this case. The configure script option shows that it was compiled with safe-mode functionality but it hasn't been turned on, so there is no safe mode restriction in effect - so that can probably be ruled out as a possible cause.
Ooops, yeah what Luke said ;).
If you feel confident tinkering with php code, you could try removing the call to testSysRoot in installdirectory.inc. So far I can't replicate getting a blank screen on step 3 through changing permissions around, however someone else is having problems with this too.
Marcus,
I guess that's me 
Yes, this one helped:
Commenting out everything at [Matrix Installer Root]/steps/installdirectory.inc
in a function _testSysRoot($sys_root) and keeping only the line
$success = true;
worked.
Thanks,
Gregory
It's strange; I've tried all sorts of things to make that code break (safe mode, no write access etc) and it was able to handle the error. Anyway, have you managed to get it to work now?
Well, not exactly. I've been stuck at step 5
Fatal error: Cannot instantiate non-existent class: pear_registry in
/var/www/html/installmatrix/steps/versioncheck.inc on line 281
It's the same error as with previous installer. I guess this has something to do with PEAR path ? Currently I'm doing on this issue with my support stuff as I am on a hosted server (Ensim) .
You can't get MySource Matrix to work on an Ensim server without root access to the server itself, to change the way PHP works. In High Security mode on Ensim, PHP won't allow the Matrix system to access the core PEAR modules, and you cannot install new PEAR modules in the Virtual Host either.
On the PEAR issue, did you try leaving the pear path blank? That will make the installer try and load the classes manually instead of through the registry.
With regards to ensim security, what happens if you manually install the PEAR modules under matrix/php_includes?
If the hosting provider is willing to work with you on this, its an easy fix to get Ensim to run Matrix. If the provider edits the /etc/httpd/conf/virtual/siteXX file (where XX is the number of your site) and change this line:
Change:
php_admin_flag engine off
to
php_admin_flag engine on
And then comment out/remove these lines completely:
Action php-script /interpreters/php-script
AddHandler php-script .php .php4 .php3Then you'll be using the global PHP Apache module installation and you can reference the PEAR installation at /usr/share/pear. The hosting provider can then easily install/upgrade PEAR modules using the "pear" command:
# pear install Mail_Mime
# pear install XML_HTMLSaxHope that helps.
Hi Avi,
thanks. They were prepared to help me with that but now the PEAR version is too old and they've been having really wierd upgrade problems with PEAR:
…this is very2 wierd. If you login via SSH and do:
cd /
pico -w go-pear.php
…you will see the version is written as:
$Id: go-pear,v 1.63 2004/06/06
You can even re-install it via command below:
php ./go-pear.php
after the installation, you should see:
install ok: PEAR 1.3.1
install ok: Archive_Tar 1.2
install ok: Console_Getopt 1.2
install ok: XML_RPC 1.1.0
install ok: DB 1.6.5
install ok: Net_Socket 1.0.2
install ok: Net_SMTP 1.2.6
install ok: Mail 1.1.3
install ok: XML_Parser 1.2.0
install ok: PHPUnit 1.0.1
But when we check this directory after the installations:
cd /usr/share/pear
pico -w DB.php
It will state the version is 1.59 instead of 1.6.5…
Any suggestions ?
What do you get when you use this command?
# pear list
Avi,
I get
===================
Package Version State
Archive_Tar 1.2 stable
Console_Getopt 1.2 stable
DB 1.6.5 stable
HTTP 1.2.1 stable
Mail 1.1.3 stable
Mail_Mime 1.2.1 stable
Net_SMTP 1.2.6 stable
Net_Socket 1.0.2 stable
PEAR 1.3.1 stable
PHPUnit 1.0.1 stable
XML_HTMLSax 2.1.2 stable
XML_Parser 1.2.0 stable
XML_RPC 1.1.0 stable
but again when I check DP.php at usr/share/pear
// ±---------------------------------------------------------------------+
//
// $Id: DB.php,v 1.59 2004/07/08 21:15:11 danielc Exp $
//
// Database independent query interface.
is written. I don't know if DB.php "date modified" stamp means anything in this
case but it is 29th July.
It seems like whichever PEAR is in the path is not in /usr/share/pear – during the installation, leave the PEAR path empty (blank) and see if it detects the PEAR modules automatically.
No, it didn't detect it automatically. Now it's telling me " Could not find the PEAR registry. You can still proceed with install, but you may encounter some errors. "
I would go ahead with the install and see how far you get. You have all the required PEAR modules. Ensure that you also have MySQL 4.0 and you should be good to go.
Avi,
during step 15 and got the error
MySource Error
DB Error: syntax error
SET table_type=innodb [nativecode=1064 ** You have an error in your SQL syntax near 'table_type=innodb' at line 1]
You need to upgrade MySQL to v4.0.