Answers.Body: <p>People using 4.7 are out of date - 4.7 is end-of-life.  You should definitely go with 5.x for most use cases.</p>
  
  <p>I would check your error logs in the <a href="https://civicrm.stackexchange.com/a/15932/12">ConfigAndLog</a> directory - then come back here and edit your question to add the relevant logs.  In general, there's a <a href="https://docs.civicrm.org/sysadmin/en/latest/troubleshooting/" rel="nofollow noreferrer">troubleshooting page</a> in the documentation, but most of the suggestions aren't applicable to upgrade failures.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-09-14T22:43:18.377Z
Answers.LastActivityDate: 2018-09-14T22:43:18.377Z
Answers.UserDisplayName: Jon G - Megaphone Tech
Body: <p>I'm relatively new to CiviCRM and am trying to get a client set up with the platform. I like it overall, it seems much more usable than most I've touched in the past.</p>
  
  <p>All seemed to be going well until late last week. I had it basically set up on a third-party server. There might have been a resource path issue, or it might be a known testing bug (probably the latter).</p>
  
  <p>Somewhere in there an upgrade was called for by Civi and I decided to give it a try. It appeared to work, but after the DB upgrade step I couldn't get to any Civi pages. I had to completely blow away Civi and start again to get anything displayed. Restoring the db from Backup brought me back to a somewhat usable state, but it wants to upgrade the db. I've tried a couple times with the same result.</p>
  
  <p>I'm limping along right now with a db that says it needs to upgrade, but otherwise seems to work.</p>
  
  <p>Looking around on the forums here, it seems like maybe I should be using an older version. The website seemed to be strongly steering me to 5.* so I assumed it was stable. I see here, people using 4.7 which I didn't even see on the website (all seemed to be 5.* and 4.6.*).</p>
  
  <p>Any thoughts on either fixing this 5.5.1 problem or if I should be finding and running 4.7?</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-09-14T19:04:54.120Z
Comments.Text: Did you check CiviCRM logs to see for any error?
Comments.UserDisplayName: Pradeep Nayak
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-09-14T19:06:08.453Z
Comments.Text: There's a report on the WordPress Mattermost channel that non-shortcode URLs have an issue on 5.5.1. If so that's a major problem and will likely be sorted very shortly.
Comments.UserDisplayName: Andrew West
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-09-21T08:56:01.567Z
Comments.Text: update: there haven't been any other reports on this since, so I don't think it's an issue.
Comments.UserDisplayName: Andrew West
Tags: <upgrade><database><version>
Title: Wordpress CiviCRM site unusable after database upgrade from 5.4.0 to 5.5.1
ThreadText: # Wordpress CiviCRM site unusable after database upgrade from 5.4.0 to 5.5.1
  
  (Asked by: username_0 on 2018-09-14)
  
  I'm relatively new to CiviCRM and am trying to get a client set up with the platform. I like it overall, it seems much more usable than most I've touched in the past.
  
  All seemed to be going well until late last week. I had it basically set up on a third-party server. There might have been a resource path issue, or it might be a known testing bug (probably the latter).
  
  Somewhere in there an upgrade was called for by Civi and I decided to give it a try. It appeared to work, but after the DB upgrade step I couldn't get to any Civi pages. I had to completely blow away Civi and start again to get anything displayed. Restoring the db from Backup brought me back to a somewhat usable state, but it wants to upgrade the db. I've tried a couple times with the same result.
  
  I'm limping along right now with a db that says it needs to upgrade, but otherwise seems to work.
  
  Looking around on the forums here, it seems like maybe I should be using an older version. The website seemed to be strongly steering me to 5.\* so I assumed it was stable. I see here, people using 4.7 which I didn't even see on the website (all seemed to be 5.\* and 4.6.\*).
  
  Any thoughts on either fixing this 5.5.1 problem or if I should be finding and running 4.7?
  
  **Tags:** upgrade, database, version
  
  > **Comments:**
  > **username_1**: Did you check CiviCRM logs to see for any error?  
  > **username_2**: There's a report on the WordPress Mattermost channel that non-shortcode URLs have an issue on 5.5.1. If so that's a major problem and will likely be sorted very shortly.  
  > **username_2**: update: there haven't been any other reports on this since, so I don't think it's an issue.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_3 on 2018-09-14. Score: 1
  
  People using 4.7 are out of date - 4.7 is end-of-life. You should definitely go with 5.x for most use cases.
  
  I would check your error logs in the [ConfigAndLog](https://civicrm.stackexchange.com/a/15932/12) directory - then come back here and edit your question to add the relevant logs. In general, there's a [troubleshooting page](https://docs.civicrm.org/sysadmin/en/latest/troubleshooting/) in the documentation, but most of the suggestions aren't applicable to upgrade failures.
  
  
  ---
  
  