Answers.Body: <p>Make sure there is only one symlink (name does not matter) from modules directory to any civicrm directory outside web root. You might also need to restart apache after you delete the additional symlinks / directory</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-27T18:20:45.397Z
Answers.LastActivityDate: 2015-05-27T18:20:45.397Z
Answers.UserDisplayName: Donald Lobo
Answers.Body: <p>It's how I do it, it works fine.</p>
  
  <p>So you have (outside of the drupal folder) several folders civicrm-4.5.4 civicrm-4.6.2 ...</p>
  
  <p>and (within the sites/all/modules create a single symlink civicrm -> the later civicrm-4.6.2)</p>
  
  <p>The name doesn't matter, but as you will have urls that use it, I recommend keeping civicrm as the name of the symlink, and only keep a single one that you symlink with the civicrm version you want</p>
  
  <p>then you upgrade normally using civicrm/upgrade and voila</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-28T12:36:05.960Z
Answers.Text: didn't work for me
Answers.UserDisplayName: roi
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-28T12:38:35.177Z
Answers.Text: could you clarify what didn't work?
Answers.UserDisplayName: Xavier
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-28T15:50:52.693Z
Answers.Text: @DonaldLobo what you wrote, together with restarting apache service has solved. thanks
Answers.UserDisplayName: roi
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-28T12:32:52.367Z
Answers.LastActivityDate: 2015-04-29T09:26:53.193Z
Answers.LastEditDate: 2015-04-29T09:26:53.193Z
Answers.UserDisplayName: Xavier
Answers.Body: <p>Symlinks may have to be enabled in the Apache configuration by putting
      Options FollowSymLinks
  in your .htaccess or apache config file.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-29T18:22:36.473Z
Answers.LastActivityDate: 2015-04-29T18:22:36.473Z
Answers.UserDisplayName: Tom B.
Body: <p>I am used to put all my development stuff (not only civicrm) at a certain point on my linux machine, therefore I use symlink from </p>
  
  <pre><code>&lt;drupal base&gt;/sites/all/module/civicrm to /my/devel/path/civicrm
  </code></pre>
  
  <p>This has the benefit of pointing the link to a newer version of civicrm as a means of upgrade or testing new developments.</p>
  
  <p>This doesn't work when I change the symlink to point to another version of my development.
  The instructions regarding upgrade civicrm (for example to 4.6) won't be helpful here because they talk about replacing the files locally.</p>
  
  <p>Do you think the way I work is not logical?</p>
  
  <p>thanks</p>
  
Tags: <developer>
Title: symlink at sites/all/modules/civicrm doesn't work
ThreadText: # symlink at sites/all/modules/civicrm doesn't work
  
  (Asked by: username_0 on 2015-04-28)
  
  I am used to put all my development stuff (not only civicrm) at a certain point on my linux machine, therefore I use symlink from
  
  ```
  <drupal base>/sites/all/module/civicrm to /my/devel/path/civicrm
  
  ```
  
  This has the benefit of pointing the link to a newer version of civicrm as a means of upgrade or testing new developments.
  
  This doesn't work when I change the symlink to point to another version of my development.
  The instructions regarding upgrade civicrm (for example to 4.6) won't be helpful here because they talk about replacing the files locally.
  
  Do you think the way I work is not logical?
  
  thanks
  
  **Tags:** developer
  
  
  ---
  
  ## 3 answers
  
  ### Answer by username_1 on 2015-05-27. Score: 1 | Accepted answer
  
  Make sure there is only one symlink (name does not matter) from modules directory to any civicrm directory outside web root. You might also need to restart apache after you delete the additional symlinks / directory
  
  
  ---
  
  ### Answer by username_2 on 2015-04-28. Score: 2
  
  It's how I do it, it works fine.
  
  So you have (outside of the drupal folder) several folders civicrm-4.5.4 civicrm-4.6.2 ...
  
  and (within the sites/all/modules create a single symlink civicrm -> the later civicrm-4.6.2)
  
  The name doesn't matter, but as you will have urls that use it, I recommend keeping civicrm as the name of the symlink, and only keep a single one that you symlink with the civicrm version you want
  
  then you upgrade normally using civicrm/upgrade and voila
  
  > **Comments:**
  > **username_0**: didn't work for me  
  > **username_2**: could you clarify what didn't work?  
  > **username_0**: @username_1 what you wrote, together with restarting apache service has solved. thanks  
  
  ---
  
  ### Answer by username_3 on 2015-04-29. Score: 1
  
  Symlinks may have to be enabled in the Apache configuration by putting
  Options FollowSymLinks
  in your .htaccess or apache config file.
  
  
  ---
  
  