Title: Ryan McCue's Replies | WordPress.org --- # Ryan McCue [ ](https://wordpress.org/support/users/rmccue/) * [Profile](https://wordpress.org/support/users/rmccue/) * [Topics Started](https://wordpress.org/support/users/rmccue/topics/) * [Replies Created](https://wordpress.org/support/users/rmccue/replies/) * [Reviews Written](https://wordpress.org/support/users/rmccue/reviews/) * [Topics Replied To](https://wordpress.org/support/users/rmccue/replied-to/) * [Engagements](https://wordpress.org/support/users/rmccue/engagements/) * [Favorites](https://wordpress.org/support/users/rmccue/favorites/) Search replies: ## Forum Replies Created Viewing 15 replies - 1 through 15 (of 77 total) 1 [2](https://wordpress.org/support/users/rmccue/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/rmccue/replies/page/3/?output_format=md) [4](https://wordpress.org/support/users/rmccue/replies/page/4/?output_format=md) [5](https://wordpress.org/support/users/rmccue/replies/page/5/?output_format=md) [6](https://wordpress.org/support/users/rmccue/replies/page/6/?output_format=md) [→](https://wordpress.org/support/users/rmccue/replies/page/2/?output_format=md) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WordPress REST API (Version 2)] WP REST API Plugin support for PHP 7](https://wordpress.org/support/topic/wp-rest-api-plugin-support-for-php-7/) * Plugin Author [Ryan McCue](https://wordpress.org/support/users/rmccue/) * (@rmccue) * [9 years ago](https://wordpress.org/support/topic/wp-rest-api-plugin-support-for-php-7/#post-9353557) * The WordPress REST API is integrated into WordPress since 4.7, so you no longer need this plugin. Additionally, these are all false positives. * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [REST Api in WP 4.7](https://wordpress.org/support/topic/rest-api-in-wp-4-7/) * [Ryan McCue](https://wordpress.org/support/users/rmccue/) * (@rmccue) * [9 years, 7 months ago](https://wordpress.org/support/topic/rest-api-in-wp-4-7/#post-8620246) * You need to be using pretty permalinks to access `/wp-json/`. If you’re not, you can instead use `?rest_route=/` to get the index and `?rest_route=/wp/v2/ posts` (e.g.) for specific routes. * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [Anonymous user can get user list via REST API – is it a bug or a feature?](https://wordpress.org/support/topic/anonymous-user-can-get-user-list-via-rest-api-is-it-a-bug-or-a-feature/) * [Ryan McCue](https://wordpress.org/support/users/rmccue/) * (@rmccue) * [9 years, 7 months ago](https://wordpress.org/support/topic/anonymous-user-can-get-user-list-via-rest-api-is-it-a-bug-or-a-feature/#post-8620244) * There are a few restrictions on the data that’s shown here. In particular, only authors (users with published, publicly-available posts) are available when listing, and only information that’s already public is shown. * In particular, things like ID, username, display names, avatar URLs are all publicly- available via theme templates and feeds. We took specific care when designing the API to only expose what was already there. * If you’re concerned about this being an issue, I’d recommend installing a privacy- related plugin that handles all of these (including feeds), such as [iThemes Security](https://wordpress.org/plugins/better-wp-security/)( see [their post on this topic](https://ithemes.com/2016/12/22/update-on-the-wordpress-rest-api-and-ithemes-security/)). * Forum: [Hacks](https://wordpress.org/support/forum/plugins-and-hacks/hacks/) In reply to: [WP_UnitTestCase::tearDownAfterClass() -> “mysqli_query(): Couldn’t fetch mysqli”](https://wordpress.org/support/topic/wp_unittestcaseteardown-causes-mysqli_query-couldnt-fetch-mysqli/) * [Ryan McCue](https://wordpress.org/support/users/rmccue/) * (@rmccue) * [9 years, 8 months ago](https://wordpress.org/support/topic/wp_unittestcaseteardown-causes-mysqli_query-couldnt-fetch-mysqli/#post-8570345) * Heads up: I [filed this on Trac](https://core.trac.wordpress.org/ticket/39327) after finding the problem (PHPUnit’s backupGlobals option). The simple solution is to set `protected $backupGlobals = false` in your unit test. * Will continue to investigate the problem there. 🙂 * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WordPress Importer] Notice: wp_get_http is deprecated since version 4.4!](https://wordpress.org/support/topic/notice-wp_get_http-is-deprecated-since-version-44/) * Plugin Author [Ryan McCue](https://wordpress.org/support/users/rmccue/) * (@rmccue) * [10 years, 4 months ago](https://wordpress.org/support/topic/notice-wp_get_http-is-deprecated-since-version-44/#post-6836092) * > It’s like it got dropped 🙁 * Not dropped, just in hibernation, as my focus is split across a lot of different projects. The beta importer now has admin UI in the works and coming soon, see [this pull request](https://github.com/humanmade/WordPress-Importer/pull/26) for more about that. I’ll be writing an update about it soon. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WP REST API (WP API)] how to retrieve the users username and password by using wordpress](https://wordpress.org/support/topic/how-to-retrieve-the-users-username-and-password-by-using-wordpress/) * Plugin Author [Ryan McCue](https://wordpress.org/support/users/rmccue/) * (@rmccue) * [10 years, 8 months ago](https://wordpress.org/support/topic/how-to-retrieve-the-users-username-and-password-by-using-wordpress/#post-6777739) * You cannot retrieve the password, as passwords are stored in the database after hashing (which is a one-way, irreversible process). The username is available the `slug` property on the user, which you can get from `/users/me` * Also, you should update your version of WordPress 🙂 * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WP REST API (WP API)] Error trying to activate JSON REST API plugin](https://wordpress.org/support/topic/error-trying-to-activate-json-rest-api-plugin/) * Plugin Author [Ryan McCue](https://wordpress.org/support/users/rmccue/) * (@rmccue) * [11 years, 3 months ago](https://wordpress.org/support/topic/error-trying-to-activate-json-rest-api-plugin/#post-6033039) * I pinged [@tlovett1](https://wordpress.org/support/users/tlovett1/) (the author of CCF) about this, but doesn’t look like he’s gotten to it yet. 🙂 * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WP REST API (WP API)] html tags in content- WP REST API plugin](https://wordpress.org/support/topic/html-tags-in-content-wp-rest-api-plugin/) * Plugin Author [Ryan McCue](https://wordpress.org/support/users/rmccue/) * (@rmccue) * [11 years, 4 months ago](https://wordpress.org/support/topic/html-tags-in-content-wp-rest-api-plugin/#post-6007340) * This sounds like an issue with how you’re outputting `curfilm`. Not sure what templating language it is, but maybe try `{{{curfilm}}}` instead. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WP REST API (WP API)] Authentication question](https://wordpress.org/support/topic/authentication-question/) * Plugin Author [Ryan McCue](https://wordpress.org/support/users/rmccue/) * (@rmccue) * [11 years, 4 months ago](https://wordpress.org/support/topic/authentication-question/#post-6011684) * The REST API uses WP’s built-in authentication system, however requires a nonce to be passed unless specific handling is added for it. * Your best bet for custom authentication is to hook into the `determine_current_user` filter in core to do authentication, and then filter `json_authentication_errors` to integrate with the API. `WP_JSON_Server::check_authentication()` has documentation on how to use the latter. 🙂 * Forum: [Reviews](https://wordpress.org/support/forum/reviews/) In reply to: [[Test Plugin 3 - Testing plugin] What the hell is going on here](https://wordpress.org/support/topic/what-the-hell-is-going-on-here-1/) * Thread Starter [Ryan McCue](https://wordpress.org/support/users/rmccue/) * (@rmccue) * [11 years, 5 months ago](https://wordpress.org/support/topic/what-the-hell-is-going-on-here-1/#post-7942903) * (With thanks to [https://wordpress.org/support/topic/what-the-hell-is-going-on-here](https://wordpress.org/support/topic/what-the-hell-is-going-on-here)) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WP REST API (WP API)] Getting JSON without a curl call](https://wordpress.org/support/topic/getting-json-without-a-curl-call/) * Plugin Author [Ryan McCue](https://wordpress.org/support/users/rmccue/) * (@rmccue) * [11 years, 6 months ago](https://wordpress.org/support/topic/getting-json-without-a-curl-call/#post-5759891) * You should be able to do something like the following: * ``` $endpoint = new WP_JSON_Posts(); $data = $endpoint->get_post( 4 ); ``` * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WP REST API (WP API)] JSONP response add /**/ before the function name](https://wordpress.org/support/topic/jsonp-response-add-after-the-function-name/) * Plugin Author [Ryan McCue](https://wordpress.org/support/users/rmccue/) * (@rmccue) * [11 years, 11 months ago](https://wordpress.org/support/topic/jsonp-response-add-after-the-function-name/#post-5304784) * This is intentional, as it secures against an important security issue. * Why do you need to remove this? * Forum: [Reviews](https://wordpress.org/support/forum/reviews/) In reply to: [[WP REST API (WP API)] It could be better](https://wordpress.org/support/topic/it-could-be-better/) * Plugin Author [Ryan McCue](https://wordpress.org/support/users/rmccue/) * (@rmccue) * [11 years, 11 months ago](https://wordpress.org/support/topic/it-could-be-better/#post-7859126) * I’d love to hear any feedback on what exactly we could be doing better here. 🙂 * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WP REST API (WP API)] Filter by Post Date](https://wordpress.org/support/topic/filter-by-post-date/) * Plugin Author [Ryan McCue](https://wordpress.org/support/users/rmccue/) * (@rmccue) * [11 years, 11 months ago](https://wordpress.org/support/topic/filter-by-post-date/#post-5146641) * This is not currently possible, but we are [looking at adding it](https://github.com/WP-API/WP-API/issues/389) in a future release. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WP REST API (WP API)] Filterig for post_format?](https://wordpress.org/support/topic/filterig-for-post_format/) * Plugin Author [Ryan McCue](https://wordpress.org/support/users/rmccue/) * (@rmccue) * [11 years, 11 months ago](https://wordpress.org/support/topic/filterig-for-post_format/#post-5155267) * WordPress’ WP Query supports this through the `post_format` arg, but this is not marked as a public query argument. You can add the following to your site’s code to enable it as a public query argument, but keep in mind that it may cause privacy concerns: * ``` add_filter( 'json_query_vars', function ( $vars ) { $vars[] = 'post_format'; return $vars; } ); ``` Viewing 15 replies - 1 through 15 (of 77 total) 1 [2](https://wordpress.org/support/users/rmccue/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/rmccue/replies/page/3/?output_format=md) [4](https://wordpress.org/support/users/rmccue/replies/page/4/?output_format=md) [5](https://wordpress.org/support/users/rmccue/replies/page/5/?output_format=md) [6](https://wordpress.org/support/users/rmccue/replies/page/6/?output_format=md) [→](https://wordpress.org/support/users/rmccue/replies/page/2/?output_format=md)