If the website is critical for the Organization and downtime is not acceptable, please open a ticket with Drupal Service and we will prepare the procedure for a transparent name transfer. Note that this action might take some time.
In case you come across any errors after cloning your site, there is one action you can try before opening a ticket. Go to the menu where you can normally take and restore backups: <SITE>.web.cern.ch/_site/backups/
and click the big red button REGISTRY REBUILD
Thanks for writing your experience. The incredibly long sync itself is completely out of our control, and I have complained to the responsible service.
To work around this in some cases, since mid-March we don’t remove the admin egroup when the Drupal 7 site is deleted. When the Drupal 8 site with the same name is created, it picks up admins from the same, existing egroup. Therefore, if you have been in the admin egroup of the old Drupal 7 and the Drupal 8 DEV site long enough (>1 day to be sure), there should be no further delay after the Drupal 8 PROD site is created.
I have created the new version of my current D7 website (https://odpp.web.cern.ch/) under Drupal 8 as a dev. site and built it from scratch (https://test-odp1.web.cern.ch/).
Now I want to put my new site in production, but with a new name, ideally https://privacy.web.cern.ch.
I would furthermore like to keep my current dev site, so that I can use it for further tests.
My questions are:
a) Can I follow the 4-step-procedure mentionned above, involving cloning, to put in production my new site?
b) Can I omit step 4 to keep my dev. site?
Many thanks, dear Ismael, for the quick reply.
So, I will start with the procedure, but wait until I delete the old web site so that I can request a static copy as a safeguard (should not be a problem, as the new site will have a different name).
my new web site under Drupal 8 is now in production (https://privacy.web.cern.ch/) and I have for my archives a zip file with my old Drupal 7 site (http://odpp.web.cern.ch/).
I would like to delete now the ODPP site, and have an automatic redirect from the ODPP site that points to the landing page of the PRIVACY site. Do you know how I can put in place such a redirect?
Many thanks in advance for your advice,
I think one way would be to delete the ODPP site, and once the alias is available — it can take up to two hours — you register this odpp site again to be an alias of your new privacy site, by managing the later one and just adding an alias with that name.
That’s what we did for some of the sites we already put in production