Fixed bug in Profile > Authorized Applications #101
Merged
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
… the consumer name correctly.
… th with no left padding for some reason. Hardcoded some padding inline for now. Also included missing th element.
Member
|
Thanks for this, good catch!
That'd be less efficient, as it wouldn't be cached. :) |
rmccue
added a commit
that referenced
this pull request
Dec 7, 2015
Fixed bug in Profile > Authorized Applications
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Currently there is a bug in the WP-Admin > Users > Your Profile in the list of Authorized Applications. The name of the consumer application is not being displayed.
The current code has the consumer being looked up using
rest_get_client().The array of
$approvedapplications contains the consumer ID in the$row. This is simply thejson_consumertype post in wp_posts, so modified to simply useget_post().[ Alternatively, I suppose we could use a
$wpdbSELECT post_title .. query, since we've already pulled that into global. More efficient? ]