Known Issues with Installation

This post will list any known issues with installing MySource Matrix (updated as new information comes). If it is listed and addressed here, then please do not post a new thread with the same information. If you have a query or feedback about any issue raised, feel free to post in this thread. Note: Matrix WILL NOT install in an environment with Safe Mode or Open Basedir in effect.


Cannot log in after installing on top level domain using Alias matches

Bug Report



When installing on a top level domain, ie matrix.squiz.net, and you attempt to log in, you receive a 404 error. This is because the alias match generated by the installer is missing a trailing slash after the index.php for this case. Either change your alias match to have the trailing slash (for top level domain). This problem only exists in the very first release of the installer; most people will have a correct version.



The htaccess for the symlinks looks wrong!

It only looks wrong. The actual symlink created is correct, it has been fixed for the next installer release.



Fatal error: Maximum execution time of 30 seconds exceeded

The final step of the installer is very intense and can take some time to complete. If you’re receiving this error, try putting ‘set_time_limit(600)’ in the index.php file of the installer.



All my database tables are gone!



The matrix installer will delete ALL database tables in a given database if you select the ‘empty database’ checkbox. It does NOT discern between Matrix and non-Matrix tables at this time (in future this is a possibility). If you use the same database for other things, you will want to back up before installing, as the installer requires an empty database before commencing.



What are these 0000644 files?

(As in Bug Report)



This is sometimes caused by unzipping a tar.gz file on Windows. Please download the .zip version of the installer.



I can’t get PSpell to work properly

This is could be caused by a permission problem where you installed aspell. Read Bug Report for a solution.



Step 3 going blank?

Try checking the following thread for a solution. It seems like some people are having problems with fopen not working on their host.



Bug Report

I get an error trying to create the database tables
If you're using PostgreSQL, you need to install the plPgSQL language into your database using the following command:

    $ createlang plpgsql database_name


You may need to su to your postgres user in order to run this command.

Can't connect to Postgres
If you're running PostgreSQL, you need to either configure PostgreSQL to listen via TCP/IP (which is disabled by default on Fedora Core/Red Hat Enterprise Linux), or change "localhost" to "unix()" on the Database Details page of the Installer (the same page you select the database type).

Removed the XML_Parser-related info ("the Populate Database Tables step looks like it exploded" heading) from the Known Issues list, because it only applied to 3.1.0 RC1. The problem was that the code didn't take into account a change in XML_Parser 1.1.0 where the parser resource was automatically freed after parsing completed. It was fixed as bug #80 a week after RC1's release, so any XML_Parser version >= 1.0.1 can be used.

[quote]I get an error trying to create the database tables
If you're using PostgreSQL, you need to install the plPgSQL language into your database using the following command:

    $ createlang plpgsql database_name


You may need to su to your postgres user in order to run this command.[/quote]
Where do I run the createlang plpgsql database_name (obvisouly inserting my databse name) via shell access? Do I just run it in the root directory of the Shell access?

You may need to find the createlang binary (part of PostgreSQL). If you installed PostgreSQL as part of your distribution (e.g on Fedora Core or SuSE), then this binary may already be in your path and you can just issue this command anywhere.