This repository has been archived by the owner on Sep 16, 2019. It is now read-only.
Displays XML error messages on production website #385
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
In the current configuration FoundationPress is displaying error messages on production websites that have WP_DEBUG set to false. This corrects the issue.
|
Hi, Would you mind correcting the errors and push a new commit? Thanks! |
In the current configuration FoundationPress is displaying error messages on production websites that have WP_DEBUG set to false. This corrects the issue, and only outputs to the page if WP_DEBUG_DISPLAY is set to true.
|
Travis CI warnings corrected in 26984f3. |
olefredrik
added a commit
that referenced
this pull request
Jul 16, 2015
Displays XML error messages on production website
|
👍 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
In the current configuration FoundationPress is displaying error messages on production websites that have WP_DEBUG set to false. This corrects the issue.