Upgrading beta products 3->4

OK reading the doco on this:
http://svn.modxcms.com/docs/display/revolution/Fresh+Installation

Is again suitably vague.

I am not using an SVN version, just doing this by FTP / command prompt. Upgrading from b3 to b4.

Do I just upload/over write everything there? I would think there are some config files I shouldn’t overwrite but is it just the config.core.php or some others as well?

What about core/config.inc.php ?

A brief summary of the upgrade process would be great, concerned I could stuff everything up by overwriting the wrong file or not overwriting the necessary files.

Thanks.

The config files are not part of the distribution (with the exception of the config.core.php files in each of the main directories when using the Traditional package, which is not a problem to overwrite). You are free to just upload and overwrite existing files from the package; though be careful in OS X where folders (not just files) are completely replaced rather than augmented if they already exist.

So, for an installation on a webhost would the steps be as followed?

1. Upload zip folder to web server
2. Unzip folder to existing directory
3. Done? or Run Setup?

I wish I had read this post yesterday before upgrading. I somehow managed to mess up the upgrade and my beta-3 install and ended up having to do a clean install and manually transfer everything over from the database. It took me about 4-5 hours to get it done.

I do love the beta-4 improvements. Especially the tabbed interface for the resource browser (Resources / Elements / Files) - it’s night and day better than the previous sliding-windows interface.

mattcdavis1 - that’s right as far as I understand it however you would also have to keep your config.core.php files intact to give the core location.

OK done all that.

Goto setup, select upgrade, it runs all its checks and I get all green ticks and proceed. Then I simply get a white screen with this on it:

Fatal error: Call to a member function execute() on a non-object in /usr/local/modxrevolution/xpdo/om/mysql/xpdomanager.class.php on line 159

Any ideas/suggestions?

All admins logged out, browser cache cleared prior to trying upgrade.

No errors in cache/logs/error.log

I cannot reproduce this error at all scarfy96; we’ll need environment information including MySQL client API and server version, PHP version, platform, etc.

It’s possible that one or more files was corrupted in transfer or that your unzip utility didn’t overwrite existing files.

Environ variables:

php v 5.2.0-8
linux
apache 2.0
mysql 5.0.32
safe mode off
memory_limit 120M
max_execution_time 120

I guess I can re-transfer the files and try again.

php v 5.2.0-8 is likely the problem; I suggest getting a much more recent version of php 5.2 (I recommend 5.2.6 or higher) as there were a lot of problems with PDO in early 5.2 releases (not to mention all the security issues and other bugs that have been fixed since then).

I’ll request with the ISP but it isn’t my call there.

Thanks.

Quote from: scarfy96 at Oct 27, 2009, 05:24 PM

I’ll request with the ISP but it isn’t my call there.

Thanks.

You might as well ask for a MySQL upgrade while you’re at it (as long as you don’t get 5.0.51 !)

I see XAMPP now includes 5.1.37, so yours is fairly out of date.