We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 34162
    • 1 Posts
    At first, server details:
    Server OS: Linux (yes, I know a bit generic but I know at least they run a x86_64 of it)
    Server Version: Apache (again, no idea what version, I'd say it _might_ be 2.2x)
    PHP Version: 5.2.10
    MySQL Version: 5.0.58
    Is pdo_mysql installed: Yes
    Browser: Mozilla Firefox 3.5.2
    

    The server is a shared hosting enviroment which has at least Mod_Security and Suhosin enabled. Tho they claim they have suPHP enabled, I doubt it as I still need to change the file permissions and the site won’t go into a HTTP 500 if a php_flag is set in .htaccess-file.

    On to the problem itself:
    When I try to install with correct database details, the installation will display an empty summary page (Basic package of 2.0.0-Beta-3) or just stay on the database connection information page.

    When trying to install with wrong/incomplete database details the following summary page gives the following results (this is from the advanced package):
        * Checking PHP for zlib dependency: OK!
        * Checking PHP version: OK!
        * Checking if memory limit is set to at least 32M: OK!
        * Checking if sessions are properly configured: OK!
        * Checking if core/cache directory exists: OK!
        * Checking if core/cache directory is writable: OK!
        * Checking if core/export directory exists: OK!
        * Checking if core/export directory is writable: OK!
        * Checking if core/packages directory exists: OK!
        * Checking if core/packages directory is writable: OK!
        * Checking if /{imagine-a-path-to-root-of-the-site-here}/ directory is writable: OK!
        * Checking if /{imagine-a-path-to-root-of-the-site-here}/manager/ directory is writable: OK!
        * Checking if /{imagine-a-path-to-root-of-the-site-here}/connectors/ directory is writable: OK!
        * Checking if core/config/config.inc.php exists and is writable: Failed!
          For new Linux/Unix installs, please create a blank file named config.inc.php in your MODx core config/ directory with permissions set to be writable by PHP.
        * Creating connection to the database: Database connection failed!
          Setup will attempt to create the database.
        * Checking if memory limit is set to at least 64M for zip extensions: OK!
    
      • 3749
      • 24,544 Posts
      Have you followed the suggestion on the screen to create an empty, writable core/config/contig.inc.php file?

      I’d also suggest setting the folders to 755 and the files (including config.inc.php) to 644 if suPHP is involved.

      Read this also:
      http://wiki.modxcms.com/index.php/What_is_mod_security_and_how_does_it_affect_me
        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
        • 34162
        • 1 Posts
        Setting all the directories to 755 and files to 644 just makes the installer halt at start suggesting to make the files/folders just chmod’d writable.
        As to the mod_security, all references to the mod_security options will only result in a HTTP 500-error.
          • 3749
          • 24,544 Posts
          Sounds like you were right that suPHP is not the problem.

          See if this helps: http://modxcms.com/forums/index.php?topic=20770.0
            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
            • 34162
            • 1 Posts
            The `suhosin.executor.disable_eval` is currently off and the `suhosin.executor.eval.whitelist/blacklist` is empty.
              • 2364
              • 73 Posts
              chmod does not solve all the problems. You always need to check chown rights.
              For example. If apache run as apache:apachegroup and you uploading data from user:usergroup (or user:ftpgroup) all will be working only with 777 (666 files) (all needed files and folders from here), unsecure but working. If data uploaded as user:apachegroup chmod must be 775 (664). And only if user=apache you can set 755 (644).
              AND after installations set new_file_permissions\new_folder_permissions system settings to right values. And for sure check rights for files\folders in ./core/cache/* directory.
                • 34162
                • 1 Posts
                Apache is running under it’s own user and group but the ftp-user is in a group of it’s own.
                Also the files created by apache (including php) are virtually un-deletable if i don’t use a php script to remove them, due to owner being different.

                Edit: After I had the site moved to the newer server, the installation went without a hitch.