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
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.
Are you formatting the mysql2date() input string as ‘Y-m-d H:i:s’, as specified in the Codex? Also, why not use this same format as $date_format? EDIT: What output do you get for $last_login? The second argument in human_time_diff() is optional. Why not just omit it? That way, if you get valid output from $last_login, you should … Read more
Yes, you can safely ignore it, especially if your site has no “admin” user. The brute-force attack will never accomplish anything. I also use Limit Login Attempts – mainly for this very purpose. It lets me know when manual brute-force attempts are being made on my back-end login. (Last time I bothered to WHOIS the … Read more
The problem is that this function is normally used in the backend. To use it in the frontend, you need to add the following filter: add_filter( ‘auth_redirect_scheme’, ‘wpse16975_check_loggedin’ ); function wpse16975_check_loggedin(){ return ‘logged_in’; } Then auth_redirect() will work as expected : redirect users to the login form if they are not logged in.
I figured this one out finally. It turns out that the data in the wp_usermeta table for user_id=1 (admin) was corrupted. This was apparently causing the SSL redirect issue when trying to login to any domains. Once I restored the proper data for user_id=1 into wp_usermeta, everything worked fine. I would much rather have WordPress … Read more
The action wp_login_failed fires when there’s a failed login due to a faulty username/password combination. So that’s a good place to start. This is a super simple example that just redirects to the home page. <?php add_action( ‘wp_login_failed’, ‘wpse25628_login_failed’, 10, 1 ); /** * Catches all failed logins and redirect them to the * websites … Read more
If you are using a newer version of WordPress, you’ll see that you can’t both edit the same page/post because it will show that as locked (you can take over though). I agree that a separate admin account would be good. WordPress is designed to support many users logged in and active. The only issue … Read more
4.0 made a change to the structure of the authentication cookie and added a “token” feild to it. I assume that you were logged out because your older style cookie didn’t match the new format.
Wrangled up some things to check: @otto via comment on this post Look at the login page’s HTML source. Is there anything at all before the initial DOCTYPE line? Even a blank line? If so, then you have some piece of code creating output before the headers are made, in which case this prevents it … Read more