Copying MODX Revolution for students

Hi,

previously we worked with Evolution, where the teacher would prepare a "student-site" and I would script copying that site for different students. Hereby I replaced some values in the SQL-export and config files so that all the installations have their own identifiers and logins.

Now the teacher wants to upgrade to Revolution and I'm trying to do the same.
I thought coping the "template"-site, change values of MySQL-configuration, paths/url's and site_id, site_sessionname in the different config.inc.php (root, core, manager, connectors) and creating a specific database for that site would be enough. I was wrong ;-)

So my question is, how do I make a copy of a MODX Rev site to another site, which files and what in the database should I change?

Using contexts in one site isn't a solution.

Thanks in advance and best regards,
Peter

The easiest way is to use Vapor to make a package of the basic site, then every time you make a new installation immediately install the Vapor package. I'm working on building up a library of various basic sites, such as a bare-bones site with my preferred extras and configuration settings already done, one with Login, one with multi-language, one with a gallery, etc.

Hi Sottwell,

thanks for the fast response

Problem with this method is that I have to login in each site and I would like to script it without user intervention because there are about 50-100 sites which I should roll out.
I could off course ask the teacher to do that part.

Is there also a more difficult way? ;-)

Best regards,
Peter

@kruppa, you haven't specified what exact issue you faced! Check this might help.

yes pls do give us more info on what the problem is.

You have 50-100 existing sites which need to be ported over?

Or you need a Revo template which is suitable to be used to make like 50-100 different sites with different name and so on?

Sorry for my confusion, I will get out of the way now ;-)

Hi all,

it isn't a migration or upgrade in the exact meaning of the word, every year we roll out new sites for the new students so they can practise working with a CMS.
Therefore the teacher configures a template-site (simple install configured to his needs) which I have to copy to other subdirectories in the site.
The site would be for example http://modxrstudents.example.com/template

The way I did it doesn't work, it gives an error 503 in the page and 404 on the windows title for the new sites and the manager prompt a login-box but authentication won't work.
The sites would be for example http://modxrstudents.example.com/2014892 http://modxrstudents.example.com/2014893 http://modxrstudents.example.com/2014894 http://modxrstudents.example.com/2014895

I thought I'd ask the procedure in here. For MODX Evolution I found and used it, worked without a problem.
Troubleshooting the errors will probably clear out some things.

Thanks and best regards,
Peter

I understood what you are doing from your first post. And indeed you need to check your logs. What you are doing is still considered a migration which can be done by the steps provided in the link above. You just need to script it.

@sottwell:

I'm working on building up a library of various basic sites, such as a bare-bones site with my preferred extras and configuration settings already done, one with Login, one with multi-language, one with a gallery, etc.

I will like to learn from your knowledge in achieving this. Will be a time saver. Can you lead me with a written direction, maybe made available on your site.

After the MODX Weekend - I don't want to spoil my presentation

As far as your exact needs goes, it depends on how "individual" each site is. Do they use the same database? Does each site have its own database?

You can copy the files from one site to another, but then you have to edit four configuration files, and probably run setup again in upgrade mode, so you might just as well use something like install.php to download and give you the setup installer to install each one new, then you don't have to worry about paths and database stuff.

If you use Vapor on the basic site, you can then immediately install the Vapor's whatever.transport.zip file to have a clone of your basic site. The only thing to keep in mind is that the database is replaced, so your Manager login will not be valid, and you'll need to log out and log in again the the same login as the original basic site.