[BUGFIX] Don't try to flush output buffers that don't exist #198
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
All existing output buffers are closed before dumping the file contents. Calling ob_flush again will not have an effect on the buffers, but trigger a warning instead. (Notice: ob_flush(): failed to flush buffer. No buffer to flush)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
All existing output buffers are closed before dumping the file contents. Calling
ob_flushagain will not have an effect on the buffers, but trigger a warning instead:Notice: ob_flush(): failed to flush buffer. No buffer to flushWith exceptionErrors enabled, this will break the eID dumpfile function.