Title: Plugin session writes make subrequests fail
Last modified: July 3, 2020

---

# Plugin session writes make subrequests fail

 *  [tigertech](https://wordpress.org/support/users/tigertech/)
 * (@tigertech)
 * [5 years, 11 months ago](https://wordpress.org/support/topic/plugin-session-writes-make-subrequests-fail/)
 * This plugin opens (but does not close) a PHP session for each request, which 
   makes WordPress “loopback” requests fail because the sloopback request can’t 
   lock the same session ID. This manifests as failures in the health check (“Your
   Site Could Not Complete a Loopback Request”) and slow requests when using [for
   example] the AMP plugin.
 * The technical cause of the problem is that the file at “/cm-list-manager-pro/
   plugin/notices/AdminNoticeManager.php” uses start_session(), but does not use
   session_write_close() after each write or read to avoid session deadlocks, as
   explained in <[https://ma.ttias.be/php-session-locking-prevent-sessions-blocking-in-requests/&gt](https://ma.ttias.be/php-session-locking-prevent-sessions-blocking-in-requests/&gt);.
   Adding session_write_close() would presumably solve it.
 * Can this be fixed?

The topic ‘Plugin session writes make subrequests fail’ is closed to new replies.

 * ![](https://ps.w.org/cm-curated-list-manager/assets/icon-256x256.png?rev=3228330)
 * [CM Curated List Manager - Effortless tool for link management](https://wordpress.org/plugins/cm-curated-list-manager/)
 * [Support Threads](https://wordpress.org/support/plugin/cm-curated-list-manager/)
 * [Active Topics](https://wordpress.org/support/plugin/cm-curated-list-manager/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/cm-curated-list-manager/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/cm-curated-list-manager/reviews/)

 * 0 replies
 * 1 participant
 * Last reply from: [tigertech](https://wordpress.org/support/users/tigertech/)
 * Last activity: [5 years, 11 months ago](https://wordpress.org/support/topic/plugin-session-writes-make-subrequests-fail/)
 * Status: not resolved