I wanted to do a similar thing a couple of weeks ago in Revo. I have a site with a few hundred HTML pages from an older site that needed to be imported into MODx. I was working on cleaning these pages up in Dreamweaver (making bulk sitewide changes using global regex find+replace), and afterwards I imported them into MODx using the handy Import HTML feature. Later after updating quite a few Resources, I realized I had missed a few things in my find+replace which would now need to be updated manually -- in hundreds of pages -- or done with DB queries or a script! It would have been nice to just export all site resources as plain HTML and finish that up in DW, then re-import and go from there.
I ended up making a list of changes I needed to make, and wrote a quick find + replace snippet to clean up the last few things, which I think saved me time in the end after all (TBH, DW is a pain to work with!
).
You could look at the issue from two points of view. On one hand, people may not want their content "stuck" in the MODx database without a way to actually get the content out later; even if it means leaving MODx tags like snippets, chunks, etc, and only exporting the resource’s content field, pagetitle and alias path (basically, the reverse of the Import HTML feature). Yes, it’s a crippled site without the ability to process tags, but there’s a facility to easily get stuff out once it’s in. On the other hand, you could say that the content is essentially useless without all the extra stuff. It certainly couldn’t be viewed without all that stuff!
MODX Staff
