Step by step installation and upgrade instructions

Just ran the installation on my shared host server (redhat) and I got the same exact error asking me to create a blank config.inc.php file and make it writeable.

Looks like you actually do have to create the file. Thanks.

I have found that if I make the includes directory world-writable, then change it back after intsallation, the setup is able to create the file with no trouble.

I wonder if the upgrade procedure in this guide applies to ModX Revolution 2.0.0 beta 3 to beta 4 or beta 3 to beta 5 upgrade procedures?

No. Revolution is completely different.

Well, Susan, would it be now good time for instructions? I tried twice to upgrade from Revo 2.0.0. b3 to b4 and b5. NADA! The upgrade procedure would fail with a blank screen, after 30-40 seconds of spinning the wheel in my browser. I tried increasing the mem. limit for php to 128M, extending the exec. time to 300s and it’s the same thing all over. Now I am again uploading 55 Megs from my backup and marking another site maintenance record downtime.

It would also help to know if some kind of manual migration would be possible. Have the SQL tables been altered from b3 to b4? I have my own Revo compatible snipets and chunks, themes and lots of custom TVs.

Some good info here: http://svn.modxcms.com/docs/display/revolution/Fresh+Installation

If you are using FTP to upload the new version files, make sure your FTP program will overwrite existing files - they often don’t.

You might also find some help here: http://bobsguides.com/modx-installation-faq.html

Bob, I’m no expert, so please have a look:


and this also


755 * / (MODx root directory)
755 * /core/packages
755 * core/cache
755 * core/export
755 * /manager
755 * /connectors

When doing upgrade, should I do any trickery regarding this sugesstion:

Create an empty file: "/core/config/config.inc.php" and make it writable

?

Quote from: 100janovic at Jan 28, 2010, 02:25 PM

755 * / (MODx root directory)
755 * /core/packages
755 * core/cache
755 * core/export
755 * /manager
755 * /connectors

When doing upgrade, should I do any trickery regarding this sugesstion:

Create an empty file: "/core/config/config.inc.php" and make it writable

?

The permissions look good assuming that your host is running SuPHP or SuExec.

The time and memory limit should be OK, although it never hurts to increase them.

As for the config.inc.php file, it just needs to be writable.

Because Revo is in beta, there *are* usually changes to the database that occur during the setup process so updating manually can be a recipe for disaster.

It’s a good idea to make sure no one is logged in when you upgrade and to clear the cache (I usually delete everything in the core/cache dir. except for the index.php file). I also delete core/packages/core dir and core/packages/transport.core.php (if they are there). Then I clear the browser cache and cookies before running setup. Theoretically, none of that is really necessary, but it can’t hurt and it bypasses some potential problems.

As for the config.inc.php file, it just needs to be writable.

Bob,
Thanks for making the above step obvious to me - blank screen disappeared when I chmod’ed the core/config/config.inc.php to 755.

It should be noted in advance, possibly in the preparation check-up of the installation script, as this is of such IMPORTANCE when upgrading. Every time all the checks were OKed, and I still was presented with a blank screen.

Also, the Installer’s error handling logic should take this case into account. Just a blank screen is no good.

Quote from: 100janovic at Jan 29, 2010, 05:51 AM

As for the config.inc.php file, it just needs to be writable.

Bob,
Thanks for making the above step obvious to me - blank screen disappeared when I chmod’ed the core/config/config.inc.php to 755.

It should be noted in advance, possibly in the preparation check-up of the installation script, as this is of such IMPORTANCE when upgrading. Every time all the checks were OKed, and I still was presented with a blank screen.

Also, the Installer’s error handling logic should take this case into account. Just a blank screen is no good.

There is a check for that in the installer and it gives a warning on my system when I forget to make config.inc.php readable. I don’t know why it didn’t work for you but things like suPHP and suExec make it complicated on some servers.

It would be great if you could file it as a feature request using the Jira link at the top of this page. Be sure to include all the details about your server configuration and MySQL/PHP/Browser versions.