Answers.Body: <p>SiteHealth does not account for sessions and CiviCRM depnds on them. See the discussion at <a href="https://lab.civicrm.org/dev/wordpress/-/issues/32" rel="noreferrer">https://lab.civicrm.org/dev/wordpress/-/issues/32</a></p>
  <p>Possible fix:
  <a href="https://civicrm.stackexchange.com/a/35234/155">https://civicrm.stackexchange.com/a/35234/155</a></p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-08-21T00:36:56.350Z
Answers.Text: Thanks, Pradeep Nayak. The discussion gives me a much better understanding.
Answers.UserDisplayName: rgilman
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-08-20T21:52:55.120Z
Answers.LastActivityDate: 2020-08-20T21:52:55.120Z
Answers.UserDisplayName: Pradeep Nayak
Body: <p>This is related to <a href="https://civicrm.stackexchange.com/questions/35227/wordpress-site-health-contains-critical-errors-unless-civicrm-is-disabled">WordPress Site Health contains critical errors unless CiviCRM is disabled</a> but I'm raising it because</p>
  <ol>
  <li>WordPress 5.5 adds the &quot;active PHP session was detected&quot; issue</li>
  <li>There was no response to RiverRunner's request for the basis for saying the test are inaccurate</li>
  </ol>
  <p>I'm currently running WordPress 5.5 and CiviCRM 5.28.2.</p>
  <p>The Site Health function in WordPress 5.5 reports 3 three &quot;critical issues&quot; related to the WP REST API.</p>
  <ol>
  <li>An active PHP session was detected - A PHP session was created by a session_start() function call. This interferes with REST API and loopback requests. The session should be closed by session_write_close() before making any HTTP requests.</li>
  <li>The REST API encountered an error - The REST API is one way WordPress, and other applications, communicate with the server. One example is the block editor screen, which relies on this to display, and save, your posts and pages.
  The REST API request failed due to an error.
  Error: cURL error 28: Operation timed out after 10005 milliseconds with 0 bytes received (http_request_failed)</li>
  <li>Your site could not complete a loopback request - Loopback requests are used to run scheduled events, and are also used by the built-in editors for themes and plugins to verify code stability.
  The loopback request to your site failed, this means features relying on them are not currently working as expected.
  Error: cURL error 28: Operation timed out after 10004 milliseconds with 0 bytes received (http_request_failed)</li>
  </ol>
  <p><a href="https://wordpress.org/support/topic/critical-issue-active-php-session/" rel="nofollow noreferrer">This discussion</a> suggests that the problem is with plugins and themes that need to be updated. By elimination, I found that CiviCRM 5.28.2 was triggering the error.</p>
  <p>Can these &quot;critical issues&quot; safely be ignored and, if so, why or under what conditions?</p>
  
Tags: <wordpress><error>
Title: CiviCRM 5.28.2 triggering "critical issue" in WordPress 5.5 Site Health
ThreadText: # CiviCRM 5.28.2 triggering "critical issue" in WordPress 5.5 Site Health
  
  (Asked by: username_0 on 2020-08-20)
  
  This is related to [WordPress Site Health contains critical errors unless CiviCRM is disabled](https://civicrm.stackexchange.com/questions/35227/wordpress-site-health-contains-critical-errors-unless-civicrm-is-disabled) but I'm raising it because
  
  1. WordPress 5.5 adds the "active PHP session was detected" issue
  2. There was no response to RiverRunner's request for the basis for saying the test are inaccurate
  
  I'm currently running WordPress 5.5 and CiviCRM 5.28.2.
  
  The Site Health function in WordPress 5.5 reports 3 three "critical issues" related to the WP REST API.
  
  1. An active PHP session was detected - A PHP session was created by a session\_start() function call. This interferes with REST API and loopback requests. The session should be closed by session\_write\_close() before making any HTTP requests.
  2. The REST API encountered an error - The REST API is one way WordPress, and other applications, communicate with the server. One example is the block editor screen, which relies on this to display, and save, your posts and pages.
     The REST API request failed due to an error.
     Error: cURL error 28: Operation timed out after 10005 milliseconds with 0 bytes received (http\_request\_failed)
  3. Your site could not complete a loopback request - Loopback requests are used to run scheduled events, and are also used by the built-in editors for themes and plugins to verify code stability.
     The loopback request to your site failed, this means features relying on them are not currently working as expected.
     Error: cURL error 28: Operation timed out after 10004 milliseconds with 0 bytes received (http\_request\_failed)
  
  [This discussion](https://wordpress.org/support/topic/critical-issue-active-php-session/) suggests that the problem is with plugins and themes that need to be updated. By elimination, I found that CiviCRM 5.28.2 was triggering the error.
  
  Can these "critical issues" safely be ignored and, if so, why or under what conditions?
  
  **Tags:** wordpress, error
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2020-08-20. Score: 4 | Accepted answer
  
  SiteHealth does not account for sessions and CiviCRM depnds on them. See the discussion at <https://lab.civicrm.org/dev/wordpress/-/issues/32>
  
  Possible fix:
  <https://civicrm.stackexchange.com/a/35234/155>
  
  > **Comments:**
  > **username_0**: Thanks, username_1. The discussion gives me a much better understanding.  
  
  ---
  
  