Cannot send session cookie/cache/header in session_start().

  • Resolved WPAdminJoe

    (@wpadminjoe)


    10 years, 11 months ago

    I just added new functionality to my site which works fine on the development site (Windows 7) but fails with the messages below on production (Linux Webm401.xx).

    Warning: session_start(): Cannot send session cookie – headers already sent
    Warning: session_start(): Cannot send session cache limiter – headers already sent
    Warning: Cannot modify header information – headers already sent by

    (output started at /home/wordpress/wp-includes/class.wp-scripts.php:180) in /administration/index.php on line2

    Based on my research of the problem, everything seems to point to un-readable characters in class.wp-scripts.php which was never modified. I have insured that my new code does not contain any un-readable characters.

    The only modules modified within WP are:

    • Functions.php in the child theme (added Admin Bar main/sub menu options)
    • wp-config.php (added a variable to the end of the file)
    • The addition of a new page.

    Functions and wp-config were modified using Notepad++ and have an encoding of UTF-8 without BOM.

    Why would I have a problem within the class.wp-scripts.php core file?

    Any ideas?

    Thankx

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter WPAdminJoe

    (@wpadminjoe)

    10 years, 10 months ago

    Hello,

    Still hoping someone can help with this error as I cannot integrate another application into the WP Administration panel.

    The errors are:
    Warning: session_start(): Cannot send session cookie – headers already sent (output started at /home/wordpress/wp-includes/class.wp-scripts.php:180) in /administration/index.php on line 2

    Warning: session_start(): Cannot send session cache limiter – headers already sent(output started at /home/wordpress/wp-includes/class.wp-scripts.php:180) in /administration/index.php on line 2

    Warning: Cannot modify header information – headers already sent by (output started at /home/wordpress/wp-includes/class.wp-scripts.php:180) in /administration/index.php on line 26

    All pointing to the class.wp-scripts.php core file

    Anyone? Configuration problem perhaps?

    Thanx, Joe

    Denzel Chia

    (@denzel_chia)

    10 years, 10 months ago

    Hi,

    Why don’t you try re-installing WordPress?
    And try using servers that are WordPress recommended?
    https://ww.wp.xz.cn/about/requirements/

    Perhaps subscribing a WordPress friendly web hosting is much easier to handle.

    I have never encountered your error.

    Thanks!

    Thread Starter WPAdminJoe

    (@wpadminjoe)

    10 years, 10 months ago

    Hello Denzel;

    I certainly am not going to perform a reinstall of WordPress each time a glitch occurs within the environment. The only exception being a very precise and complete explanation as to why a reinstall will fix the problem. But some debugging first would be nice. I have spent hours attempting to insure that no white space or improper code exists in my modified modules.

    Since this is occurring in a core module (class.wp-scripts.php:180), I was hoping this would be of interest to an author.

    As an update, I have backup and restored a base copy of class.wp-scripts.php. Same error occured.

    Thanx

    Joe

    Denzel Chia

    (@denzel_chia)

    10 years, 10 months ago

    Hi,

    If you think that is a bug in WordPress, you can report it https://make.ww.wp.xz.cn/core/handbook/testing/reporting-bugs/

    Thanks

    Thread Starter WPAdminJoe

    (@wpadminjoe)

    10 years, 10 months ago

    Hey Danzel,

    Your suggestion is a good one and thank you for the link. Before doing so however, I am going to open a new post in the WordPress Forum where this should have probably been in the first place since it is a core issue.

    Thanx again. Cheers.

    Thread Starter WPAdminJoe

    (@wpadminjoe)

    10 years, 10 months ago

    Closed but unresolved. Moved to the WordPress Forum where it belongs.

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

The topic ‘Cannot send session cookie/cache/header in session_start().’ is closed to new replies.