Conflict with Cron

  • Resolved timwendisch

    (@timwendisch)


    4 years ago

    We want to use your plugin in our kubernetes environment. While testing we had the issue, that on each cron-tick we get the error:
    “session_set_save_handler(): Cannot change save handler when headers already sent in /www/htdocs/w0146a6f/staging/staging.healy.shop/releases/20200422121153/wp-content/plugins/wp-native-php-sessions/pantheon-sessions.php on line 163”

    I found out, that the headers, which have been already send are the default wp expire headers

    [22-Apr-2020 16:37:52 UTC] array (
  0 => 'Expires: Wed, 11 Jan 1984 05:00:00 GMT',
  1 => 'Cache-Control: no-cache, must-revalidate, max-age=0',
  2 => 'Content-type: text/html',
)

    Is there a possibility to deactivate this for cron?

    We have a big commercial Site (woo-commerce) with a lot of different plugins on actual WordPress version 5.4

    Thank you in advanced!

Viewing 1 replies (of 1 total)
  • Plugin Author Daniel Bachhuber

    (@danielbachhuber)

    4 years ago

    Hey @timwendisch,

    Thanks for the report!

    I don’t see any reason why WP Native PHP Sessions should initialize for DOING_CRON. I’ve tagged a new v1.1.0 release which disables PHP sessions in the cron context.

Viewing 1 replies (of 1 total)
  • The topic ‘Conflict with Cron’ is closed to new replies.

Tags