→ Test database server connection and view collations. Didn't work.#

Hello all!

I'm trying install MODx Evolution 1.0 but when it comes to → Test database server connection and view collations I can't do anything. When I press on it it's just adds # to the end of /install/index.php?action=connection.

My webhost setup is:

FreeBSD - 6.3
PHP - 5.2.9
MySQL - 5.0.45
Full info you can get here - http://ignatynikulin.com/info.php

My OS & browser:

Mac OS X 10.6.1
Firefox 3.5.2
Safari 4
Opera 10

Live preview of problem you can see here - http://ignatynikulin.com/install/index.php?action=connection

Thank you for your help!

BTW, there is no errors in server error logs

Firebug is giving me this error on your test page :-

window.addEvent is not a function
http://ignatynikulin.com/install/connection.js Line 1

why this should be however I don't know, maybe the js guys can throw some light on it.

Firebug is also showing that
http://ignatynikulin.com/manager/media/script/mootools/mootools.js
is 404.
Maybe your upload didn't complete?

Strange... I just unarchived tar.gz on server, so I didn't upload files by FTP.

BTW, /manager/media/script/mootools/mootools.js is there

The requested URL /manager/media/script/mootools/mootools.js was not found on this server.

Just to confirm what netProphET said

Quote from: ignaty at Sep 17, 2009, 01:41 PM

BTW, /manager/media/script/mootools/mootools.js is there

Well, it may be, but for some reason the web server is not seeing it at http://ignatynikulin.com/manager/media/script/mootools/mootools.js. Check permissions on the file and if that's not it, check to make sure the Apache config can serve js mime-types properly.

Strange, on this hosting just works fine MODx 0.9.6, FrogCMS, Wordpress...

Hello,
I had the same problem that had been solved by disabling ModSecurity during installation phase ... Good luck.

O.

For what it's worth, I would like to add that after digging around for hours, I solved this by providing "127.0.0.1" as the host name, instead of "localhost". I am not sure why this works, something to do with connecting via TCP/IP, as opposed to a local socket (or something).

It might be useful if the installation script returned some error report to the screen if no connection can be made. If you're looking at a screen that just does nothing, it's hard to determine where to look for the problem, as it could be just about anywhere