Title: sslaughter's Replies | WordPress.org --- # sslaughter [ ](https://wordpress.org/support/users/sslaughter/) * [Profile](https://wordpress.org/support/users/sslaughter/) * [Topics Started](https://wordpress.org/support/users/sslaughter/topics/) * [Replies Created](https://wordpress.org/support/users/sslaughter/replies/) * [Reviews Written](https://wordpress.org/support/users/sslaughter/reviews/) * [Topics Replied To](https://wordpress.org/support/users/sslaughter/replied-to/) * [Engagements](https://wordpress.org/support/users/sslaughter/engagements/) * [Favorites](https://wordpress.org/support/users/sslaughter/favorites/) Search replies: ## Forum Replies Created Viewing 5 replies - 1 through 5 (of 5 total) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[JWT Authentication for WP REST API] Will not Authorize. Does Plugin work in WordPress 4.6 ?](https://wordpress.org/support/topic/will-not-authorize-does-plugin-work-in-wordpress-4-6/) * Thread Starter [sslaughter](https://wordpress.org/support/users/sslaughter/) * (@sslaughter) * [9 years, 9 months ago](https://wordpress.org/support/topic/will-not-authorize-does-plugin-work-in-wordpress-4-6/#post-8273037) * Semi Update/Hack for this. * The Validate endpoint was successful in our PRO environment (my local must have not had all the permissions set correctly in .httaccss), but when I tried to retrieve user information (using WP API v2) I would get an error message saying I had not logged in yet. Acting like the Auth was not being passed along to WP API v2 * I saw this on the wp-api-jwt-auth plugins github “issues” page: [https://github.com/Tmeister/wp-api-jwt-auth/issues/6](https://github.com/Tmeister/wp-api-jwt-auth/issues/6) * > Hey, thanks for this great plugin. I’m having an issue that I need to add: > add_filter( ‘rest_authentication_errors’, ‘__return_true’ ); > Which forcing WP API to skip the cookie authentication to get the JWT auth > work. Or the response will always be something like ‘rest_not_logged_in’ (status > 401). > Is it just me or it is the right way to get this plugin to work? > P.S. I’m using the latest WP API v2 beta 4 and the develop branch, both not > working without adding this filter. * After putting add_filter( ‘rest_authentication_errors’, ‘__return_true’ ); to my themes functions.php I can retrieve the user info – but there looks like some weird redirection is going on – but that is more of a WP API V2 issue than it is wp-api-jwt-auth’s * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Global Gateway e4 | Payeezy Gateway |] Hosted Checkout Error – Demo/test payment page not working anymore.](https://wordpress.org/support/topic/hosted-checkout-error-demotest-payment-page-not-working-anymore/) * Thread Starter [sslaughter](https://wordpress.org/support/users/sslaughter/) * (@sslaughter) * [10 years, 2 months ago](https://wordpress.org/support/topic/hosted-checkout-error-demotest-payment-page-not-working-anymore/#post-7366194) * Thanks, I got it resolved though. * My issue ended up being that by default the setting is “Live” instead of “Demo” when you initially install the plugin. It looked like it was a value for “Auto Submit Payment” because of the way the values are laid out in the settings page * x Auto Submit Payment Live or Demo : Demo * But it was just the “Live or Demo” value. * === Ignore the below if you want, it falls under “feature” request ====== * One thing it would be nice of you to work on is to make a separate “Save” button for the “Payment Page ID” and “Transaction Key” values. Right now there is just the “Generate HTML” button, which saves those values – and then stomps on the previous HTML Form value. * We have customized the HTML Form a little bit, so when I have to change the Payment Page ID from its DEMO value to its real value, I have to remember to first copy the HTML, and then edit to put it back in place. I’m pretty sure that sometime soon, someone else not knowing about this will go to change the “Payment Page ID”, and wipe out the form. * Also – to make the form code a “little” more portable – instead of hard-coding the plugin path for the confirm.php file in the forms “action=” tag you could use plugin_dir_url *