Installation Javascript Error

Hi all,

I’m attempting to install MODx 1.0.2. When I get to the screen to test my database connection, before doing anything, I received a Javascript error on the connection.js file and am unable to test my connection, or continue with the installation.

I get this error with IE8 and also Firefox 3.5.5.

I’m running PHP 4.4.9, MySQL 4.1.22. and Apache 1.3.41


Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; Win64; x64; Trident/4.0; .NET CLR 2.0.50727; SLCC1; Media Center PC 5.1; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Timestamp: Thu, 19 Nov 2009 22:19:58 UTC

Message: Object doesn’t support this property or method
Line: 1
Char: 1
Code: 0
URI: http://www.fullcirclecycles.com/install/connection.js

After poking around a bit, I realize that the installation is trying to access:

/manager/media/script/mootools/mootools.js

However, when I try to directly access this file, I receive:

HTTP Status 404 - /manager/media/script/mootools/mootools.js

type Status report

message /manager/media/script/mootools/mootools.js

description The requested resource (/manager/media/script/mootools/mootools.js) is not available.
Apache Tomcat/5.5.25


I have copied the ’manager’ directory to the root directory of the web server.

The other odd thing I’ve realized is that I cannot access ANYTHING in a directory called ’manager’ on this webserver. If I rename the directory to something else, I can access the files within it. If I name it back to ’manager’ I get the error above.

Is there a setting that I could be missing that does not allow a ’manager’ directory on this webserver? The website I’m developing is hosted with "Host For Web."

Has anyone else had this issue?

Thanks,
Randall

The permissions are also open on the ’manager’ directory.

Apache Tomcat/5.5.25

/manager is reserved dir in Tomcat server.

You can ask your host to change the default Tomcat admin path.

Excellent timing, Zi. I just found another thread that mentioned this problem in 0.9.2.2 after the installation was complete. This was something I also encountered when trying to install an older version.

Obviously, this is still an issue with running Apache in 1.0.2. I read in the same post that a user installed MODx something other than their root directory, but this isn’t exactly the option I want to take.

Any other thoughts?

Thanks,
Randall

Unfortunately, I havent came across a solution to this.

Does ur client run any java app on the server?

If not, you can ask your host for the ideas on bypassing this. OR turning off the tomcat.

Just thinking out loud. No server admin here

What I ended up doing was searching all instances of:

’manager/

"manager/

/manager/

and replaced them with management. With the right editor it doesn’t take too much time. There were a couple of other small items that needed to be ironed out after that, but I’ve gotten it installed and been able to log in to the administrator and also see the default index.php page the installation generates.

Thanks for the response, Zi.

Thats a nice alternative, provided u will have to do it with every upgrade. But, well, it works you know.

Glad you got it working.