Regarding the update part in your question: I think the problem here is that you’re missing the number of accepted arguments in your add_action() setup. If you check out the Codex, the usage is: add_action( $hook, $function_to_add, $priority, $accepted_args ); where by default $priority = 10 and $accepted_args = 1. So your code snippet should … Read more
You can add an extra help message box, on the reset password screen: with the following: /** * Display an extra help message box on the ‘reset password’ screen * * @link http://wordpress.stackexchange.com/a/204429/26350 */ add_action( ‘validate_password_reset’, function( $errors ) { add_action( ‘login_message’, function( $message ) { // Modify this help message box to your needs: … Read more
you can Disable users activation email: https://buddypress.org/support/topic/resolved-disable-users-activation-email/ and there is plugin to do its: https://timersys.com/free-plugins/bp-disable-activation-reloaded/
WordPress itself provides you with a function called register_new_user() which can be used to create a user-account in your WP instance. You will have to write some kind of integration between your Firebase DB and WordPress but this function would probably be the way to go.
You might need this plugin: http://wordpress.org/extend/plugins/no-disposable-email/
You can use user_register add_action(‘user_register’, ‘wpse42506_user_register’, 10, 3); function wpse42506_user_register( $user_ID ) { // do stuff here } If you want to just use the user information, you can use get_userdata http://codex.wordpress.org/Function_Reference/get_userdata If you need more control, you can initiate a new WP_User http://codex.wordpress.org/Class_Reference/WP_User
I had to do something similar. What you need to do first is in each of your config files define the table prefix … make sure that they are different. Example: WordPress installation 1: wp123_ WordPress installation 2: wp124_ Your first installation would be your main installation the one with the user table you want … Read more
With that in functions.php you’d probably have to declare $error to be global like so : if (‘POST’ == $_SERVER[‘REQUEST_METHOD’] && !empty($_POST[‘action’]) && $_POST[‘action’] == ‘registration’) { global $error; $error = new WP_Error(); // the rest of your code And then do global $error; again on your registration page before trying to use it. But … Read more
Here is a function I’ve Used Before: function registration_form_wpa95139(){ if (is_user_logged_in()) return; ?> <div class=”Registration”> <div id=”register-form”> <div class=”title”> <h1><?php _e(‘Register your Account’); ?></h1> <span><?php _e(‘Sign Up with us and Enjoy!’); ?></span> </div> <form action=”<?php echo site_url(‘wp-login.php?action=register’, ‘login_post’) ?>” method=”post”> <input type=”text” name=”user_login” value=”Username” id=”user_login” class=”input” placeholder=”Username” /> <input type=”text” name=”user_email” value=”E-Mail” id=”user_email” class=”input” placeholder=”E-Mail” … Read more
So user_register is when the post data for user registration is submitted. Can you try this if ( isset( $_POST[‘first_name’] ) ) { $first_name = $_POST[‘first_name’]; } Ditto for last_name. I looked up the codex for the user_register hook, check the example.