Membershipworks and Powerpress

I don’t think the code fixed your issue. We tweaked the code to look for an @ sign in the login address before using your logic, that way otherwise regular wordpress plogin names would still also work.

ref in powerpress-feed-auth.php in recent versions:

				if(  strpos( $user, '@', 1 ) !== false ) {
				$userObjID = get_user_by( 'email', $user); // Get the user by email
				if( !is_wp_error($userIDObj) )
					$user = $userObjID->user_login; // Use the user's login (not email) to authenticate
			}

I personally looked into this and I thought I emailed you the final changes based on your feedback. We tweaked it to use the get_user_by() function but only if we found an @ sign in the username.

I am still not sure this code was ever needed. If you look at the code in wp_authenticate in WordPress it uses the “get_user_by” function call. I just re-studying this with WordPress 5.2.2 to confirm…

The wp_authenticate() function calls filters including: wp_authenticate_username_password and wp_authenticate_email_password. The filter wp_authenticate_email_password uses get_user_by with email passed as a parameter. So as long as the username is the user’s email address, the 2nd filter will be handled. From my testing this is the case as well. The only reason this may not be working is if you have a plugin manipulating these filters. In this case the logic we added for you should work, again as long as the username has an @ sign in it which is required for an email address.

When you use the current logic in PowerPress, do you get the error: ERROR: Invalid username, email address or incorrect password.

If you do, then something is manipulating the filters mentioned above. If you do not, then things are working correctly as far as the wp_authenticate() being able to locate the account by email or username. This code in wp_authenticate() can be found in file wp-includes/pluggable.php, line 521-562.

One other thought, your membership plugin may be replacing the pluggable.php with their own wp_authenticate() function. You may want to grep/search the code in the membership plugin to confirm this. If this is the case, you should be able to add this logic you are referencing in the membership plugin’s wp_authenticate() function.

Thanks,
Angelo

Angelo,

Thanks for the prompt reply. Well, you are probably right about updating the code from what I pasted. I remember that conversation but can’t find that email in my user stream.

I will check with membershipworks about pluggable.php although I rather doubt they do.

When we do this in powerpress, the error is Wrong Password on the Activity Log plugin that we are using.

• This reply was modified 5 years, 4 months ago by tedstur.

So, I have confirmed that they do not modify wp_authenticate() and the server is not using FASTCGI.

Hello @tedstur,

Did you say some logins work and some do not? If some accounts work then there is not an issue with the server, the issue is with the roles and capabilities.

Thanks,
Angelo

Still a problem for me…

Here is my status:

No logins are working at all. Not even admins.
I have disabled all Plugins that affect member access. There were four of them that I could find. Still no luck.
The regular, unprotected feed works fine.
Under “Protect Content”
Require user to be signed-in to access feed. <– Checked
User must have the following capability: Premium Content
Under User Role Editor:
Premium Subscriber Role exist and has premium_content, read, read_feed, and read_feed_source checked

What can I check to debug this??

I have to get this fixed. How can I sign up for some paid assistance with this?

Please help.

I have turned off the Membershipworks plugin. I cannot log into password protected feeds.

Please go here:
https://www.blubrry.com/contact/
Click the Select link underneath All Other Inquiries and choose Technical Support. Fill out the form with your questions and someone will get back to you with assistance.