I think that it’s rare for a plugin to make a direct DB connection, for the very reason you’re citing (among others, like port concerns, DB security best practices, etc.). In most cases, if you want your plugins to connect to an external data source, it’s best to do it using an API. So you’d … Read more
I would approach the situation like: Create an user with subscriber role. Add a meta field to the user profile. This will be the password like field you will verify the user against. Use AJAX to verify the password(meta value) entered by the visitor and display product specification accordingly. You do not have to worry … Read more
If you have access to the database, through phpMyAdmin or otherwise, you can change the email address in the ‘wp_users’ table. (your table may have a different prefix)
I think you’re looking for the retrieve_password_title filter. For example: add_filter( ‘retrieve_password_title’, function( $title ) { $title = __( ‘WPSE Custom Password Reset’ ); return $title; } );
WordPress cannot resend the existing password, because it does not know the existing password. Passwords are not stored as plain text, they are stored using a one-way hash. They cannot be decrypted and resent. They can be reset to something entirely new, and you can send that, but you can’t send what you don’t know … Read more
Don’t do it? Passwords meant to be remembered not stored, and once you store them in extractable format (i.e. without hashing or other sort of many to one transformation) they become a less effective security measure. As with any security related question, you have to start with defining what is it that you trying to … Read more
The easier way can be have a group of users called teachers and give just the teacher’s group the permission to visit the page. There are many plugins for permission handling and grouping users so you’ll just need to search WordPress plugin repository. Just an example: groups plugin Another possible answer can be : multi … Read more
I really don’t see the point of “launching” a website that is still in development, only to be seen by the developers and the client. By all definitions, that’s not ‘launching a website’ 🙂 If the client can accept the fact that the website is still in development and the launch part takes place only … Read more
You have to get user’s hash (hash is encrypted password) from the database: get_currentuserinfo(); $user_hash = $current_user->user_pass_md5; Then check if it’s correct: wp_check_password( $password, $user_hash, $user_id ); $password – Plaintext user’s password from input $user_hash – Encrypted password from database $user_id – user ID I guess But as Mark said in comment – this is … Read more
The login page is a horrible mess mixing functions with output the way it does. It makes projects like your unnecessarily difficult. It is actually better now that is used to be. You can cheat around the problem with output buffering: ob_start(); include(‘wp-login.php’); ob_end_clean(); Of course, the page still gets generated so it is consuming … Read more