• I know the temporary solution is probably to disable the plugin, but I really need it for my site.

    But I’m getting errors consistently for the past few days; is this a known problem and is there a fix for it? thank you very much!

    PHP Warning: session_start(): Cannot send session cookie – headers already sent in *** wp-content/plugins/custom-sidebars/inc/class-custom-sidebars-explain.php on line 55

    https://wordpress.org/plugins/custom-sidebars/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Confirmed. I am getting the same error but only when I try to use the www version of our domain. Our WordPress Address and Site Address are set to non-www. But this is still a real problem since not everyone visiting the site will know to leave off the www.

    Full error below.

    Warning: session_start(): Cannot send session cookie - headers already sent by (output started at /wp-includes/functions.php:3008) in /wp-content/plugins/custom-sidebars/inc/class-custom-sidebars-explain.php on line 55
    
    Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /wp-includes/functions.php:3008) in /wp-content/plugins/custom-sidebars/inc/class-custom-sidebars-explain.php on line 55
    
    Warning: Cannot modify header information - headers already sent by (output started at /wp-includes/functions.php:3008) in /wp-includes/pluggable.php on line 896

    Hey there guys,

    Hope you’re well today 🙂

    Thanks for additional info, can you please try redirecting www to non www in htaccess, that should fix the issue.

    If you’re unsure how to do this please check the following: http://stackoverflow.com/questions/234723/generic-htaccess-redirect-www-to-non-www

    Hope this helps 🙂

    Cheers,
    Bojan

    We are already redirecting www to non-www.

    Found our issue.

    Long story. We are using W3 Total Cache and for some reason we had a cached version of the www site. When a user would visit the www they were served the cached version and the errors. Since we changed to non-www W3 won’t clear the old cache from admin. I did it manually and now everything looks good.

    Must have been a problem in an older version of the plugin that was cached and has been fixed since.

    Hey again robskidmore,

    Thank you for taking time to post you solution here, glad you manged to figure that one out 🙂

    @mel2337 Can you please try the solution from @robskidmore in case you’re using caching plugins?

    Have a nice day!

    Best regards,
    Bojan

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Getting a PHP warning related to this plugin’ is closed to new replies.