- Installation Pre-Steps
- Advanced Options
- Database Options
- Context Configuration
- Pre-Installation Checks
- Post-Installation Summary
- See Also
This is the tutorial for the advanced distribution of MODx. It is recommended to only install this distribution if:
- You plan on renaming the manager/ or connectors/ directories, or move the core/ directory
- You have SSH access or can easily move/make writable directories on your server.
After you've downloaded MODx Revolution's advanced distribution, upload and extract it to your server. You should be left with two directories - core/ and setup/. From here, if you plan on moving the core/ directory, proceed to the next section. If you're not going to do so, or rename the config key, browse to setup/ in your browser and skip to the Advanced Options section of this document.
Renaming or Moving the Core
MODx Revolution allows you to rename and/or move the core/ directory to enhance your level of security. You can also move the core/ directory outside of the webroot to further secure your MODx installation.
Should you choose to rename or move the core, MODx recommends doing so before installing. Simply rename or move the core, and setup/ - at the beginning - will present you with a page asking for the new location of the core:
Enter into the textfield the absolute path to where you have moved the core directory. If MODx is able to find the core from there, you will proceed normally with the installation. If MODx still cannot find the directory from the path you specified, check if you have typed it correctly, that it is an absolute path, and that you've made the directory readable (and the core/cache/ file writable).
MODx might also ask you to make the setup/includes/core.config.php file writable. This is required to change the core path, and you should do so before proceeding.
Changing the Configuration Key
From here, MODx will ask you to choose a language. Do so at this time. MODx will then prompt you with a welcome page, and below will ask if you want to change the MODx Configuration Key. This allows you to run multiple sites with a shared core, as each individual site will need its own unique configuration key.
To change it, simply click the link the install tells you to change the config key, and you'll be presented with a textfield:
Specify a custom, unique config key and click next.
You will now be presented with some options for install, similar to the Basic Installation screen, but with two extra options at the bottom. 'New Installation' will be your only radio option available to check, which is what you want. Below that, you can choose to adjust the permissions for creating new files or folders in your MODx installation. The defaults should work fine, but if on a more restrictive server, you can change the folder/file perms to 0775/0664, respectively.
Below that, you will be presented with two checkbox options:
These will be grayed out during new installations. (During upgrades, it is recommended that you uncheck these as well.) Click 'Next' to proceed to the next step.
From here, you will get a form asking you for your database information:
Add in your database hostname, which is the URL at which your database is located. For most users, this will be 'localhost'. If you have your MySQL server on a different port, specify it like so: "my.database.com;port=3307", with the ;port= appending the IP/hostname.
Also, if you want, you can specify a different table prefix here. This tells MODx to prefix the tables with this value - this is useful should you want to make multiple MODx installations on one database.
When finished, click the 'Test database server connection and view collations' link. Should you have any errors, they will show below. If you do have errors, check to make sure your database username and password are correct. Also, if your user does not have access to create a database, you might need to do that manually.
Collations and Charsets
This will then popup another form for setting your database charset and collation:
For most users you can leave these values at what they are. However, if you need to change them, make sure the collation matches the charset. Click the 'Create or test selection of your database.' after you've finished.
Creating an Administrator User
This form will now present you with a few fields for setting up your administrator user. Specify a username that you want to be the administrator username.
MODx recommends not using 'admin', as this is a common administrator username and is often the first username hackers check.
From there, put in your email (or the email of your administrator) and specify a password. Click next when you're finished.
MODx will now present you with a detailed context installation screen. This is where you can configure the paths to your web context (the main context), as well as the directories for your connectors/ and manager/ folders. MODx recommends leaving the web/ context paths as they are, unless you have a special reason not to.
Renaming your manager/ and connectors/ directories, however, can add an extra level of security to your site. Simply change the paths and URLs in the textfields provided. Note: If you do change the directories, the directories above any of those paths must be writable to allow MODx to write the manager/ and/or connectors/ directories to them.
Make sure you change both the path and URL!
When done, click 'Next' to proceed.
MODx will then proceed with a list of checks to verify that your system is ready for installing. If any of these fail, you'll need to proceed with the directions that it suggests to make sure your environment meets the Server Requirements and has the correct directories writable.
Once you're ready, and all the checks pass, click 'Install' to proceed.
If you get a blank screen or cannot proceed after clicking 'Install', verify these steps: 1. Make sure the directories "/[root]", "/core/config", "/core/packages","/core/cache", and "/core/export" are writable. (root will be the actual directory you are installing to.) 2. Make sure your php.ini setting sets memory_limit to 128M, and max_execution_time to 120 3. Ensure that MODx can create the manager and connectors directories; this is done by making the parents of those directories writable (since you can change where they are installed) 4. Post a message in the Revolution forum regarding your issue. State your server setup and installation info, and we'll try and help you find a solution.
MODx will then let you know if any errors occurred during install, and prompt you to attempt reinstallation should any of those errors have occurred.
When install is successful, click 'Next' to proceed, and you'll be presented with one final option:
MODx recommends that you make sure to remove the setup/ directory after installing, to safeguard your site from anyone else trying to run setup on your site. You can do this by clicking the 'Check this to DELETE the setup directory from the filesystem.' checkbox.
When ready, click 'Login' to be presented with the Login form for the manager interface. You're finished!
- Basic Installation
- MODx Revolution on Debian
- Lighttpd Guide
- Problems with WAMPServer 2.0i
- Installation on a server running ModSecurity
- MODX and Suhosin
- Nginx Server Config
- Advanced Installation
- Git Installation
- Command Line Installation
- The Setup Config Xml File
- Troubleshooting Installation
- Successful Installation, Now What Do I Do?
- Using MODx Revolution from SVN