PHP Warning: Cannot modify header information – headers already sent by

  • Resolved lmm314

    (@lmm314)


    10 years, 2 months ago

    I’ve got these errors happening twice each day since I installed April 04. Meaning the 554, 556, 559 lines are listed twice on April 4, twice on April 5 and April 6

    [04-Apr-2016 00:04:25 UTC] PHP Warning: Cannot modify header information – headers already sent by (output started at /home/xxx/public_html/xxx/wp-content/plugins/sucuri-scanner/sucuri.php:7307) in /home/xxx/public_html/xxx/wp-includes/class-IXR.php on line 554
    [04-Apr-2016 00:04:25 UTC] PHP Warning: Cannot modify header information – headers already sent by (output started at /home/xxx/public_html/xxx/wp-content/plugins/sucuri-scanner/sucuri.php:7307) in /home/xxx/public_html/xxx/wp-includes/class-IXR.php on line 556
    [04-Apr-2016 00:04:25 UTC] PHP Warning: Cannot modify header information – headers already sent by (output started at /home/xxx/public_html/xxx/wp-content/plugins/sucuri-scanner/sucuri.php:7307) in /home/xxx/public_html/xxx/wp-includes/class-IXR.php on line 559

    https://ww.wp.xz.cn/plugins/sucuri-scanner/

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter lmm314

    (@lmm314)

    10 years, 2 months ago

    oops, sorry, it’s not twice a day. Its multiple times a day since April 4. Actually April 6 has those lines a lot.

    yorman

    (@yorman)

    10 years, 2 months ago

    That line 7307 [1] is associated to the admin notices, those bars that appear on top of the admin dashboard with information of the result of an action. Some time ago someone reported a similar issue during the user authentication process so I decided to include a conditional to stop printing that admin notice during the user logins.

    Can you tell me which actions you executed when the errors were logged? That way I can include another conditional in the code to prevent the printing of the admin notices during the execution of those actions too.

    [1] https://github.com/Sucuri/sucuri-wordpress-plugin/blob/a2363e036d0caaf0c462c0265d1b0b567a2f580c/sucuri.php#L7307

    Thread Starter lmm314

    (@lmm314)

    10 years, 2 months ago

    I don’t recall editing anything on April 6th. Just found the error log in my clients ftp account. I deleted it last night from the ftp and there is not one today. But logging into the WP I do see these errors…

    Dashboard: Sucuri: (1460040370) Get_logs: couldn’t connect to host.

    Then in the Last Logins area, there is someone trying to login constantly but failing and that looks ok. But below it is more than 50 lines that say basically the same thing…

    Thread Starter lmm314

    (@lmm314)

    10 years, 2 months ago

    oops, got cut off…

    yorman

    (@yorman)

    10 years, 2 months ago

    Many errors have been fixed in the development version of the code [1] I do not know if this is (related to) one of them but I suggest you to install it [2] and see if the problem disappears. The error message about the connection might be related to the API request timeout, you can configure that from the “API Service” panel located in the plugin’ settings page.

    Check the settings page, there are a lot of options that can be used to configure the plugin to match your needs and be fully compatible with the server where your website is being hosted. Since I do not know anything about your hosting provider I can not provide any specific configuration, but I am sure you will figure it out.

    Feel free to ask questions about the available options.

    [1] https://github.com/Sucuri/sucuri-wordpress-plugin
    [2] https://github.com/Sucuri/sucuri-wordpress-plugin/archive/master.zip

    andersce

    (@andersce)

    10 years, 2 months ago

    Was there ever a fix for this? I’m getting lots of sucuri.php line 7307 headers already sent warnings in my error_log (1859 times in the last 37 days).

    I’ve only edited the site once in that time so I don’t think it’s connected to editing the site.

    Thanks in advance.

    yorman

    (@yorman)

    9 years, 1 month ago

    The API service was recently migrated to a different server with better performance. We will monitor the requests from multiple locations and apply patches to the code if necessary. During the last month the average response time has been 5 secs and the maximum has been 20 secs. If someone detects timeouts with higher values let me know. For now lets consider this issue resolved.

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

The topic ‘PHP Warning: Cannot modify header information – headers already sent by’ is closed to new replies.