• Hello! Fantastic plugin!

    When we have a subdomain multisite setup, WordPress allows us to populate any domain when creating a new site in the network, not just a subdomain of the main stie. NS Cloner, however, is forcing the cloned site to be a subdomain of the main one. This creates additional work for the admin… they have to clone the site, go into the site list, change the domain manually, log into the new site, and perform a search and replace (and then a cache flush, depending on config).

    Please provide the option to completely specify the full FQDN when cloning a site that is part of a subdomain install. I agree that it makes sense to perhaps pre-populate the new site’s domain field with the main site’s domain for ease of use for people who just want subdomains, but since “subdomain” is kind of a misnomer at the WordPress-level anyway (as it allows for fully unique FQDNs for each site), this would bring it more into alignment with how WordPress operates, and save time for users who are using separate domains.

    Thanks!

Viewing 1 replies (of 1 total)
  • I second this. We are setting up about 110 subsites that are being built with subdomains. split pretty evenly between two different domains. For 1/2 of them I have to change and then do a find and replace after creating. I wish we could just use the cloner to set them up. Additional we have a handful that are being added with their own custom domain.

Viewing 1 replies (of 1 total)
  • The topic ‘Allow custom domains in subdomain install’ is closed to new replies.