Skip to content
General Revolution Evolution Add-ons International
Login | Register | MODX.com
MODX Open Source Content Management System, Framework, Platform and More.
Find a Partner | Hosts + SaaS | Jobs | Donate
  • RegisterSign Up with the MODX Community
  • LoginUse Your MODX.com Account
  • MODX Community Forums
  • Evolution
  • Evo Release Support
  • Evolution 1.0.0
  •  
  • → Test database server connection and view collations. Didn't work.#

  • 12693
    3

    ignaty Reply #1, 2 years, 8 months ago

    Reply
    • Link to this post#1
    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


  • 26903
    1,303
    Use MODx, or the cat gets it!

    shamblett Reply #2, 2 years, 8 months ago

    Reply
    • Link to this post#2
    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.




  • 21257
    687
    Mike Schell
    Senior Developer, MODX Complete Team
    MODX, LLC

    Email: support@modx.com
    GitHub: https://github.com/netProphET/
    Twitter: @mkschell
    Web: modx.com Tw: @modxcms FB: modxcms

    netProphET - MODX Complete Team Reply #3, 2 years, 8 months ago

    Reply
    • Link to this post#3
    Firebug is also showing that
    http://ignatynikulin.com/manager/media/script/mootools/mootools.js
    is 404.
    Maybe your upload didn't complete?


  • 12693
    3

    ignaty Reply #4, 2 years, 8 months ago

    Reply
    • Link to this post#4
    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


  • 4310
    2,276
    Snippets : eForm 1.4.4.7 with SMTP & PMS's security fixes | PHC Results | EasyNewsletter from CSV

    Wiki Articles : Custom DB table to placeholders | Manager Locked Out?

    Websites : Work - U.K. based MODx development  |  Hobby - Free interactive education resources for teaching 4 - 11 year olds

    Hosting : One Smart Host - Professional MODx hosting 

    bunk58 Reply #5, 2 years, 8 months ago

    Reply
    • Link to this post#5
    The requested URL /manager/media/script/mootools/mootools.js was not found on this server.
    Just to confirm what netProphET said


  • 22303
    9,764
    - MODX Chief Architect

    Jason Coward | MODX Chief Architect

    jasoncoward.com | @drumshaman

    opengeek Reply #6, 2 years, 8 months ago

    Reply
    • Link to this post#6
    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.


  • 12693
    3

    ignaty Reply #7, 2 years, 8 months ago

    Reply
    • Link to this post#7
    Strange, on this hosting just works fine MODx 0.9.6, FrogCMS, Wordpress...


  • 22059
    26

    oho Reply #8, 2 years, 4 months ago

    Reply
    • Link to this post#8
    Hello,
    I had the same problem that had been solved by disabling ModSecurity during installation phase ... Good luck.

    O.


  • 36875
    5

    DutchIris Reply #9, 2 years, 3 months ago

    Reply
    • Link to this post#9
    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





Actions

Login to Post

Other Support Options

To file a bug or make a feature request visit our issue tracker, or you can also purchase commercial support.

Love MODX?

If you build sites for a living with MODX or just love using it, why not give back?

Information

Posted in this thread:
bunk58, drdoolittle, ignaty, netProphET, oho, opengeek, shamblett

 
Back to Top

MODX Global HQ

1333 N Stemmons Fwy, Ste 110
Dallas, TX 75207
United States

+1 (469) 777-MODX (6639)

The MODX Company

  • Contact
  • Media Center
  • Careers at MODX
  • Wall of Fame
  • The MODX Blog

Sponsors

SoftLayer Firehost: Secure Cloud Hosting

Stay Connected

Read our previous email newsletters.

Twitter Facebook Google+ LinkedIn github Feeds

Privacy Policy | Terms of Service | Pixels by AKTA Web Studio© 2005-2012 MODX. All rights reserved. Trademark Policy