Search Results for: short code

wpmem_logout_link

Description

This filter hook allows you to change the URL that is used to log a user out. The default link is the result of the WP function home_url() plus the /?a=logout querystring, such as http://yoursite.com/?a=logout.

If you need/want to change this URL to something else (such as using the WP default logout process or some other process), this hook will allow you to change the link returned for logout.

This link is used by the sidebar widget, the display status function, and in the logged in state of various shortcode pages (login and register).

Useage

add_filter( 'wpmem_logout_link', function ( $string ) {
	return "https://mysite.com/?a=logout";
});

Reset password with just email

Chad Butler · Jan 27, 2014 ·

NOTE: if you are using version 2.9+, there is a new set of code snippets using some new filter hooks that make this process easier.

One of the requests I get most often is how can I change the plugin to have the password reset only require the user to give their email address. This especially comes up when people customize the process to use the person’s email address as their username, since a password reset form with “username” and “email” doesn’t make much sense in that situation.

Well, since version 2.8.5, there has been a filter hook in the password reset process that allows you to filter the arguments that are passed in order to reset the user’s password – wpmem_pwdreset_args. There are two stages to this demonstration, and thus two parts of the code snippet. First, we only need a form requesting the user’s email, so we will remove the “username” field from the form. Second is filtering the arguments of the password reset process so that the user’s password can be reset with only the email provided. Continue Reading →

A random word and number combination for passwords

Chad Butler · Jan 22, 2014 ·

One of the earliest code snippets provided on this site was one that discussed how to create an easier random password. This post discussed two examples: one that showed how to create a random password of only upper and lower case letters and one that always set a specific word.

I understand that some sites have users that are not very computer savvy, and I often get the question of how does one generate a random password that is both secure and easy to use. So, I came up with this little example.

This code snippet will generate a password that is a combination of a random word and a random 2 digit number. This allows you to generate random passwords that will be easier on the user and still have some level of security. Continue Reading →

WP-Members 2.8.9 release

Chad Butler · Dec 31, 2013 ·

This article is provided free. Find out how you can get full access to premium content, including how-to articles and support forums, as well as priority email support and member exclusive plugin extensions..

I had initially expected that 2.8.8 would wrap up 2.8.x and the next release would be begin 2.9. But it looks like we need one more update to get through the period before 2.9 will be ready.

2.8.9 contains a couple of fixes, some updates to deal with the new Twenty Fourteen theme, and some updates that will help users transition to 2.9 (which will be rebuilding the form building functions). Continue Reading →

Workaround for WP-Members front end login when using a CAPTCHA device on the WP login form

Chad Butler · Dec 20, 2013 ·

If you using a plugin to implement a CAPTCHA on the WordPress login form (the backend login, wp-login.php), you will find that this is not always compatible with the WP-Members front end login.

WP-Members includes WP’s native hooks such as login_form for broad compatibility with plugins that may add additional authentication to the login. But these are not always compatible with WP-Members or with front-end logins in general.

If the third party plugin does not load its scripts on the front end, it will not be compatible. If you are getting failed logins with strange error messages (such as “human verification incorrect” or something like that), then the issue is likely that a third party CAPTCHA is being used, but cannot authenticate on the front end of the site.

What happens is that in order to implement the CAPTCHA, the plugin must remove the function wp_authenticate_username_password from the authenticate process with remove_filter. This allows the plugin to implement its own authentication that includes not only username and password, but also will validate the CAPTCHA.

This creates a problem since WP-Members also uses WP’s authentication to log a user in. Because the WP-Members form will only be passing two parameters, username and password, and the authentication is now requiring the addition of a third parameter (the CAPTCHA) that is not included in that form, the login will fail.

There are ways to work around this.

Continue Reading →