|
David Dadekian
|
October 15, 2013 at 9:06 am
Every 3 hours the following two lines show up in my error_log:
[15-Oct-2013 13:00:01 UTC] PHP Warning: session_start() [< a href='function.session-start'>function.session-start]: Cannot send session cookie – headers already sent in [ROOT]/eatdrinkri.com/wp-content/plugins/espresso-multiple/espresso-multi-registration.php on line 72
[15-Oct-2013 13:00:01 UTC] PHP Warning: session_start() [< a href='function.session-start'>function.session-start]: Cannot send session cache limiter – headers already sent (output started at [ROOT]/eatdrinkri.com/wp-content/plugins/espresso-multiple/espresso-multi-registration.php:72) in [ROOT]/eatdrinkri.com/wp-content/plugins/espresso-multiple/espresso-multi-registration.php on line 72
I replaced my path with [ROOT] but other than that, those are the errors. I can’t seem to find the exact problem in a topic. This is a new install of WordPress and the Event Espresso plugins on an already registered domain.
I have one event live right now: http://eatdrinkri.com/event-registration/?ee=1
WordPress version 3.6.1
Event Espresso – Version 3.1.35.1.P
Event Espresso – Multi Event Registration Version 1.0.4
Event Espresso – Permissions Version 1.5.4.1
Event Espresso – Recurring Events Version 1.1.7.1
Event Espresso – Social Media Version 1.1.5.1
Event Espresso – Ticketing Version 2.0.10.2.p
Event Espresso – API Plugin Version 2.0.3.p
-
This topic was modified 11 years, 1 month ago by
 David Dadekian.
-
This topic was modified 4 years, 9 months ago by
 Seth Shoultes. Reason: Removed broken link
-
This topic was modified 4 years, 9 months ago by Seth Shoultes. Reason: Removed broken link
|
|
Josh
|
October 15, 2013 at 1:22 pm
Hi David,
It turns out that this is not an error, but rather a warning.
The message actually says that “Plugin is trying to start a session, but output has been already sent to the browser”. A session cannot be started after a single byte (it can even be a space) has been sent to the browser.
One possible cause is a space forgotten by the developer in one of your plugins or your theme files coming after closing ?> tag.
It may be difficult to find the real source of such an issue. One method is by deactivating all of your plugins (except Multi Event Registration) and reactivating them one by one. Then check the log file.
What you might try first is try loading up the default WP theme and deactivate/reactivate Multi Event Registration. If you don’t get the message there, then you can look for the problem in your theme files (possibly in functions.php).
|
