Cannot modify header information – headers already sent (solution)

  • Resolved p4r4n1c

    (@p4r4n1c)


    7 years, 1 month ago

    In Regards to Patrich Beuken‘s Topic, wich was marked as resolved but with no answer given, here’s my solution:

    If you don’t need the debug output,
    in wp-content/plugins/wp-invites/wp-invites.php line 26 change
    echo "\n<!--wp-invites debug:\n" . implode("\n\n", $this->debug_log) . "\n-->";
    to
    //echo "\n<!--wp-invites debug:\n" . implode("\n\n", $this->debug_log) . "\n-->";

    basically deactivating this line.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author themaster5_07

    (@themaster5_07)

    I have changed the status of Patrich Beuken’s post and will look into this issue this weekend. I was under the impression that this was resolved before I took over development and support. Thank you for your feedback.

    Plugin Author themaster5_07

    (@themaster5_07)

    @p4r4n1c, have you been able to duplicate this error? It seems as though this error would only occur if debugging is activated in the plugin configuration. I am thinking about disabling this debugging information altogether as I see this as having very little value to the end user, they just want it to work!

    As the debugging was added by the former developer, do you yourself see the need to having the debugging information available to the end users? (I wish there was a way to poll all users of the plugin with this question.)

    Thread Starter p4r4n1c

    (@p4r4n1c)

    I did deactivate debugging, both as an option aswell as deactivating the code.
    But the error still persists.

    I’d suggest that the plugin cannot resolve that ./wp.login.php was renamed to another link.

    Plugin Author themaster5_07

    (@themaster5_07)

    @p4r4n1c please update your plugin to the newest version 2.52 and confirm that this updated corrected your concerns.

    Plugin Author themaster5_07

    (@themaster5_07)

    @p4r4n1c Oh, and be sure to deactivate debugging mode. If debugging is enabled, then the problem with page redirection will still be present. I have added code statements to not run debugging functions if debugging is not enabled.

    Thread Starter p4r4n1c

    (@p4r4n1c)

    Yes, the white Screen “Bug” was solved now! thank you

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Cannot modify header information – headers already sent (solution)’ is closed to new replies.