[quote]Thank you. Before I get in further over my head, here’s what I am getting…
Warning: require_once(…/includes/database.php) [function.require-once]: failed to open stream: No such file or directory in /home/.fay/user/sub.domain.com/installation/install2.php on line 19
Fatal error: require_once() [function.require]: Failed opening required ‘…/includes/database.php’ (include_path=’.:/usr/local/php5/lib/php:/usr/local/lib/php’) in /home/.fay/usere/sub.domain.com/installation/install2.php on line 19[/quote]
Both of those errors are the result of the same problem: Your install2.php script cannot find the database.php file.
In the first instance it can’t find it at “…/includes/database.php”, and in the second case it could not find it in the “default” includes directory of your PHP installation. That said, let’s troubleshoot this step by step.
First, what is the actual directory referred to in the first warning message? Since “install2.php” runs from the Joomla! installation directory (which is “/home/.fay/user/sub.domain.com/installation/”), the directory the code is looking to find the file in is “/home/.fay/user/sub.domain.com/includes” (it is trying to find the file “/home/.fay/user/sub.domain.com/includes/database.php”)
That said, you can safely eliminate any concern about the dataglob being at fault or relevant to the error. Stating the path with the dataglob is just a characteristic of the PHP error reporting routine, and the code should work with, or without, the dataglob in the path. For the purposes of debugging this issue, “/home/.fay/user/sub.domain.com/includes” is functionally the same as “/home/user/sub.domain.com/includes”.
Do you have a file “database.php” in “/home/user/sub.domain.com/includes/” ? If you do not, then clearly that is the problem (an incomplete installation). If that file is missing (and you didn’t delete it!) then I’d be suspicious of the entire installation - if one file is missing many more are also likely to be missing.
Such a problem is, actually, pretty common with Joomla! installations in which the core files were extracted on one computer ant then uploaded to the server via FTP. Joomla! has a lot of files, and very often, for one reason or another, some will not be properly transferred in that massive upload of hundreds of files.
I’ve seen those developing using an instance of Joomla! installed on their own machine, and then trying to upload the “launch ready” site onto their production server via FTP running into this pretty often. To avoid this, I think they should install the Joomla! core, and extensions “on the server”, and just export the “staging” database from their “dev” system for future import to the “live site”.
This is why I always install Joomla! in the shell by using wget and tar rather than downloading the package to my computer, extracting it, and trying to upload it to the server with FTP.
At any rate, your next troubleshooting step is to locate that database.php file before doing anything else - if it is not there, you need to put it there and proceed. Just be aware though, as I said above, if you didn’t delete that file but it is not where it is supposed to be, I think you should treat your whole installation as “suspect”.