WP-Members 2.9.9.1 update patch for 2.9.9

I have the last update but the admin notification doesn′t work!
Wordpress 4.1.1
Woocommerce 2.3.4
WP-Members 2.9.9.1

HELP!!!!

not getting member email notifications any longer since I upgraded to 2.9.9.1, nor are those “approved” are getting emails with passwords to access site. On latest WP, and ALL plugins are on the latest updates.

Please advise.
Thank you.

I’d a similar case, problem was on the domain level. I’d reached the limit of email sending. It was solved by creating an email account in my domain and setting it in the email tab for WP-Member configuration

Hope it is similar on your side.

I’m on WP 4.2 and WP-Members 2.9.9.1 as the only activated plugin, and admin notification + validation doesn’t work.

Let me add some clarity to people’s questions/issues with emails.

Yes, there was a problem with the 2.9.9 release and that was the reason for 2.9.9.1. That issue was specific to a change in a variable name and the 2.9.9.1 release corrects it. Aside from that, there are no issues in the plugin with regards to emails.

The plugin sends all emails using the wp_mail function.

If emails are not being sent/received, it is not necessarily an issue with the plugin. The plugin will generate an email and will fire the wp_mail function. At that point, it is out of the plugin’s and WP’s hands.

It is important here to point out that there is a difference between emails not being sent and emails not being received.

Let’s start with email not being sent.

Just because wp_mail generates an email and attempts to have it sent does not mean that the email will in fact be sent. There are a number of reasons emails may be rejected for sending.

As @chasky pointed out, one reason is that you (or your shared server) is at capacity. Other possibilities could be that your host disallows the sending based on rules they may have in place. Some possibilites are your sending address does not match your assigned, improperly configured headers, throttling emails due to spammers on the system. If you are on shared hosting, you are kind of at the mercy of what else is going on on the server with other sites.

In these types of cases, an email was generated and wp_mail attempted to send it. But it is rejected at some point after that. Take a look at the notes on the wp_mail function for more information on these possibilities.

Just to make your life more complicated, after an email is sent, there are many possibilities a receiving email host may reject it before it ever gets to the user.

Some of these cases may be similar to reasons it might not ever be sent, such as the sending address not matching the domain. It could also include the sending IP being blacklisted (if you’re on a shared host, again, this might not necessarily be related specifically to you – but it affects you). These are just a few of the possibilities.

So how do you deal with this and make your email more robust?

I highly recommend that you send email through SMTP. (I also recommend that you have your own email service that is outside of your site hosting, but that’s another discussion.) You can do this with a plugin or you can set up your own script to handle it. Either way, this will make your life with email much easier.

When using SMTP, not only will your emails be more reliable, but you’ll have better access to information about troubleshooting. If you send via your web server, you are at the mercy of your host with troubleshooting information and if it is shared hosting, good luck getting them to go through server logs to see if your email is even being sent at all. SMTP will bypass that problem and you’ll have better access to information that may help you should emails be failing.

If you can’t/won’t use SMTP, there are still a number of steps you can take to make things more robust. First, check with your host regarding their rules for sending script-based emails. And once you know what those are, make sure you comply with them. Another little trick that may help is to make your email’s return path in the header the same as the “from” address.

I have a number of posts on my personal blog about troubleshooting, understanding how script-based email works (or doesn’t work), and some things you can do to get things working.

• Working with the WordPress wp_mail function
• Troubleshooting WordPress wp_mail configuration
• Testing your wp_mail settings
• Changing the wp_mail address with a simple plugin
• Changing the wp_mail from address without a plugin
• Change WordPress email settings to reduce spam rejection
• Easy SMTP email settings for WordPress

These posts cover the most common possibilities.

I would add that it is 2015, SPF is everywhere, and if you violate an SPF rule or spoof an email (use a sender address that’s not yours), the big services (Gmail, Hotmail, and Yahoo) will often drop your email without warning or error.

Use an SMTP plugin.

Thanks for all the clarification about emails in WP, but I’m still not able to have admin moderation of new user subscriptions work.

When a new user subscribes to my website, I expect :
– Admin receives notification email defined in WP-Members “Emails” tab
– User receives notification email defined in WP-Members “Emails” tab

What happens instead :
– Admin receives usual WordPress notification email “A new user has subscribed to your website + login + email.
– User receives usual WordPress notification email “Your login and password + login + pass”

So in my case at least, wp_mail() works, and WP-Members subscription validation by admin doesn’t.

So in my case at least, wp_mail() works, and WP-Members subscription validation by admin doesn’t.

Actually, based on your description of the emails received (which are the WP defaults), it’s not that the WP-Members emails are not working. It’s more likely a case that they are not being used, which would be the case if you are not using the WP-Members registration form.

If you use the WP default registration, then you’ll get the WP defaults. If you are using another plugin that uses its own front end registration (hooking into WP or otherwise), same thing – WP-Members isn’t going to fire its emails.

To address the question of why not, that’s because there are just too many other possibilities of what the process might be and for WP-Members to assume that it should override that other process would create many problems the other way (like “I need the welcome email from {some plugin}, why does WP-Members jump in front of this?”).