Attempting an upgrade from Evo 1.0.6 to Revo 2.2.6

Hi there,

Is this still the definitive resource for upgrading from Evo?
http://rtfm.modx.com/display/revolution20/Upgrading+from+MODx+Evolution

It seems a little out-of-date.

I realise I'll need to re-code my theme, and DocManager 1.1 will break.

Does any one have any other resources or advice to add?

Many thanks in advance.

You'll need to change all MODx tags to the Revo tags, such as [*content*] to [[*content]].

Plugins, anything other than the simplest snippets, and modules will definitely not work. You'll have to find the Revo equivalents, such as the Revo version of Wayfinder, getResources instead of Ditto, and FormIt instead of eForm.

Quote from: sottwell at Mar 05, 2013, 06:52 AM

You'll need to change all MODx tags to the Revo tags, such as [*content*] to [[*content]].

Plugins, anything other than the simplest snippets, and modules will definitely not work. You'll have to find the Revo equivalents, such as the Revo version of Wayfinder, getResources instead of Ditto, and FormIt instead of eForm.

Thanks Susan,

That's what I was expecting after reading Bob's Guide on Migrating to Revo http://bobsguides.com/migrating-revolution.html

Then I found some information on Provisioner http://modx.com/learn/modx-college/migrating-from-evo-to-revo/

However, since you're considered the expert around here and my Evo site only has about 25 Documents, I think I'll go for a straight upgrade using Revo's setup script and do a find and replace on all content.

Plugins installed: (most of these I realise we can do without in Revo)
Manager and Admin

• Forgot Manager Login 1.1.2
• ManagerManager 0.3.9
• Quick Manager+ 1.5.5
• TinyMCE Rich Text Editor 3.3.9.2
• TransAlias 1.0.1

Search

• Search Highlight (4) - 1.5

OK, some progress.

I've created a copy of my modx evo site files in a subfolder revo/ and duplicated it's mysql db by restoring a backup into a blank schema. I also edited the duplicat config.inc.php file to use the new db and edited my .htaccess file in the evo site root to pass through requests to that new folder:


The duplicate site's homepage shows up at mydomain.com/revo/ and I am able to make changes to the content from mydomain.com/revo/manager/ without affecting the original site. All fine so far.

Now I've uploaded all of the files from the modx Revo package without replacing existing Evo files or manager/ directory and run mydomain.com/revo/setup/ choosing the Upgrade option. I get a 500 error:


Where am I going wrong? Do I need to do a tighter merge of the new ad old packages over FTP?

- edit -

The core of Revo is really, really different from that of Evo. You won't be able to simply "upgrade" like that; it cannot use anything from an Evo installation. Any upgrade installation expects to find its config.inc.php file in a specific location, and in the case of Revo that is not manager/includes/ as it is with Evo. An Evo config.inc.php file won't work, anyway.

The /revo/ subdirectory should have only a new Revo installation. You'll then be able to simply copy/paste your templates (changing all the MODx tags from Evo to Revo), then copy/paste your resources and chunks, and any custom snippets. The standard MODx snippets will need to be installed using Package Manager.

Revo comes with nothing extra, you'll need to install the extras you want using the Package Manager (in the System menu). I'd start out with Wayfinder, getResources (replaces Ditto), getPage (to provide paging for getResources or any other listing snippet like that), TinyMCE, FormIt (quite different from eForm, it does not generate the form but works on a regular HTML form in your content) and SimpleSearch. I also always recommend MIGx, for the most amazingly useful customized TVs, as I can't imagine creating any site without it, but that's just my opinion

You'll need to spend time with the rtfm documentation pages for these, as in most cases they work somewhat differently than their Evo counterparts.

You can, of course, copy all of your original site's supporting files such as images, .css and .js files to the same locations in the revo installation. In all of my sites these are put in the assets folder, just as they are for Evo sites, but they can go anywhere you like, as long as the links to them in your HTML are correct.

Provisioner may very well work in your case. I've never been able to get it to work at all, but that's just my relatively brief experience with it. http://www.scribd.com/doc/55906476/MODx-Provisioner-User-Guide-v1-9-beta



The Revo analog to ManagerManager is known as "Form Customization", and for the most part (at least for resource editing and creation) is built-in.
http://rtfm.modx.com/display/revolution20/Customizing+the+Manager
http://rtfm.modx.com/display/revolution20/Adding+Custom+Fields+to+Manager+Forms

There is no equivalent for QuickManager; the closest is called QuickBar and has a similar menu bar that opens the proper page in the Manager for editing or creating resources. No fancy AJAX-based overlay editing, though.

You might want to go over this series of articles http://codingpad.maryspad.com/2010/08/18/modx-revolution-for-beginners-part-1-introduction/

Wow, ok I'm going to try with a clean install of Revo in my subfolder and see where I get from there.

Thanks Susan for the long and detailed response.

I'm good at that... push the right buttons and get more than you wanted to know