I would like to clone and then replace an existing Hub site as a workflow for editing and then deploying site updates. However, I don't want to end up with new Core Team and Content Groups I have to configure every time I do this. Can you use the existing groups from the original site? Has anyone done this successfully and would you mind sharing the Clone/Replace process you follow?
are you cloning your site to make new sites (like it's a template) or are you cloning it to iterate on the same site as a sort of way to stage changes (like draft publishing)
edit: i'm dumb you gave me the answer in the title 🙂
we are a few weeks away from releasing a draft publishing flow in Hub Sites
That's good to hear. That should resolve the issue going forward. I do have a more immediate need to replace my current site as my existing AGOL users have lost the ability to save changes. (I submitted a support ticket on this and it was recommended that I just create a new site to resolve the issue) Do you have a basic process of what I need to do to manually clone and replace a site?
Hello @Anonymous User - I realize this topic is a bit dated, but when you say "we are a few weeks away from releasing a draft publishing flow in Hub Sites" - can you direct me to that resource?
I can't seem to locate a "draft publishing flow" such that I too can clone our site without having to configure a new core team and content groups.
We send a lot of data to our site via distributed collaborations and this will be a real time saver.
for others that run into this sort of issue "Cannot save domain changes" error....
there was a bug....for a short time if you updated your URL we would redirect traffic through the new URL but the site item did not get the updated URL stored in it. for your URL's protection we throw the above error if we ever see these two are out of sync.
Chase and I met and used the equivalent of the AGO Assistant to edit the site item's data.json resource--updating the `subdomain` and `defaultHostname` to match the actual URL that the site was running on.
once we did that the site is once again editable. i hope not many of you need this info but wanted to close the loop