Answers.Body: <p>Just adding an answer - which is actually from the comments - since I think stackexchange doesn't like answers in the comments - anyway - the issue was an extra copy of the codebase</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-09-25T11:33:39.937Z
Answers.LastActivityDate: 2020-09-25T11:33:39.937Z
Answers.UserDisplayName: eileen
Body: <p>I have a WordPress website that is using v5.22.0 of CiviCRM, it was a fresh install and this is my first time trying to upgrade it.</p>
  <p>To upgrade to v5.29.1 I followed all steps to the letter:
  <a href="https://docs.civicrm.org/sysadmin/en/latest/upgrade/wordpress/" rel="nofollow noreferrer">https://docs.civicrm.org/sysadmin/en/latest/upgrade/wordpress/</a></p>
  <p>When I attempt the final step to upgrade the database which is to point your browser to the URL <a href="http://example.org/wp-admin/admin.php?page=CiviCRM&amp;q=civicrm/upgrade&amp;reset=1" rel="nofollow noreferrer">http://example.org/wp-admin/admin.php?page=CiviCRM&amp;q=civicrm/upgrade&amp;reset=1</a> (obviously replacing example.org with our domain) I get the error message and there is no Upgrade Now button:</p>
  <blockquote>
  <p>Sorry, due to an error, we are unable to fulfill your request at the
  moment. You may want to contact your administrator or service provider
  with more details about what action you were performing when this
  occurred. Your database has already been upgraded to CiviCRM 5.22.0</p>
  </blockquote>
  <p>Am I done? Is there no database upgrade to be done between v5.22.0 and v5.29.1? Everything appears to be working on the front / backend.... did I do it properly?</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-09-24T19:39:22.230Z
Comments.Text: It looks like it's not picking up the new code base - there is always an upgrade- you don't still have the old code 'somewhere' on you system do you? There should be a file in your civi dir xml/version.xml with the version....
Comments.UserDisplayName: eileen
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-09-24T19:41:36.003Z
Comments.Text: Found a copy of the old codebase! Got rid of that and working now, thank you.
Comments.UserDisplayName: MrLucas
Tags: <wordpress><upgrade>
Title: Error after upgrading from v5.22.0 to v5.29.1 in WordPress
ThreadText: # Error after upgrading from v5.22.0 to v5.29.1 in WordPress
  
  (Asked by: username_0 on 2020-09-24)
  
  I have a WordPress website that is using v5.22.0 of CiviCRM, it was a fresh install and this is my first time trying to upgrade it.
  
  To upgrade to v5.29.1 I followed all steps to the letter:
  <https://docs.civicrm.org/sysadmin/en/latest/upgrade/wordpress/>
  
  When I attempt the final step to upgrade the database which is to point your browser to the URL <http://example.org/wp-admin/admin.php?page=CiviCRM&q=civicrm/upgrade&reset=1> (obviously replacing example.org with our domain) I get the error message and there is no Upgrade Now button:
  
  > Sorry, due to an error, we are unable to fulfill your request at the
  > moment. You may want to contact your administrator or service provider
  > with more details about what action you were performing when this
  > occurred. Your database has already been upgraded to CiviCRM 5.22.0
  
  Am I done? Is there no database upgrade to be done between v5.22.0 and v5.29.1? Everything appears to be working on the front / backend.... did I do it properly?
  
  **Tags:** wordpress, upgrade
  
  > **Comments:**
  > **username_1**: It looks like it's not picking up the new code base - there is always an upgrade- you don't still have the old code 'somewhere' on you system do you? There should be a file in your civi dir xml/version.xml with the version....  
  > **username_0**: Found a copy of the old codebase! Got rid of that and working now, thank you.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2020-09-25. Score: 1 | Accepted answer
  
  Just adding an answer - which is actually from the comments - since I think stackexchange doesn't like answers in the comments - anyway - the issue was an extra copy of the codebase
  
  
  ---
  
  