warning_settings isn't properly used. #201
Merged
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
Signed-off-by:Thorsten Eurich <thorsten@eurich.de>
…ning_settings'] is still a string. Signed-off-by:Thorsten Eurich <thorsten@eurich.de>
…it is used in Display. Signed-off-by: Norv <a.w.norv@gmail.com>
Add warning_enable as permanently accessible $modSetting
|
Lets sneak it in then. |
norv
added a commit
that referenced
this pull request
Mar 4, 2013
warning_settings isn't properly used.
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.
There are several places where $modSettings['warning_settings'] was used as an array, but it was never made an array in the first instace. Either it should be used as a string or be splitted into an array. My fix does the same as it was aldready done in Admin.php