Answers.Body: <p><a href="https://civicrm.stackexchange.com/questions/37438/civicrm-5-28-2-triggering-critical-issue-in-wordpress-5-5-site-health">CiviCRM 5.28.2 triggering &quot;critical issue&quot; in WordPress 5.5 Site Health</a></p>
  <p>This is not an issue with CiviCRM.  It's a failure of Site Health to consider that other plugins may use sessions</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-01-03T23:09:27.187Z
Answers.Text: How can this information be added to the installation documentation so newbies like myself are pre-warned?
Answers.UserDisplayName: Neil
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-01-05T12:31:15.013Z
Answers.Text: I am unsure how we could document this in a way that is visible.  We could add our own hook into Site Health and put the notice there, but we'd need  to find the time to do this.
Answers.UserDisplayName: Kevin Cristiano
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-01-07T09:21:13.393Z
Answers.Text: That would be so useful. It would be right there in your face when you become aware of the issue.
Answers.UserDisplayName: Neil
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-01-02T17:00:21.347Z
Answers.LastActivityDate: 2024-01-02T17:00:21.347Z
Answers.UserDisplayName: Kevin Cristiano
Body: <p>I am getting two critical issues in the WordPress Site Health section. These are:</p>
  <ol>
  <li><strong>An active PHP session was detected</strong></li>
  </ol>
  <p>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.</p>
  <ol start="2">
  <li><strong>The Rest API encountered an error</strong></li>
  </ol>
  <p>The REST API is one way that WordPress and other applications communicate with the server. For example, the block editor screen relies on the REST API to display and save your posts and pages.</p>
  <p>When testing the REST API, an error was encountered:</p>
  <p>REST API Endpoint: <a href="https://www.example.org/wp-json/wp/v2/types/post?context=edit" rel="nofollow noreferrer">https://www.example.org/wp-json/wp/v2/types/post?context=edit</a>
  REST API Response: (http_request_failed) cURL error 28: Operation timed out after 10001 milliseconds with 0 bytes received.</p>
  <p>...</p>
  <p>There were similar reports three/four years ago, and the conclusion then was that it was nothing to worry about as the WordPress Core does not use sessions, whereas CIVICRM does use them. Is this still the case?</p>
  <p>Some of the discussion about this is in this thread:</p>
  <p><a href="https://civicrm.stackexchange.com/questions/35227/wordpress-site-health-contains-critical-errors-unless-civicrm-is-disabled?rq=1">WordPress Site Health contains critical errors unless CiviCRM is disabled</a></p>
  <p>and through the links found on the page.</p>
  <p>If it is nothing to worry about, perhaps something could be added to the installation documentation about this known issue, so newbies like myself are pre-warned.</p>
  <p>Thanks</p>
  <p>Neil</p>
  
Tags: <wordpress>
Title: WordPress Site Health critical issues - CiviCRM 5.68.1 WordPress 6.4.2
ThreadText: # WordPress Site Health critical issues - CiviCRM 5.68.1 WordPress 6.4.2
  
  (Asked by: username_0 on 2024-01-02)
  
  I am getting two critical issues in the WordPress Site Health section. These are:
  
  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 that WordPress and other applications communicate with the server. For example, the block editor screen relies on the REST API to display and save your posts and pages.
  
  When testing the REST API, an error was encountered:
  
  REST API Endpoint: <https://www.example.org/wp-json/wp/v2/types/post?context=edit>
  REST API Response: (http\_request\_failed) cURL error 28: Operation timed out after 10001 milliseconds with 0 bytes received.
  
  ...
  
  There were similar reports three/four years ago, and the conclusion then was that it was nothing to worry about as the WordPress Core does not use sessions, whereas CIVICRM does use them. Is this still the case?
  
  Some of the discussion about this is in this thread:
  
  [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?rq=1)
  
  and through the links found on the page.
  
  If it is nothing to worry about, perhaps something could be added to the installation documentation about this known issue, so newbies like myself are pre-warned.
  
  Thanks
  
  username_0
  
  **Tags:** wordpress
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2024-01-02. Score: 2
  
  [CiviCRM 5.28.2 triggering "critical issue" in WordPress 5.5 Site Health](https://civicrm.stackexchange.com/questions/37438/civicrm-5-28-2-triggering-critical-issue-in-wordpress-5-5-site-health)
  
  This is not an issue with CiviCRM. It's a failure of Site Health to consider that other plugins may use sessions
  
  > **Comments:**
  > **username_0**: How can this information be added to the installation documentation so newbies like myself are pre-warned?  
  > **username_1**: I am unsure how we could document this in a way that is visible.  We could add our own hook into Site Health and put the notice there, but we'd need  to find the time to do this.  
  > **username_0**: That would be so useful. It would be right there in your face when you become aware of the issue.  
  
  ---
  
  