• Resolved Ambyomoron

    (@josiah-s-carberry)


    I believe you are already aware of the situation leading to entries in the WordPress debug.log similar to:

    PHP Warning: session_start(): Cannot start session when headers already sent in /mysite/wp-content/plugins/webba-booking-lite/frontend/classes/class_wbk_frontend_booking.php on line 38

    I hope you resolve the underlying issue, which will like come back to haunt us sooner or later.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Webba Appointment Booking

    (@webba-agency)

    Hello,

    Thank you for your message.

    However this bug is not caused by Webba Booking plugin. Let me explain: headers are sent in a wrong way by some other plugin or your current theme. As a result Webba can’t initialize session and the error message appeared. To be sure I have tested again on our staging server and confirm that the issue is not observed. To troubleshot the issue on your server I would suggest doing the following:

    1. clean up log file.
    2. try with the default theme.
    3. try with other plugins deactivated.

    If you have any questions, please reply to in the topic.

    Thread Starter Ambyomoron

    (@josiah-s-carberry)

    Thank you for this explanation. I will investigate farther what is happening.

    I wonder if you could share more information about what I should look for in an incorrectly formed header that is causing the problem.

    Plugin Author Webba Appointment Booking

    (@webba-agency)

    Yes, sure.

    Headers are generated by plugins or theme. Warning message appears on the page that contains the Webba Booking’s shortcode. Therefore, if you want to determine which plugin or theme cause the issue, you need to deactivate plugins, refresh the page page with Webba shortcode and check if the warning message appeared or not.

    If you have any question, feel free to ask.

    Thread Starter Ambyomoron

    (@josiah-s-carberry)

    Thank you for that, but my question was different. I want to know what directive(s) in the header I should be looking for, not how to find which plugin is causing the problem.

    Plugin Author Webba Appointment Booking

    (@webba-agency)

    By the ‘headers’ in this case we mean any output made in a wrong way, there is no strict directives you can search for. This can be unexpected output using echo or mistaken usage of html templates. From my experience, the error can be caused because of the extra-spaces in the php files before the opening tag <?php. Hope this helps.

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

The topic ‘Cannot start session when headers already sent’ is closed to new replies.