Fix fatal error when another the_content filter callback returns null instead of a string #1283
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 a support topic, a user reported a fatal error:
Uncaught TypeError: webp_uploads_update_image_references(): Argument #1 ($content) must be of type string, null given
It appears there is some other plugin which adds a
the_content
filter which returnsnull
instead of astring
. Sincewebp_uploads_update_image_references()
is added as a filter, it should be updated to guard against this case by allowingmixed
as the input, as we've done for other filters. This stems from work in #775.