• Resolved stephta6

    (@stephta6)


    Hey there,

    So far this plugin as been great. I did run into one snag that I am hoping you could help me with. When I first built the site I made a test subsite with the name de.vidyo.com. I deleted that subsite because eventually it would become a clone of vidyo.com. I made sure to completely remove the site from the database. When it came time to clone vidyo.com, I tried to name it de.vidyo.com and I got an error saying: “Sorry that site is reserved.” I double and triple checked and there are absolutely no references to that domain or any tables with it’s former ID in the database. Any ideas why the NS Cloner won’t let me reuse that name for my subsite?

Viewing 1 replies (of 1 total)
  • Plugin Author Never Settle

    (@neversettle)

    That message is generated by WordPress when you try to create a site with the same name as an existing user. This can happen whether from a user that was created as part of a subsite that was previously created and then deleted, or even if the user was just added separately. (The user can be a member of any existing site, so be sure to verify through /wp-admin/network/users.php). The keyword here in that message is “reserved.” WordPress reserves site names for existing users because with certain settings it allows users to create blogs and it wants the blog name to match the user name. 

    The Cloner uses the WordPress blogname validation to make sure that a new site that is generated the result of a cloning operation is a valid sitename and won’t lead to other issues after it is cloned.

    You can:
    1) delete the user with the same name
    2) manually edit the DB to change that username and re-use the original for the site
    3) use a different site name

    Best!
    NS

Viewing 1 replies (of 1 total)
  • The topic ‘Sorry that Site is Reserved’ is closed to new replies.