Tips and Tricks HQ Support Portal › Forums › WP eMember › WP eMember Troubleshooting › No email sent after auto-upgrade member level
Tagged: membership auto upgrade
- This topic has 6 replies, 3 voices, and was last updated 4 years, 5 months ago by admin.
-
AuthorPosts
-
May 26, 2020 at 7:22 am #13993sensizMember
We use ~ 6 membership levels and provide website content depending om membership level.
In eMember we setup an auto-upgrade membership and defined an email template for customers who get access to the new level. However, customers do not receive this email after an auto-upgrade. All other mails (order emails f.e.) are fine.
We already tried to install/setup a SMTP plugin but without any luck.
The domain in the sender address is equal to the domain name of the website. The SPF records are fine and the email is not in the spambox, we tested with different kinds of email addresses.
Any tips?
May 26, 2020 at 8:32 pm #80629wzpModeratorAre the memberships actually being upgraded at the expected time?
If you haven’t already done so, please enable the debug logs; and check them after an expected upgrade takes place. So you can see if the upgrade task is being carried out or not. The email issue could be just an email delivery related issue (so lets first try to pinpoint which one it is).
May 30, 2020 at 5:31 am #80630sensizMemberYes, the member upgrade are running fine, permissions are correct. There are 6 levels and each level is upgraded after 1 week and gives access to an extra website section.
I thought the debug log was enabled but it wasn’t. I enabled the debug and will get back here as after the next upgrade.
Thx for the update!
June 1, 2020 at 7:45 am #80631sensizMemberHi, yesterday the automatic membership level upgrade was done. The test user did go 1 level up, but without the email that should have been sent.
I have the following logs:
cronjob debug: empty
ipn handle debug: no recent records
eMember debug log:
[05/31/2020 5:44 PM] – SUCCESS :Authenticating login request for username: . Request came from IP Address: [removed]
[05/31/2020 5:44 PM] – FAILURE :Username value is missing. Cannot process this request.
[05/31/2020 5:45 PM] – SUCCESS :emember_membership_changed action hook handler. Retrieving user record for member ID: 9
[05/31/2020 5:45 PM] – SUCCESS :emember_membership_changed action hook handler. Member account is active. Invoking level specific autoresponder signup functionality.
[05/31/2020 5:45 PM] – SUCCESS :Performing membership level specific autoresponder signup if specified.
[05/31/2020 5:45 PM] – SUCCESS :End of membership level specific autoresponder signup.
[05/31/2020 5:45 PM] – SUCCESS :emember_membership_changed action hook handler. Updating user role if applicable
June 2, 2020 at 12:53 am #80632adminKeymasterThe cronjob events are logged in the other log file that has the keyword “cronjob” in the name (you can find it below the standard one). Please look at that one.
The cronjob is triggered on a regular interval and can add a lot of debug output. So we didn’t want to clutter the main log file with the items from the cronjob related events (there are a couple of cronjobs that are to do with account upgrade and expiry control).
June 6, 2020 at 12:46 pm #80633sensizMemberHi admin,
In my previous message I mentioned that the cron log is empty. Do I have 2 cronjob log files or did you miss my remark: cronjob debug: empty
This is what I see:
Enable Debug:
If checked, debug output will be written to log files. This is useful for troubleshooting failures.
You can check the debug log file by clicking on the link below (The log files can be viewed using any text editor):
eMember_debug.txt file
eMember_debug_cronjob.txt file
ipn_handle_debug_eMember.txt file
So, eMember_debug_cronjob.txt file is empty
Ciao, Petra
June 9, 2020 at 1:12 am #80634adminKeymasterTHere is only one cronjob log file (eMember_debug_cronjob.txt). The cronjob log file empty would be the issue. It means that the cronjob is not running on this site (something has messed it up).
Please do the following:
#1) Deactivate the eMember plugin from the plugins menu
#2) Then re-activate the eMember plugin. This should re-register the cronjobs.
#3) Install the following plugin and check the currently active cronjobs to make sure the emember cronjobs are also registered:
https://wordpress.org/plugins/wp-crontrol/
Do you see the emember cronjobs now registered to run? You can search for the keyword “emember” in that crontrol plugin’s interface to see if there is any emember ones there.
Also, do you have any caching that could be caching the log file?
-
AuthorPosts
- You must be logged in to reply to this topic.