I guess you don’t have code on your new login form that supports ?action=lostpassword ? Your choices are either copy the relevant code from wp-login.php to your new form; you want the retrieve_password() function. Then you can post back to /login?action=lostpassword. use your own ‘lost password’ form, but post to /wp-login.php?action=lostpassword hook the lostpassword_redirect filter … Read more
What about filtering the_content? function se365701_require_email ( $content ) { if ( is_page( ‘require_email’ ) ) && !isset( htmlspecialchars( $_COOKIE[‘submitted_email’]) ) { return $form; // your MailChimp Form Code } else{ return $content; } add_filter( ‘the_content’, ‘se365701_require_email’ ); Note that your form provide itself may have a cookie or you may need to set it … Read more
Thank you that helped me alot! But there was one more problem and that was the “‘Authorization’ => ‘Basic ‘, $apiKey,” part. I just needed a dot before $apiKey. Thanks again for your help!
You could hook into the login process in the WP site and create a unique token (stored in meta) for that user on login. The token can then be sent to the other server, that could query the WP API with that token. You would have to create a custom endpoint that validates the user … Read more
If you’re looking to restrict the ability to view pages or posts to those that have a specific role, you can use the method described here: https://wpti.ps/check-if-user-has-specific-role-or-capability-in-wordpress/ You could create a custom role for those that need access and then check for that role using the custom function in the link above. If going that … Read more
Out of the box there is no mechanism for a user to login via the REST API to begin a session without pre-configured access. WordPress Core provides 2 authentication methods for the REST API: cookies + nonces application passwords Likewise there is no mechanism for registering for an account via the REST API, user creation … Read more
You should use cookie based authentication instead of basic auth. Delete the basic auth/application password authentication code. Follow the cookie authentication example that creates a post via the REST API from the REST API handbook: https://developer.wordpress.org/rest-api/using-the-rest-api/authentication/#cookie-authentication Create a valid nonce for use in your AJAX requests in PHP wp_create_nonce( ‘wp_rest’ ) as the docs tell … Read more
I tend to use template_redirect action to check, if a user has access to certain content, e.g. a page. To me, it is the most logical and straightforward place to handle the checking. As per the docs, https://developer.wordpress.org/reference/hooks/template_redirect/, the action, Fires before determining which template to load. Also the WP object has been already set … Read more
Simple Facebook Connect uses this exact registration widget. http://wordpress.org/extend/plugins/simple-facebook-connect/
Maybe it is too late to hook on init. Try set_current_user or some earlier hook. List is here: https://codex.wordpress.org/Plugin_API/Action_Reference