Hiya peeps! Great forum, great program, great to be onboard with such a fine open source initiative.

I am trying to install a fresh copy of XOOPS v2.0.10 onto my local webserver for testing a new site I'm developing for a local community group. My test server is a vanilla install of Apache2Triad v1.4.1 using following versions:

Apache version 2.0.53
MySQL version 4.0.24
PostgreSQL version 8.0.0
Openssl version 0.9.7e
Slimftpd version 3.16
Xmail version 1.21
Perl version 5.8.6
PHP version 4.3.11
Python version 2.3.4


FWIW I would have preferred to use the XSAS server but it will not give me an option of installing to a different drive letter (W is already in use on my local box) and nobody has responded to my cry for help over on the XSAS forum at sourceforge. But anyhoo, on to the problem.....

I've made all the necessary folders writable and give full access permissions to the database user name account in MySQL panel.


Install confirms:

Checking file and directory permissions...
Directory uploads/ is writable.
Directory cache/ is writable.
Directory templates_c/ is writable.
File mainfile.php is writable.
No errors detected.


Heres's my setup config:

Database mysql
Database Hostname localhost
Database Username (private)
Database Password (private)
Database Name xoops
Table Prefix xoops
Use persistent connection? NO
XOOPS Physical Path D:/WebServer/htdocs/xoops
XOOPS Virtual Path http://localhost/xoops


Two windows later I am getting this error message:

Saving configuration data..
Could not write into mainfile.php. Please check the file permission and try again.


I've read and re-read the installation instructions and followed the very excellent wink tutorial over at http://www.warpigw2.com/ (big kudos to the bloke who prepared this bunch of flash tutorials) but can't for the life of me figure out what I am doing wrong here.

I read some mumblings in another thread here that somebody was getting this same error after upgrading to Apache2.... is there anything I might need to enable in there which is not enabled in vanilla Apache2Triad setup? Or something I can do to check MySQL has correct permissions to edit the file?

I'm running Win2003 here (hacked to workstation), using Firefox browser to run the install, set my NTFS folder permissions to allow full file access, all my server bits are listening on correct ports and enabled in firewall (Outpost).

Hope that was enough info So, can any of you XOOPS guru's shed some light please?

Cheers m'dears

Z

Please Note: I am only trying to run this on local server for now - it might be a month or so before I get client approval and have it on a web hosted server - so I'm only concerned with this end of things for now and getting this XOOPS test server operational.

[edit: typos]

[re-edit: changed thread title to update status]

I could quite easily walk you through it on a W2K3 box using IIS 6. Do you have to use XSAS?

Quote:

Thanks for the offer but I am just not willing to enable stuff like IIS stuff on this box. I'm happy to try other open source webserver options if it turns out that is where the problem lies, but I'm not touching anything "microsoft" with a 20 foot pole.

Maybe I over-explained myself before... what I mean is that I wanted to use XSAS but wasn't able to because of the "Drive W" default setting, and the only other "all-in-one" local websserver solution I was able to find at short notice is Apache2Triad, so this is what I am using....

http://apache2triad.net/

Can somebody suggest a list of possible reasons why mainfile.php cannot be written to other than the obvious ones which I have ruled out already like "read only" file and "NTFS security permissions" ?

Cheers
Z

OK I dumped the Apache2Triad. Took me nearly an hour to manually clean the POS out of the registry so I won't be giving that any rave reviews at any time... ay caramba!

I've installed WAMP5 1.4.3 server now (with PHP downgraded to 4.3.11 and Apache 1.3.33) and got a few steps further down the installation path, but still not all the way yet. It writes to the mainfile.php OK now and everything is in the correct place in the next few install windows, but now I get to this one....

Check Database

Could not connect to the database server.
Please check the database server and its configuration.

Can't find anything in the tutes or docs to explain this error and it's way past my bedtime now, so I'll be back to check in manana.

Anyone can help please?

Cheers
Z

If the installation procedure cannot connect to the database it is likely to be because database username and password mismatch or the database server is not running. Can you connect through phpmyadmin or similar? (usually enclosed in xAMPP packages)

Quote:
Thanks for your reply Mithrandir, I went thru all the steps of restarting my web/sql servers and rechecking permissions and after a day of driving myself nuts trying to read sql documentation and find out what I was doing wrong with setting my db permissions, it turned out to be the simplest thing of all.....

I needed to set up XOOPS from in my local webserver environment using the username "root" and with "NO password". Tres bizarre, but that's what did the trick.

I've no idea why it would not install using the "new user" account I set up in phpMyAdmin (which had global permissions to everything but my sodding bank account ) but we're running now.

Wow you guys made this CMS a piece of cake to customise. Can't wait to impress my client with what this puppy can do.

Cheers muchly
Z