Mass Upgrading

Hello. Let me first say thank you to all the MODx Developers, Designers and Contributers. You truly have created something I’ve longed to have in my possession.

Ok, I need to ask for or create a PHP script (or Perl) that will mass Upgrade locations of MODx installs. The reason for this is I am a designer/ hoster and my plans will include most clients having MODx, and upgrading 40 security - critical websites would be beyond tedious.

As you read this you can probably already gather the importance of this concept, and how valuable it would be.
Also, I think this would be a first on the CMS scene, I haven’t seen / heard this before.

Thanks for your time any help/ concepts/ POC would be great.

If I develop this I will certainly make it available to the community.

The problem is any databases changes that occurred between the two versions (current and new). The only way I know of to upgrade the database is to run the installer. However these changes have to be stored in a file somewhere, so it is executed during the install.

Andy

@elitesean:

One of the new features coming in the next major release is that of using a single core installation to power any number of MODx configurations. Each configuration will then define a database and paths/URLs for each context of the site (i.e. back-end, front-end, etc.).

Another feature on the roadmap is one for packaging up data along with related file resources and script dependencies. This can be used to package up a set of changes to be deployed in the core (i.e. core upgrade), a specific site or site context, or to several sites.

If you are interested in contributing to on-going core development in these regards, to help improve and speed up the process of getting these features completed, tested, and stabilized for release, we’d love to have your help...