We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 50845
    • 3 Posts
    After some searching I've discovered the "Failed" item in my install list is table prefixes, but this is utterly ridiculous since all permissions are available to the MySQL user that ModX is allocated to.
    The "Installation Summary" page is completely useless to find this (see picture). I had to dig around on the web to even find out what the error is.
    But, table prefix? Why is there a problem there? I've installed Wordpress on this site before - table prefix i just an option, not a server-side specific. And why are there no indications as to what has failed?
    After getting a Wordpress.org site hacked into a spambot, a senior developer has recommended this, but these errors are simply stupid and terminal. What next?
      • 28042 ☆ A M B ☆
      • 24,524 Posts
      Your site has an installation error log in core/cache/logs. It should have what you need to know.
        Studying MODX in the desert - http://sottwell.com
        Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
        Join the Slack Community - http://modx.org
        • 50845
        • 3 Posts
        core/cache/logs does not exist!
          • 10208 ☆ A M B ☆
          • 1,780 Posts
          Did you give the table prefix a value on the prior setup page? Something like "modx_" perhaps? As far as I know, this is essential when installing MODX and most certainly not an option.

          Do you have any MODX files showing up? If you haven't ever loaded up the site, there will be nothing in the core/cache folder at all.

          How did you do the installation? FTP of locally unpacked files or did you extract them on the server?

          Regardless, at this point I'd say start over. Delete the files that you have on the server entirely, grab a fresh copy of MODX.zip from modx.com (yes, go get a new zip file just in case), upload that to the server, extract it there, open the new extracted folder, copy all those files to the public_html folder and then re-run setup. Give your tables a prefix, make sure to name the database field with your full database name (username_databasename), db username, and db user password, set to utf8 and utf8_general_ci.

          This process is swift and clean normally, and the only issues I've ever really had is when I forget the full database name actually includes the username and underscore. Any other install errors or issues I recall most certainly were due to user error (i.e. not giving full permissions to the user).

          If you follow the instructions here closely and exactly, it should install in seconds without any failure messages. https://rtfm.modx.com/revolution/2.x/getting-started/installation/basic-installation
            Frogabog- MODX Websites in Portland Oregon
            "Do yourself a favor and get a copy of "MODX - The Official Guide" by Bob Ray. Read it.
            Having server issues? These guys have MODX Hosting perfected - SkyToaster
            • 28042 ☆ A M B ☆
            • 24,524 Posts
            Or use the installer script https://github.com/sottwell/installer
              Studying MODX in the desert - http://sottwell.com
              Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
              Join the Slack Community - http://modx.org
              • 50845
              • 3 Posts
              Quote from: sottwell at Jul 31, 2015, 06:06 AM
              Or use the installer script https://github.com/sottwell/installer

              I'll try that.
              In response to the earlier post - this is a brand new installation on the server, extracted on the server from the uploaded zip. modx_ is the table prefix. I have created the database and assigned a user to it, which is what I'm entering as the installation info. Everything works except this.
              It's pretty weird that several of the installation checks don't tell me what they are checking, including the one that says "Failed" - hence I had to scoop around the web to find out what actually has failed.
              My server is Linux/Apache hosted by eukhost.com
              The modx version is MODX Revolution 2.3.5-pl