When upgrading Modx 2.2.x, how do you run setup? It just shows the homepage.

Had a working ModX 2.2.2 pl. Downloaded 2.2.7. Uploaded (merged) files onto my server, making sure not to overwrite core/config/config.inc.php. As per the upgrade instructions at: http://rtfm.modx.com/display/revolution20/Upgrading+MODx. Next, navigated to the setup page. I get the site homepage instead. Where is setup? How does one "simply run" run the setup script, as per the upgrade instructions?

It should be by going to yourdomain.com/setup/

Check to make sure that you have a setup directory in your MODX directory, then navigate to yoursite.com/setup like Dan said.

I've clarified the docs a little bit to address that missing specific path.

Thanks for updating the docs, that's a very helpful clarification. Unfortunately this is still a no-go. Here are the steps I am following, maybe someone can shed some light on this:

1. Download the current version of Modx (2.2.7 Traditional) as a zip from here:
http://modx.com/download/

2. Upload zip to my webserver. SSH into the server and unzip the files.
FYI, site root is:

Files unzipped to:


3. Prepare to merge new files into existing Modx installation. I delete a few things that are unecessary, due to this being an upgrade:


4. Using the humble cp command, I merge new files from modx227/ into public_html/ like this:


5. Navigate to the setup page like so:
...This displays the site homepage
...This also displays the site homepage
...site homepage again
Nothing seems to work here.

6. Log in to the manager. Manager warns me that the setup directory should be removed for security. Manager also says I am running 2.2.2.

Any ideas?

In your server logs are these actually showing up as 404 errors? MODX will re-direct to the homepage for a 404 by default.

Are you sure that you copied the setup folder to your main site?

@Dan, sorry but I have no access to server logs. @sottwell, yes, setup directory is there. It has permissions of 755. the manager sees it.

For what it's worth: I worked around this issue by pulling the whole site/db down locally. doing the upgrade on my Mac (which actually has ditto -- whereas the hosting server does not) and the setup instructions worked like a charm. Moved the whole site and db back up to the hosting server, and all is now good. But it took a few very frustrating hours to arrive at this place. I am not looking forward to the next upgrade.

modx already has such awesome, mind-blowing package management features, it really seems kind of odd that there is no one-click upgrade mechanism in the manager. That would sure be a nice feature.

Going forward my (new) approach to Modx upgrades will be this:
1. http://rtfm.modx.com/display/revolution20/Upgrading+MODx
2. Make a local copy of the site. This is the copy you'll upgrade.
3. The ability to merge folders is vital. On a Mac, this is extremely tricky. So, make sure your local system has ditto and avoid using the Finder or cp or mv
4. Push site back up to the server.

Thanks everyone for your help.

Quote from: sottwell at Apr 27, 2013, 09:47 AM

Are you sure that you copied the setup folder to your main site?

As Susan pointed out your commands don't suggest that you copied over the setup folder. Make sure it is there

There is no way that the url domain.com/setup will return a 400 error if the setup directory is there, and its files are all readable.

Maybe it was file permissions, not the folder. Is there any reason why setup/index.php would be unreadable?

What if setup/index.php just fails or dies, what is the fallback? Perhaps it returns a 404 redirect to the modx engine?