This repository was archived by the owner on Sep 24, 2018. It is now read-only.
Handle falsy value from wp_count_terms(), fixing fatal #1641
Conversation
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
This causes a fatal error `<br /><b>Fatal error</b>: Unsupported operand types in <b>/srv/www/wordpress-trunk.dev/wp-content/plugins/WP-API/lib/endpoints/class-wp-rest-terms-controller.php</b> on line <b>105</b><br />` otherswise.
Member
There was a problem hiding this comment.
Should we submit a core ticket for this?
danielbachhuber
added a commit
that referenced
this pull request
Oct 20, 2015
Handle falsy value from wp_count_terms, fixing fatal
danielbachhuber
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
See #1613