From b0ccfc5ce87f09d4df814b057f5e6820d37fdad1 Mon Sep 17 00:00:00 2001 From: Helen Foster Date: Tue, 5 Jan 2010 22:18:03 +0000 Subject: [PATCH] config settings: MDL-16658 small rewording --- config-dist.php | 21 +++++++++++---------- 1 file changed, 11 insertions(+), 10 deletions(-) diff --git a/config-dist.php b/config-dist.php index 5ad939e961..6049e33387 100644 --- a/config-dist.php +++ b/config-dist.php @@ -180,19 +180,20 @@ $CFG->admin = 'admin'; // shared out from your site/institution! // $CFG->includeuserpasswordsinbackup = true; // -// Completely disable user creation on restore, bypassing any right granted -// via roles/capabilities. By enabling this setting any restore process -// requiring users to be created will be stopped before any further action. +// Completely disable user creation when restoring a course, bypassing any +// permissions granted via roles and capabilities. Enabling this setting +// results in the restore process stopping when a user attempts to restore a +// course requiring users to be created. // $CFG->disableusercreationonrestore = true; // // Modify the restore process in order to force the "user checks" to assume -// that the backup was originated in a different site so detection of matching -// users is performed with some different (more "relaxed") rules. *Only* useful -// if the backup file has been generated with Moodle < 1.9.4 and the site has -// been rebuilt from scratch using backup files (not the best way, btw). If you -// are getting user conflicts on restore, try to restore the backup to a different -// site, backup it again and then restore on target server instead of enabling this -// setting permanently! +// that the backup originated from a different site, so detection of matching +// users is performed with different (more "relaxed") rules. Note that this is +// only useful if the backup file has been created using Moodle < 1.9.4 and the +// site has been rebuilt from scratch using backup files (not the best way btw). +// If you obtain user conflicts on restore, rather than enabling this setting +// permanently, try restoring the backup on a different site, back it up again +// and then restore on the target server. // $CFG->forcedifferentsitecheckingusersonrestore = true; // // Prevent stats processing and hide the GUI -- 2.39.5