Modx Revolution 2.0.0 RC3 Installation bug

Hello,

I ran into a weird bug with upgrading Modx Revolution 2.0 RC2 to RC3.

If the core/cache/setup directory is not write-able, the installation fails after you select the initial "upgrade" option.

What happens is that the loadSettings method of the modInstall class tries to load a non existent file.
The installer, in a previous step, tried to write core/cache/settings.cache.php, but silently failed.
Hence, the xPDO object is initialized with improper information, leading the installation to fail.

The solution would be to detect that this directory is not write-able, and prompt the user to make it so.

I hope this note saves someone else several hours of debugging!

Thanks.

First, why was anything in your core/cache/ directory not writable? That should always be writable.

The system already checks if core/cache/ is writable and assumes anything under it will be, since it is only ever written by the PHP process. We can definitely address this specific issue to prevent this situation. If you wouldn’t mind entering a bug report for it in our tracker at http://bugs.modxcms.com/, we’ll take care of it.

Hi Jason,

thanks for your quick reply. I’m not sure why the sub-directory wasn’t write-able. Strange, indeed.

I’ll open a bug for it.

Thanks!

Regards,
- Jay

I got the same a few minutes ago.
My first install of RC3.

Just made that directory writable (the cache dir) and
continued installation without problems.