Answers.Body: <p>Changing the site key will break a few things. How many of these are important is up to you, but at least:
  - every rest interface that connects to the site to read or write (you might not have any)
  - any hash (eg. link to update preferences). this might not be an issue if the domain name changes too
  - anything that is saved encrypted (eg. the password for the smtp connection).</p>
  
  <p>search the code base for CIVICRM_SITE_KEY to have a complete list.</p>
  
  <p>This being said, the easiest is probably simply to change and wait for a while to see if it breaks any of the features YOU use.</p>
  
  <p>The value of the key itself doesn't matter, as long as it's hard to guess and long enough. The setup process generates it that way:</p>
  
  <pre><code>md5(uniqid('', TRUE) . $params['baseURL'])
  </code></pre>
  
  <p>so a random hash of 32 characters</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-15T07:56:13.970Z
Answers.Text: Thanks for your reply. This is a new site changing over so I rather make the changes now and break it then later. How could I create a new site key then? Cheers
Answers.UserDisplayName: Sohal Khatwani
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-15T08:17:00.313Z
Answers.Text: the value of the key by itself doesn't matter. During the install, its md5(uniqid('', TRUE) . $params['baseURL']
Answers.UserDisplayName: Xavier
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-16T06:56:21.130Z
Answers.Text: thanks for your help. I have made the changes as per your suggestions. Lets see how it goes. Cheers.
Answers.UserDisplayName: Sohal Khatwani
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-15T07:38:09.410Z
Answers.LastActivityDate: 2015-04-15T08:20:20.400Z
Answers.LastEditDate: 2015-04-15T08:20:20.400Z
Answers.UserDisplayName: Xavier
Body: <p>We have developed a white label Drupal and CiviCRM installation which we plan to use to launch a new server. When changing over I usually change the settings files to match the new database settings. However, I have noticed that the CiviCRM Site key also need to be changed. How can I go about doing this or is this not possible? THanks.</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-04-15T03:22:56.393Z
Comments.Text: Are you just cloning and site and modifying the civicrm.settings.php file? Can you use a similar approach to what you are doing with the dsn?
Comments.UserDisplayName: Donald Lobo
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-04-15T03:53:31.137Z
Comments.Text: Hi Donald. Yes, just cloning the site and modifying the civicrm.settings.php file. I modify the base URL and the database login credentials. Not sure what to do with the site key.  We are keeping the same name for the database for now on the new server. If I try to change the database name the website stops working. Another issue to figure out!
Comments.UserDisplayName: Sohal Khatwani
Tags: <civicrm-home>
Title: Changing CiviCRM Site Key in the civicrm.settings.php file
ThreadText: # Changing CiviCRM Site Key in the civicrm.settings.php file
  
  (Asked by: username_0 on 2015-04-15)
  
  We have developed a white label Drupal and CiviCRM installation which we plan to use to launch a new server. When changing over I usually change the settings files to match the new database settings. However, I have noticed that the CiviCRM Site key also need to be changed. How can I go about doing this or is this not possible? THanks.
  
  **Tags:** civicrm-home
  
  > **Comments:**
  > **username_1**: Are you just cloning and site and modifying the civicrm.settings.php file? Can you use a similar approach to what you are doing with the dsn?  
  > **username_0**: Hi Donald. Yes, just cloning the site and modifying the civicrm.settings.php file. I modify the base URL and the database login credentials. Not sure what to do with the site key.  We are keeping the same name for the database for now on the new server. If I try to change the database name the website stops working. Another issue to figure out!  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2015-04-15. Score: 3
  
  Changing the site key will break a few things. How many of these are important is up to you, but at least:
  - every rest interface that connects to the site to read or write (you might not have any)
  - any hash (eg. link to update preferences). this might not be an issue if the domain name changes too
  - anything that is saved encrypted (eg. the password for the smtp connection).
  search the code base for CIVICRM_SITE_KEY to have a complete list.
  This being said, the easiest is probably simply to change and wait for a while to see if it breaks any of the features YOU use.
  The value of the key itself doesn't matter, as long as it's hard to guess and long enough. The setup process generates it that way:
  md5(uniqid('', TRUE) . $params['baseURL'])
  
  so a random hash of 32 characters
  
  > **Comments:**
  > **username_0**: Thanks for your reply. This is a new site changing over so I rather make the changes now and break it then later. How could I create a new site key then? Cheers  
  > **username_2**: the value of the key by itself doesn't matter. During the install, its md5(uniqid('', TRUE) . $params['baseURL']  
  > **username_0**: thanks for your help. I have made the changes as per your suggestions. Lets see how it goes. Cheers.  
  
  ---
  
  