Skip to content
Snippets Groups Projects
Commit 0ecf3cb8 authored by Gabor Hojtsy's avatar Gabor Hojtsy
Browse files

Issue #2824671 by mikeryan, heddn, quietone: Document dangers of preserving IDs on migration

parent 84d1e518
No related branches found
No related tags found
No related merge requests found
......@@ -803,6 +803,9 @@ public function buildOverviewForm(array $form, FormStateInterface $form_state) {
$info[] = $this->t('Make sure that the host this site is on has access to the database for your previous site.');
$info[] = $this->t('If your previous site has private files to be migrated, a copy of your files directory must be accessible on the host this site is on.');
$info[] = $this->t('In general, enable all modules on this site that are enabled on the previous site. For example, if you have used the book module on the previous site then you must enable the book module on this site for that data to be available on this site.');
$info[] = $this->t('Do not add any information on this site (including but not limited to user accounts, taxonomy terms, and node content) before upgrading. Any pre-existing information on the site risks being overwritten by the upgrade process. See <a href=":url">the upgrade preparation guide</a> for more information.', [
':url' => 'https://www.drupal.org/docs/8/upgrade/preparing-an-upgrade#dont_create_content',
]);
$info[] = $this->t('Put this site into <a href=":url">maintenance mode</a>.', [
':url' => Url::fromRoute('system.site_maintenance_mode')->toString(TRUE)->getGeneratedUrl(),
]);
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment