issue/594 - Prefer "require_once" in a few spots. #595
+7
−7
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.
What?
Using "require_once" everywhere, replacing a few inconsistent "require" and "include_once" usages
Why?
I'm being a silly and manually including a file in another plugin
How?
By using require_once, we'll all get to bypass some PHP warnings that don't appear to be intended behavior as-is
Testing Instructions
Install the latest Github master branch of the WP User Profiles plugin, navigate to your Admin Area Profile page, and visit the "Account" tab. Once there, you'll see a glorious warning because we're already (manually) including one of the files in this plugin
Changelog Entry
Prefer "require_once" in a few spots.
This change prevents unintended PHP warnings when silly JJJ people are doing silly JJJ things.
Fixes #594.