Answers.Body: <p>The web host was running an older php version on their development server.  Updating to a newer version (they said 5+) solved the problem.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-08-18T16:04:41.467Z
Answers.Text: Please mark your own answer as the "accepted" one. It's perfectly fine to answer your own question on Stack Exchange sites!
Answers.UserDisplayName: Nicholai
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-07-21T17:47:17.563Z
Answers.LastActivityDate: 2015-07-21T17:47:17.563Z
Answers.UserDisplayName: createscape
Body: <p>I'm getting a 503 error when I use the contributions search:</p>
  
  <p>.../wp-admin/admin.php?page=CiviCRM&amp;q=civicrm%2Fcontribute%2Fsearch&amp;reset=1</p>
  
  <p>I've checked the following:</p>
  
  <ul>
  <li><p>Wordpress page called civicrm is present</p></li>
  <li><p>permalinks are set to post name</p></li>
  <li><p>under civi's wordpress integration settings, civicrm is set as the wordpress base page.  </p></li>
  </ul>
  
  <p>Thanks for your help.</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-07-20T23:59:20.890Z
Comments.Text: Does it help if you try replacing `%2F` with regular forward slashes?
Comments.UserDisplayName: Coleman
Tags: <contributions><search>
Title: Find Contributions Search 503 error
ThreadText: # Find Contributions Search 503 error
  
  (Asked by: username_0 on 2015-07-20)
  
  I'm getting a 503 error when I use the contributions search:
  
  .../wp-admin/admin.php?page=CiviCRM&q=civicrm%2Fcontribute%2Fsearch&reset=1
  
  I've checked the following:
  
  * Wordpress page called civicrm is present
  * permalinks are set to post name
  * under civi's wordpress integration settings, civicrm is set as the wordpress base page.
  
  Thanks for your help.
  
  **Tags:** contributions, search
  
  > **Comments:**
  > **username_1**: Does it help if you try replacing `%2F` with regular forward slashes?  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2015-07-21. Score: 1 | Accepted answer
  
  The web host was running an older php version on their development server. Updating to a newer version (they said 5+) solved the problem.
  
  > **Comments:**
  > **username_2**: Please mark your own answer as the "accepted" one. It's perfectly fine to answer your own question on Stack Exchange sites!  
  
  ---
  
  