We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 42569
    • 3 Posts
    I am trying to install EVO 1.0.9 on a server which has many Modx installations. I enter the database details and it successfully connects and verifies the database and collation, then when I get to the Pre-install validation step it ticks off everything OK but then comes up with the message

    "Creating connection to the database: Database connection failed!"

    I don't understand how it can validate it at one step and then not be able to connect at the next step. It has created the config.inc.php file but nothing is written to it. The permissions on the file were 644, so I changed thes and re-ran the installation, but still got the same result. What else should I be checking? I am at a complete loss now.

    Is it possible to do a manual install ... if so, can someone point in the directions of some instructions as I haven't been able to find any.

    My environment is this:

    Linux/Apache
    PHP: 5.3.3 (CGI/FastCGI )
    mySql: 5.1.67

    Help!!

    Jan
    • Mark Hamstra Reply #2, 11 years ago
      I think 1.0.9 might have some issues on PHP 5.3 - a new release 1.0.10 is in the works and should be released soon.
        Mark Hamstra • Developer spending his days working on Premium Extras and a MODX Site Dashboard with the ability to remotely upgrade MODX and extras to make the MODX world a little better.

        Tweet me @mark_hamstra, check my infrequent blog at markhamstra.com, my slightly more frequent ramblings at MODX.today or see code at Github.
        • 42569
        • 3 Posts
        Quote from: markh at Mar 31, 2013, 01:18 PM
        I think 1.0.9 might have some issues on PHP 5.3 - a new release 1.0.10 is in the works and should be released soon.

        Thanks Mark, on further investigation I discovered that there was an issue with the hosting set up, so I have now manged to resolve this. Only took me about two days to work it out sad

        Jan

        • This is fixed in 1.0.10
          http://tracker.modx.com/issues/9813