This is because password protection applied on get_the_content() function. And you are not using it instead you’ve written your own custom loop. So you can alter the code before loop and check if page is not password protected using function post_password_required() and then display form using get_the_password_form() else display loop. Example:- if ( post_password_required( get_the_ID() … Read more
If you are just wanting a simple “login” you could use htpasswd and htaccess. WordPress sites already have the htaccess in the main directory. Add an .htpasswd file at the same level as your root HTML folder. Example: . ├── public_html | └── wordpress | └── .htaccess └── .htpasswd Use a tool like htpasswd generator … Read more
This is straightforward. Hook on init to detect the lostpassword page If the user is not coming from your instructions page (which we defined by adding extra query parameter) he’ll be redirected to your custom page In your custom page add the link to lost password page including the extra parameter we set to skip … Read more
No, I would expect wp_user_update to have been what gets used, but I find your motives dubious, and cannot think of a reasonable use for what you want to do But if you really want to go down this path, use the pre_user_pass filter. I would also note that there is a reason why passwords … Read more
See ‘send_password_change_email’ filter hook. It is part of the wp_update_user() function, fired on admin or on frontend… So I think you can check if the update is done via the admin, then if true, deactivate the email this way… if ( is_admin() ) add_filter( ‘send_password_change_email’, ‘__return_false’ );
You don’t want to translate the title, so there’s no need to use __() here and you won’t translate ‘%s’, because that’s a placeholder. add_filter( ‘protected_title_format’, ‘remove_protected_text’ ); function remove_protected_text() { return ‘%s’; } should work.
You can’t. WordPress stores the passwords in the DB as hashes of the user password using a salt which is unique to the install. In an import situation (unlike full migration) you will probably not have the same salts in the new site and password validation will fail. You should just notify the users that … Read more
You’ve got almost everything you need already (assuming the above plugins that you listed work). You just need to link them: Activate pippins change password plugin & create a page with the shortcode for that in it. Test that that page allows a logged in user to change their password. Note the URL of the … Read more
Problem solved! I had a filter hooked onto random_password filter to generate passwords with custom rules and get_password_reset_key uses the function wp_generate_password to generate the key, and that is why I was getting the behavior I was getting. Allz I had to do was to remove my filter from it, and bada bing bada boom, … Read more
Sometimes you have to look at the name of the input you’re trying to pick up via $_POST. It’s not always consistent across forms. In the case of the WooCommerce password change form, the input name for the new password field is ‘password_1’ so that’s what you need to pick up via $_POST: function my_profile_update( … Read more