Answers.Body: <p>Check your civicrm.settings.php file to be sure that the $civicrm_root variable is correctly set, as is all the other settings in that file.  Be sure to check all the way to the end of the file, just in case some override was done.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-10-27T21:01:39.727Z
Answers.LastActivityDate: 2016-10-27T21:01:39.727Z
Answers.UserDisplayName: DaveD
Answers.Body: <p>Our CiviCRM was installed outside of the Drupal root in order to circumvent performance issues with Drupal commons. I have re-engineered so that CiviCRM is now inside the Drupal root and upgraded. I also noticed multiple instances of Drupal in /var/www/html so I moved all other copies to a backups folder outside of the html folder.</p>
  
  <p>We no longer have this problem.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-01-13T20:05:11.830Z
Answers.LastActivityDate: 2017-01-13T20:05:11.830Z
Answers.UserDisplayName: Christia
Body: <p>Running CiviCRM 4.3.8 on Drupal 7.37 (for now, but we're in the long process of a major upgrade of our website). Often I have to update the paths because they revert to a different docroot which may have been originally set up for testing purposes. (Let's call them A and B, A is the correct one and B is the wrong docroot.)</p>
  
  <p>When it reverts seems to be at random and I cannot find the cause, but it causes problems such as emails going out with links to a test website in B's docroot, the reports will not load, etc.</p>
  
  <p>Update file paths settings will show:</p>
  
  <p>Old Base Directory - 
  /var/www/html/B/docroot/sites/default/files/</p>
  
  <p>New Base Directory - 
  /var/www/html/A/docroot/sites/default/files/</p>
  
  <p>Edit: The CiviCRM installation is in a separate docroot from the Drupal installation (for now) and uses symlinks in sites/all/modules in order for Drupal to find it. </p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-10-25T20:13:34.913Z
Comments.Text: That's a very old version of CiviCRM! [Consider upgrading](https://civicrm.org/civicrm/contribute/transact?reset=1&id=78).
Comments.UserDisplayName: Coleman
Tags: <civimail><drupal><cache>
Title: Clean Up Caches and Update Paths
ThreadText: # Clean Up Caches and Update Paths
  
  (Asked by: username_0 on 2016-10-25)
  
  Running CiviCRM 4.3.8 on Drupal 7.37 (for now, but we're in the long process of a major upgrade of our website). Often I have to update the paths because they revert to a different docroot which may have been originally set up for testing purposes. (Let's call them A and B, A is the correct one and B is the wrong docroot.)
  
  When it reverts seems to be at random and I cannot find the cause, but it causes problems such as emails going out with links to a test website in B's docroot, the reports will not load, etc.
  
  Update file paths settings will show:
  
  Old Base Directory -
  /var/www/html/B/docroot/sites/default/files/
  
  New Base Directory -
  /var/www/html/A/docroot/sites/default/files/
  
  Edit: The CiviCRM installation is in a separate docroot from the Drupal installation (for now) and uses symlinks in sites/all/modules in order for Drupal to find it.
  
  **Tags:** civimail, drupal, cache
  
  > **Comments:**
  > **username_1**: That's a very old version of CiviCRM! [Consider upgrading](https://civicrm.org/civicrm/contribute/transact?reset=1&id=78).  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_0 on 2017-01-13. Score: 3 | Accepted answer
  
  Our CiviCRM was installed outside of the Drupal root in order to circumvent performance issues with Drupal commons. I have re-engineered so that CiviCRM is now inside the Drupal root and upgraded. I also noticed multiple instances of Drupal in /var/www/html so I moved all other copies to a backups folder outside of the html folder.
  
  We no longer have this problem.
  
  
  ---
  
  ### Answer by username_2 on 2016-10-27. Score: 1
  
  Check your civicrm.settings.php file to be sure that the $civicrm\_root variable is correctly set, as is all the other settings in that file. Be sure to check all the way to the end of the file, just in case some override was done.
  
  
  ---
  
  