Answers.Body: <p>The assumption that was made in the instructions is that you must extract the files into the <code>/wp-content/plugins/</code> directory and then <em>rename</em> the resulting file to <code>civicrm</code>, just like the old directory was named. The previous step to this was to backup <code>/wp-content/plugins/civicrm</code>. </p>
  
  <p>E.g. Back up and delete <code>/wp-content/plugins/civicrm</code> then extract the new version and name it <code>civicrm</code> and put it in <code>/wp-content/plugins/</code>, thus replace the previous.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-12-24T19:48:20.147Z
Answers.Text: Thanks for confirming.  Assumptions in instructions is not a good thing. Is there someone I should contact about correcting the instructions or should I just try to edit them myself?
Answers.UserDisplayName: Mike Ubell
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-12-24T22:01:25.800Z
Answers.Text: I see now that my problem was that the gui tool I was using created an extra subdirectory to extract the zip file... so this was actually operator error.
Answers.UserDisplayName: Mike Ubell
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-12-24T03:57:36.737Z
Answers.LastActivityDate: 2016-12-24T08:55:18.793Z
Answers.LastEditDate: 2016-12-24T08:55:18.793Z
Answers.UserDisplayName: Christia
Body: <p>I was following the instructions to upgrade to 4.7.14 here:
  <a href="https://wiki.civicrm.org/confluence/display/CRMDOC/Upgrading+CiviCRM+for+Wordpress" rel="nofollow noreferrer">https://wiki.civicrm.org/confluence/display/CRMDOC/Upgrading+CiviCRM+for+Wordpress</a>
  It clearly says to extract the zip file in  /wp-content/plugins/. It then says to clear caches and point to the upgrade url.
  This leads to:
  Your database has already been upgraded to CiviCRM 4.7.13.
  The extract left things in a directory called: civicrm-4.7.14-wordpress. This implied to me that the upgrade will move things from there to the civicrm directory, but reading things here and elsewhere I suspect that files need to be extracted (or moved) to the civicrm directory.  There are no instructions to do that. Should I remove the civicrm/ tree and move civicrm-4.7.14-wordpress/civicrm to plugins/?</p>
  
Tags: <upgrade>
Title: Is there a mistake in the Upgrading CivCRM for WordPress instructions?
ThreadText: # Is there a mistake in the Upgrading CivCRM for WordPress instructions?
  
  (Asked by: username_0 on 2016-12-24)
  
  I was following the instructions to upgrade to 4.7.14 here:
  <https://wiki.civicrm.org/confluence/display/CRMDOC/Upgrading+CiviCRM+for+Wordpress>
  It clearly says to extract the zip file in /wp-content/plugins/. It then says to clear caches and point to the upgrade url.
  This leads to:
  Your database has already been upgraded to CiviCRM 4.7.13.
  The extract left things in a directory called: civicrm-4.7.14-wordpress. This implied to me that the upgrade will move things from there to the civicrm directory, but reading things here and elsewhere I suspect that files need to be extracted (or moved) to the civicrm directory. There are no instructions to do that. Should I remove the civicrm/ tree and move civicrm-4.7.14-wordpress/civicrm to plugins/?
  
  **Tags:** upgrade
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2016-12-24. Score: 2 | Accepted answer
  
  The assumption that was made in the instructions is that you must extract the files into the `/wp-content/plugins/` directory and then *rename* the resulting file to `civicrm`, just like the old directory was named. The previous step to this was to backup `/wp-content/plugins/civicrm`.
  
  E.g. Back up and delete `/wp-content/plugins/civicrm` then extract the new version and name it `civicrm` and put it in `/wp-content/plugins/`, thus replace the previous.
  
  > **Comments:**
  > **username_0**: Thanks for confirming.  Assumptions in instructions is not a good thing. Is there someone I should contact about correcting the instructions or should I just try to edit them myself?  
  > **username_0**: I see now that my problem was that the gui tool I was using created an extra subdirectory to extract the zip file... so this was actually operator error.  
  
  ---
  
  