This repository has been archived by the owner on Mar 26, 2021. It is now read-only.
Fixes for STRICT STANDARD errors in PHP 5.6 #14
Closed
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.
We are working on a project for WABE.org and are using PHP 5.6 and the plugin is throwing STRICT STANDARDS errors for a site that will launch Monday Sept 28th 2015. So I am providing a fix for those issues as well as fixing several other small issues I found, see below.
The fixes are not of the nature that are likely to break anything for existing sites; I avoiding making any backward incompatible changes.
Here is what this pull request includes:
require()
statements, ones that do not assume the location of the plugin.split()
with calls toexplode()
?>
fromnprml.php