Migrating to Revolution#

I've been looking at porting an existing site to 0.9.7 to give it a shakedown. The site has manager users, web users, MaxiGallery, Wayfinder, file uploads, custom snippets, Personalize, Ditto, SPForm, and multiple templates so it would give 0.9.7 a good ride. I have the latest 0.9.7 up and running but with no content.

Obviously, I can cut and paste everything into the new site, but I'm wondering if I can use some shortcuts (and possibly develop a conversion script).

The site_content table looks to be the same except for the addition of the class_key and context_key fields and the renaming and restructuring of the contentType/content_type field. There are also a few changes from int(1) to tinyint(1) and vice versa although I'm guessing those shouldn't be an issue.

Is it possible to dump the site content table and import it into the new site after editing the dump to drop contentType, add the three new fields, and modify the snippet and chunk calls appropriately? Or would that be a suicidal undertaking? If it's possible, what should go in the new fields?

Is the site_content table modular enough that it can be imported on its own, or does document creation modify other tables that would make this move unwise?

I imagine there would have to be some editing of the permissions numbers and the groups would have to be done from scratch.

Are there any other tables that could be imported this way (member_groups, membergroup_names, document_groups, documentgroup_names, site_templates, site_snippets, site_htmlsnippets?

1. I can't find the actual translate() function. Did I miss it, or is it in another file?

2. Is the script meant to work on the SQL dump file for the whole site, selected tables, or something else?

For some reason I missed the topic notification until now; sorry BobRay...

Quote from: BobRay at Jan 23, 2008, 09:23 AM

1. I can't find the actual translate() function. Did I miss it, or is it in another file?

translateSite() is the actual function that performs the translation. You can have it just create a log of the changes it would make, or run it to actually modify the database and/or file content you specify.

$parser->translate($content)

function getParser() {
        if (!is_object($this->parser) || !is_a($this->parser, 'modParser095')) {
            $this->parser= & $this->modx->getService('parser095', 'modParser095');
        }
        return $this->parser;
    }

{{chunk}} to [[$chunk]] or [!snippet!] to [[!snippet]].

I'm thinking separate migration packages for coming from previous releases (oooh, and/or other products maybe?) might be the way to go, rather than trying to stuff all that into the regular installer.

modParser095 is what you are looking for BobRay, as included by the modTranslate095 code you alluded to...