The WP-Members™ 2.7.0 release introduced a major new feature to the plugin that was driven entirely by user request – admin customizable email messages for the various emails that are sent out by the plugin. If you are running 2.7, you will notice the addition of an email tab in the plugin’s admin panel.
Some users have indicated that after upgrading, they stopped receiving email notifications from the plugin. Note: these issues were only in the case of upgrades, not new installs; and not all upgraders were effected.
The problem in these cases is that the default messages failed to load during the upgrade process. You can determine if you were effected by looking at the email tab in the plugin’s admin panel. If the message areas are blank, you are effected. If they contain content, you should not be experiencing email issues and if you are, it is unrelated to this.
How can I fix it?
The fix for this is quite simple – fill out the emails. If you need something to get you started, I have put together a file that contains all of the default email content in plain text. This should allow you to copy/paste the defaults with no problems.
Note: only the fields for the emails you are using in your set up will show in the admin panel. For example, if you are not moderating registrations, the email fields for those messages will not show. So not all of the default messages in the file above will apply.
The defaults are intended to be a starting point for you and demonstrate the various shortcodes that are available for this function. A description of the shortcodes is here. I tried to keep them intuitive. (Note: some are only available in the admin email.)
Also, you are not required to use any of the shortcodes (although you probably will need the password shortcode so the user is emailed their password upon registration). If you want to hardcode a link into the message rather than use the reglink or members-area shortcodes, that is completely up to you. In adding this feature, I have tried to make it as flexible as I can.
As always, there are some small issues creeping up with the new release so I have already begun 2.7.1 as a fix release. That will include an updated install function that will hopefully correct this issue. It will force install the default messages if they are not there, but it will skip any that already have content. That way, we won’t be overwriting any customizations you have already made. That release should be available sometime later this week or early next week.
Hi Chad,
I have a new install and all the email fields are completed. Emails go to admin without any issue until I change the admin email to an email with the website domain extension. I am not sure if this is related or if there is anything else I should be checking. Any thoughts you may have would be appreciated. The email address receives all other emails sent. Thanks
The only reason I can think of that would cause that would be that your host restricts emails coming from scripts when the email address is from the hosted domain. Now, that doesn’t mean that is the case, but it could be. I would suggest trying a plugin that allows you to make a validated SMTP connection for wp_mail such as the WP Mail SMTP plugin.
Thanks Chad for quick reply. I will try as suggested and let you know.
Karen
Phew! Now I know why I haven’t been getting new user registration emails, and users haven’t been getting their password reset emails. Thanks for the fix Chad!
I can see 4 emails looking into the email definition in my WP-admin, but when I’m looking into your “a file that contains all of the default email content in plain text” I can see 5 emails defined – the first one in missing in my setup.
The only ones that show are the ones being used. So, for example, if you are not moderating registration, that email content field will not show on the panel.
Hope that helps.
Somehow my new users get a wrong password mailed to them.
I tried it myself and indeed the password shown in the mail does not work to login.
Does anyone have any idea how this is happening?
Are you using any type of caching plugin?
Yes still using W3TC, would that be the issue? since it used to work for a short while…
I would suggest testing without it.