We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 6136
    • 2 Posts
    I have a number of other PHP scripts installed on my domain (project management and CRM). There is an existing install.php file in the root directory, and I don’t want to mess any of my existing scripts, as it took me a while to get them running properly.

    Please advise how to deal with this. Is it as simple as renaming the existing install.php file?

    Thanks!!
      • 28042 ☆ A M B ☆
      • 24,524 Posts
      The MODx installation files are in a separate "install" folder, install/index.php; there is no install.php file for MODx; so there should be no conflict.

      Aside from that, it is very dangerous to leave install scripts laying around on your server.
        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
        • 6136
        • 2 Posts
        Now I know why I am not a programmer. I meant to say a INDEX.PHP file not a install.php file.

        So, I guess my question remains, will I have a problem once MODx is installed?

        Sorry for the confusion, and thanks for the quick reply.
          • 3749
          • 24,544 Posts
          You do have a problem. MODx definitely needs its own index.php file and your previous site will break when you install MODx. I think you’ll also be unhappy in the long run having your current files intermingled with the MODx files. If you knew MODx well, you’d know which were which, but it’s still a risk and I wouldn’t do it.

          There are a few of possible solutions. One is to just rename all the current files by putting ".bak" on the end of the file names. That way they’ll still be there if you want to revert, although they’d still be cluttering up the site. Another way is to put the MODx site in a subdirectory. It’s definitly doable but with some goofing around with rewrite rules and aliases to make it work the way you want. If it’s your first MODx install, it will add an extra layer of difficulties.

          My preference would be for a third way. I’d download the current site to your local machine as a backup, delete everything on the remote, and install MODx there. That way you could still revert by deleting the MODx site and uploading the old one.

          Bob
            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
            • 22303 MODX Staff
            • 10,725 Posts
            You can rename the MODx file to another name like modx.php or something, then change your rewrite rules appropriately (if employing the use of Friendly URLs). The main problem then will be accessing it.