-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Admin Titles: avoid PHP warnings in PHP 8.1 #4308
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
jeherve
wants to merge
1
commit into
WordPress:trunk
Choose a base branch
from
jeherve:fix/warning-strip-tags
base: trunk
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
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 was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since
wp_strip_all_tags()now handlesnull(see related trac ticket and commit d46dc08), I suppose we could do without the extra check, and only replacestrip_tagsbywp_strip_all_tags:Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
HIya @jeherve !
IMO, the pulled fix is not the right approach/fix for the following reason:
$titlemay still benullafterwards.This means, the problem is now moved to subsequent functions which may be handling
$titleand using PHP native functions to do so, so this is just setting WP up for the next bug report instead of fixing the actual issue that$titleshould always be set and set to astring.As for the second proposal (comment above), which I do think is better, there is one thing I'd like to point out about that:
nullsilently, but for anything scalar but non-string, that will now yield awarning, which is a significantly higher error level than the originaldeprecation(though justifiable).In both cases, the
// phpcs:ignore ...comment needs to be removed as that WPCS rule does not apply to WP Core and we should not add unnecessary noise like that to the codebase.