Answers.Body: <p>You should double check your <code>civicrm_settings.php</code> file. Particularly the section on File System Paths. Make sure the setting <code>$civicrm_root</code> is the correct path to civicrm for the new server.</p>
  
  <p>Hope this helps...</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-08T19:10:02.963Z
Answers.LastActivityDate: 2018-01-08T19:10:02.963Z
Answers.UserDisplayName: KilakwaBT
Answers.Body: <p>WP Engine is a quirky host--it makes lots of configuration decisions for you with the goal of optimizing for WordPress sites, but that often makes things more difficult for CiviCRM.  This is in stark contrast to Linode, where you have full control over your hosting configuration.</p>
  
  <p>A <code>500</code> error could be any number of things; you'll need to find a log message to tell you more, and I'm not certain where exactly this is on WP Engine.</p>
  
  <p>However, for examples of WP Engine-specific quirks, you might look at the following other questions:</p>
  
  <ul>
  <li><a href="https://civicrm.stackexchange.com/q/12479/44">How to successfully install CiviCRM w/Wordpress on WPEngine hosting</a></li>
  <li><a href="https://civicrm.stackexchange.com/q/7057/44">In Wordpress, I want to convert my installation from an external database to use the default database</a></li>
  <li><a href="https://civicrm.stackexchange.com/q/7611/44">Hosting CiviCRM and Wordpress on WPengine</a></li>
  </ul>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-05T17:45:34.593Z
Answers.Text: [Fri Jan 05 17:10:50.413260 2018] [:error] [pid 7021] [client 73.181.6.230:53278] PHP Fatal error: require_once(): Failed opening required 'CRM/Core/ClassLoader.php' (include_path='.:/var/www/stlukespaa.org/wp-content/plugins/civicrm/civicrm/:/var/www/stlukespaa.org/wp-content/plugins/civicrm/civicrm//packages:.:/usr/share/pear/php:/usr/share/php:/usr/share/pear') in /nas/content/live/stpaa/wp-content/plugins/civicrm/civicrm.settings.php on line 357, referer: https://stlukespaa.org/wp-admin/plugins.php
Answers.UserDisplayName: Matthew Plamp
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-05T18:15:32.723Z
Answers.Text: You may want to double check your civicrm_settings.php file. Particularly the path to civicrm and make sure it is correct for the new server.
Answers.UserDisplayName: KilakwaBT
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-08T18:42:55.933Z
Answers.Text: @KilakwaBT want to post your comment as a separate answer? I agree with your assessment - I don't think this is a WPEngine issue, I think it's an incomplete migration issue with the old filesystem path retained in `civicrm.settings.php` (or possibly somewhere else, eg DB or another config file).
Answers.UserDisplayName: Chris Burgess
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-08T19:10:40.897Z
Answers.Text: @ChrisBurgess Just added it as an answer. Thanks.
Answers.UserDisplayName: KilakwaBT
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-05T17:40:59.440Z
Answers.LastActivityDate: 2018-01-05T17:40:59.440Z
Answers.UserDisplayName: Andie Hunt
Body: <p>I recently moved from linod sever to Wp-Engine server.  I did the migration but Civicrm plugin wont work. I see it in the sidebar but when I click on it to access it I get a Http 500 page not found error.  I am unsure what to do to fixed it. </p>
  
Tags: <migration><error-page><500>
Title: Http 500 Page not Found error when plugin clicked on backend - Wp-engine
ThreadText: # Http 500 Page not Found error when plugin clicked on backend - Wp-engine
  
  (Asked by: username_0 on 2018-01-05)
  
  I recently moved from linod sever to Wp-Engine server. I did the migration but Civicrm plugin wont work. I see it in the sidebar but when I click on it to access it I get a Http 500 page not found error. I am unsure what to do to fixed it.
  
  **Tags:** migration, error-page, 500
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2018-01-08. Score: 3
  
  You should double check your `civicrm_settings.php` file. Particularly the section on File System Paths. Make sure the setting `$civicrm_root` is the correct path to civicrm for the new server.
  
  Hope this helps...
  
  
  ---
  
  ### Answer by username_2 on 2018-01-05. Score: 2
  
  WP Engine is a quirky host--it makes lots of configuration decisions for you with the goal of optimizing for WordPress sites, but that often makes things more difficult for CiviCRM. This is in stark contrast to Linode, where you have full control over your hosting configuration.
  
  A `500` error could be any number of things; you'll need to find a log message to tell you more, and I'm not certain where exactly this is on WP Engine.
  
  However, for examples of WP Engine-specific quirks, you might look at the following other questions:
  
  * [How to successfully install CiviCRM w/Wordpress on WPEngine hosting](https://civicrm.stackexchange.com/q/12479/44)
  * [In Wordpress, I want to convert my installation from an external database to use the default database](https://civicrm.stackexchange.com/q/7057/44)
  * [Hosting CiviCRM and Wordpress on WPengine](https://civicrm.stackexchange.com/q/7611/44)
  
  > **Comments:**
  > **username_0**: [Fri Jan 05 17:10:50.413260 2018] [:error] [pid 7021] [client 73.181.6.230:53278] PHP Fatal error: require_once(): Failed opening required 'CRM/Core/ClassLoader.php' (include_path='.:/var/www/stlukespaa.org/wp-content/plugins/civicrm/civicrm/:/var/www/stlukespaa.org/wp-content/plugins/civicrm/civicrm//packages:.:/usr/share/pear/php:/usr/share/php:/usr/share/pear') in /nas/content/live/stpaa/wp-content/plugins/civicrm/civicrm.settings.php on line 357, referer: https://stlukespaa.org/wp-admin/plugins.php  
  > **username_1**: You may want to double check your civicrm_settings.php file. Particularly the path to civicrm and make sure it is correct for the new server.  
  > **username_3**: @username_1 want to post your comment as a separate answer? I agree with your assessment - I don't think this is a WPEngine issue, I think it's an incomplete migration issue with the old filesystem path retained in `civicrm.settings.php` (or possibly somewhere else, eg DB or another config file).  
  > **username_1**: @ChrisBurgess Just added it as an answer. Thanks.  
  
  ---
  
  