We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 32699 ☆ A M B ☆
    • 427 Posts
    Quote from: OpenGeek at Dec 20, 2009, 09:23 AM

    Ignore mhash/mcrypt, I don’t believe these are required for Revo; these were leftover requirements from Evo.

    mhash and mcrypt are used by assorted PHP applications:

    phpMyAdmin uses mcrypt for example.

    You are running Centos -- are you by any chance running SELinux? What is the policy for httpd and mysql?

    If the permissions needed changed and were updated on the fly -- this would explain the "not work" and "then works" weirdness you experienced.

    I have mine set for enforced, and not allowed in user directories, etc...
      Get your copy of MODX Revolution Building the Web Your Way http://www.sanitypress.com/books/modx-revolution-building-the-web-your-way.html

      Check out my MODX || xPDO resources here: http://www.shawnwilkerson.com
      • 14015
      • 1 Posts
      Hi, first big thanks to the team who created this masterpiece! I am new to revolution, but very impressed with ModX evolution...
      I am trying to do a clean install of this beta version on two different server installations, and I am experiencing the same problems; Cannot connect to the database, and both pulldowns (encoding) show only a single option. Prior to the installation I created an empty DB with an user account (fully authorized) on both systems.

      Configurations:
      1) Linux, PHP Version 5.2.3, MySQL - 4.1.20, Apache/2.0.54 (Fedora)
      2) OSx, PHP Version 5.3.0, MySQL - 5.1.38, Apache/2.2.13 (Unix)

      regards, Jeroen
        • 18097
        • 33 Posts
        I have the same issue.

        Brand new server setup, never had any website or database installed on it before, and I get the same screen. I’ve attached an image for you to see what I am seeing.

        I would be very grateful to resolve this soon.

        Daniel
          • 30939
          • 27 Posts
          I have the same issue, too (fresh install):
          In DIV ID: modx-db-step2-msg:

          → Create or test selection of your database.
          Checking database:Could not connect to the mysql server.

          Previously I had build the DB with phpMyAdmin manually. Charset/Collation utf8_general_ci

          LAMP: Apache2, PHP 5.2.0, mysql 5.0.32, pdo_mysql, zlib,
          magic_quotes_gpc:off, execution time: 120, memory limit: 128M,
          safe_mode: off, Register_globals: off
          Firefox 3.5.6
            • 22303 MODX Staff
            • 10,725 Posts
            You’ll need to provide both your MySQL server and MySQL client API versions for anyone to assist further, but I can tell you that PHP 5.2.0 is full of bugs that could affect PDO, as is 5.2.3.

            I don’t understand why people run such old software? IMO, you should be running at least 5.2.6 at minimum, and I try to keep up with latest so I get important bug fixes in PHP as quickly as possible.
              • 30939
              • 27 Posts
              Well, at home-office I develop on an local Debian 4 Etch.
              In knowledge of this "old" system, I sat up a new fresh Debain 5 Lenny.
              During the installation of MODx Rev Beta 5 the setup said, the MySQL-Client 5.0.51a is buggy.
              But in the stable branch of Debian Lenny the highest MySQL-Client is 5.0.51a-24.
              http://packages.debian.org/stable/mysql-client
              Serveral times I try to install an other MySQL-Client (backports and testing branches, too) -
              without success.
              Now, I change my development-system to ubuntu (with the same package-management "aptitude" as
              Debian). Now, ubuntu contains "up to date" packages - so as MySQL-Client, too. The install of
              Revolution was without problems and now I can try the new MODx.
                • 32699 ☆ A M B ☆
                • 427 Posts
                Quote from: Jeronemo at Dec 27, 2009, 10:19 AM

                Configurations:
                1) Linux, PHP Version 5.2.3, MySQL - 4.1.20, Apache/2.0.54 (Fedora)

                Running F12 here.

                Try going to http://localhost/ and see if it returns a 404 or something.

                I’m not looking at apache as much as I am SELinux.

                Post your SELinux Profiles for httpd and myqld
                  Get your copy of MODX Revolution Building the Web Your Way http://www.sanitypress.com/books/modx-revolution-building-the-web-your-way.html

                  Check out my MODX || xPDO resources here: http://www.shawnwilkerson.com
                  • 9207 ☆ A M B ☆
                  • 2,475 Posts
                  I’m still unable to install this on my own server. I did successfully install it on my shared account with Bluehost. Anything else that’s worth trying? Is it something where I should dig into the JIRA issues myself? (hey I’m willing)
                    • 3749
                    • 24,544 Posts
                    Quote from: Everett at Dec 21, 2009, 01:09 AM

                    I just re-tried this with display_errors=On and with error_reporting = E_ALL | E_STRICT
                    I didn’t see any errors, and there was nothing in the logs other than the favicon.ico missing.

                    Right after I click "Next" from the install contexts page, I end up on a white screen. I’ll try the various PHP configurations and see if I can’t make that work.

                    Everett, that really sounds like either your memory_limit is too low, or you have a corrupted file somewhere.

                    If it can create one table, it ought to be able to create all of them since it’s just repeating the same process.
                      Did I help you? Buy me a beer
                      Get my Book: MODX:The Official Guide
                      MODX info for everyone: http://bobsguides.com/modx.html
                      My MODX Extras
                      Bob's Guides is now hosted at A2 MODX Hosting
                      • 14915
                      • 43 Posts
                      Hi,

                      I had the same problem. I first installed Modx on one computer, and then tried to install it using the same set of files (minus the main config file) on another. I think that some temporary files are generated during the installation process, and this messes up subsequent installations.

                      I hope that helps someone else.

                      - Jay