Fix debug.log warnings - session already started and headers being already sent #32
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have a custom theme that has user logins and related code where I use the PHP session.
In such a case, the SCORM Cloud plugin causes warnings to be written to the log file when WP debug is enabled.
Steps to reproduce
Visit any page on the website or in the admin.
Also trigger WP cron by visiting "/wp-cron.php?doing_wp_cron=1667920617.6225979328155517578125"
Check /wp-content/debug.log
Result:
The following warnings appears in the log file: