Its nonsensical to lock activation, unless the functional part of your code remains on your site. You essentially can make a service that you hide behind a login or apikey (like akismet) which may or may not make sense for your plugin. Calling home for permission to activate is a terrible idea, because idealistically, it’s … Read more
Why in the first place you created custom tables? There is wp_usermeta table for storing any kind of extra data to build custom user profiles with extra fields. Also you can hook into native WP login process and allow logging in with email. What method of logging in you are using? Checking if user is … Read more
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
The answer to this question was simply that the built-in password protection does not apply if you are using a custom template that doesn’t include the_loop(). Lesson learnt.
http://wordpress.org/extend/plugins/members/ Looks like a good option, I trust his plugins. There are a variety of other plugins available if you search for members, private, access, or a combination of those terms
This is the line you’re looking for: $userdata = get_user_by(‘login’, $username); The get_user_by function calls WP_User::get_data_by and that function eventually executes this SQL: SELECT * FROM $wpdb->users WHERE user_login = $username The hashed password will be contained in the results of that query. Eventually, the wp_check_password function will be called to compare the hashes.
Figured it out! The new version of WordPress (3.4) changed the way the password protected pages worked. This should work for you now: <?php if ( post_password_required() ) { ?> <form method=”post” action=”/wp-login.php?action=postpass”> <p>This content is password protected. To view it please enter your password below:</p> <input type=”password” style=”margin:10px 0;” size=”20″ id=”pwbox-<?php the_ID(); ?>” name=”post_password”/></label><br/> … Read more
I haven’t looked into it, but any hook on the page that processes the new user registration will have access to the $_POST data and as such you could get it from there. I agree with the other comments above, you should be able to use use the WordPress hash and check the password on … Read more
Maybe this is not the answer you look for but giving one of below a try could maybe help you out?! Ofcourse you have FTP or SSL access. If you don’t have one of them, don’t bother to read any further! The good old make a backup from in this case functions.php before you start … Read more