This would allow you to use the php command from scripts to run the cloner with passed in parameters necessary to control cloning.

We create custom clones for clients based on replaced keywords. !@STORENAME!@,!@ADDRESS!@ ETC..

The search and replace works great when creating a clone. But I would like to save these fields so I don't have to type them in each time I create a clone. It would speed up the process.

Thank you for your great plugin. We have a WordPress plugin that shares file and folders in multisite and it doesn’t need to be copied for every child site.
I wanted to suggest that it will be great if developers can filter files and configuration via WP hooks. Specially in copying files.
I’m referring a hook or filter in ns_recursive_dir_copy() where:
foreach ($files as $file){
if ($file != “.” && $file != “..” && $file != ‘sites’){
$num = ns_recursive_dir_copy(“$src/$file”, “$dst/$file”, $num);
}
}
so it can be filtered with hook via our plugin.
Thanks in advance.

I would love to be able to type into the Custom Site Fields Configuration and have it populate information in the ACF options or page fields.

It would be handy to have all my template blogs grouped together.
http://note.io/1zffzlZ

Maybe throw chosen on there too? http://harvesthq.github.io/chosen/

Finally, could the items be numbered by order in the list instead of an ID or order created? Not sure if that is used elsewhere but just 1,2,3... would be more useful for my use case.

hi - i have quite a few MU-WP sites. my "template" site is a bit difficult to find, and i would like to be able to establish my "template" site as a default.

There are theme thumbnails for Registration Template selections, but no descriptors. The Registration Templates we are offering have specialized configurations for particular use cases - it would be great to note these tailored uses in the Registration Template form.

Build (NS cloner X)

remotely pulls single (or subsites)
into a local multisite, as a subsite.

Deliciousbrains has one

There is an issue with db tables with names that contain wp_
e.g.
wp_8_facetwp_index is the correct new name for my cloned table but it was named wp_8_facetwp_8_index .

I suggest you check if wp_ is at the start of the table name.

Great plugin otherwise

It's not a big deal, but I have a permanent warning on the top of the screen because Nginx doesn't use .htaccess files.

This would provide self-serve template selection for a new registering user that generates a copy of a template site as their new site from the front-end.

This add-on would have two separate functions. 1: to allow manual selection of which tables should be cloned to the new site. 2: to allow certain global tables to be set as "excluded" by default any time the root site is cloned.