Forum Replies Created
-
Posts
-
Your naming conventions do allow me to find your cron jobs.
However, I have no way of knowing what tasks might be missing. Hence my request for the list, and that particular web page is a logical place to put it…
Do you create only those two cron jobs, period? Does eStore have any scheduled tasks?
Help! Where do I go next?
You wrote, “Given the condition you have set, I would say the expiry notification should trigger on the 10th or 11th (21 days to end of 31st December).“
The event was not triggered at 11:39am on Dec 9th.
The event was not triggered at 11:45am on Dec 10th.
The event was not triggered at 1:20am on Dec 11th.
Note: we have 200+ members in membership level 3 whose accounts will expire on Dec 31.
[12/09/2019 11:39 AM] – SUCCESS :Auto expiry email notification feature is enabled. Checking user account expiry details…
[12/09/2019 11:39 AM] – SUCCESS :Checking membership level: 3. fixed date : 2019-12-31
[12/09/2019 11:39 AM] – SUCCESS :Checking membership level: 5. fixed date : 2019-12-31
[12/09/2019 11:39 AM] – SUCCESS :===*** wp_eMember_auto_upgrade() Start ***===
[12/10/2019 11:39 AM] – SUCCESS :Auto expiry email notification feature is enabled. Checking user account expiry details…
[12/10/2019 11:39 AM] – SUCCESS :Checking membership level: 3. fixed date : 2019-12-31
[12/10/2019 11:39 AM] – SUCCESS :Checking membership level: 5. fixed date : 2019-12-31
[12/10/2019 11:39 AM] – SUCCESS :===*** wp_eMember_auto_upgrade() Start ***===
[12/11/2019 1:20 AM] – SUCCESS :Auto expiry email notification feature is enabled. Checking user account expiry details…
[12/11/2019 1:20 AM] – SUCCESS :Checking membership level: 3. fixed date : 2019-12-31
[12/11/2019 1:20 AM] – SUCCESS :Checking membership level: 5. fixed date : 2019-12-31
[12/11/2019 1:20 AM] – SUCCESS :===*** wp_eMember_auto_upgrade() Start ***===
PS: I just reset the notification to 19 days before, so that should be tomorrow…
Progress report: You wrote, “Given the condition you have set, I would say the expiry notification should trigger on the 10th or 11th (21 days to end of 31st December).”
The event was not triggered at 11:45 on Dec 10th.
I changed the run time to 6:15 in the morning, and I will check again on Dec 11th.
Questions: How is time-of-day handled, and does it affect the renewal notices?
Or, is time-of-day simply ignored?
* My time zone = GMT-5
* My server time zone = GMT-6
* I configured eMember to use the WP default time zone
I do not know if the time-of-day is recorded when a member joins, or if it affects when the reminder is set.
Bottom line: When the cron job runs tomorrow at 6:00, will any membership due to expire on Dec 31 be sent a notice regardless of time-of-day when the account was created?
Please confirm that the correct script is installed (and running) to create and send the advance notification:
I found two scrips with the word “eMember” in the Hook Name. They are both scheduled to run once a day:
* wp_eMember_email_notifier_event
* wp_eMember_scheduled_membership_upgrade_event
PS: Thank you for introducing me to the cron job tool. Kudos for the information, and the video, on the link you included. Well Done!
Thanks.
I have been tracking the cron logs every day. That part seems to be working. I have not seen this message this month: “The following users will receive the before expiry email notification”
This morning I reset the “Number of days before the account expiry when the reminder notification is sent (default: 10 days)” to 21.
All memberships expire 2019-12-31 – when will the cron job initiate notifications?
12/31 – 21 = Dec 10th? Dec 9th? Dec 11th?
(The cron job apparently runs at 11:30am-ish my time, if that makes a difference on the date of notification.)
I will open the logs after 1:00pm for and tomorrow, then search for the phrase “following users will” and the single word “reminder”.
_______________
[12/07/2019 11:41 AM] – SUCCESS :eMember cronjob – wp_eMember_auto_migrate()
[12/07/2019 11:41 AM] – SUCCESS :eMember cronjob – wp_eMember_cron_email()
[12/07/2019 11:41 AM] – SUCCESS :End of wp_eMember_cron_email() function
[12/08/2019 11:43 AM] – SUCCESS :Auto expiry email notification feature is enabled. Checking user account expiry details…
[12/08/2019 11:43 AM] – SUCCESS :Checking membership level: 3. fixed date : 2019-12-31
[12/08/2019 11:43 AM] – SUCCESS :Checking membership level: 5. fixed date : 2019-12-31
[12/08/2019 11:43 AM] – SUCCESS :Checking membership level: 6. fixed date : 2020-12-31
[12/08/2019 11:43 AM] – SUCCESS :Checking membership level: 7. fixed date : 2020-12-31
[12/08/2019 11:43 AM] – SUCCESS :Checking membership level: 8. fixed date : 2021-12-31
[12/08/2019 11:43 AM] – SUCCESS :Checking membership level: 9. fixed date : 2021-12-31
[12/08/2019 11:43 AM] – SUCCESS :Checking membership level: 10. fixed date : 2022-12-31
[12/08/2019 11:43 AM] – SUCCESS :Checking membership level: 11. fixed date : 2022-12-31
[12/08/2019 11:43 AM] – SUCCESS :===*** wp_eMember_auto_upgrade() Start ***===
[12/08/2019 11:43 AM] – SUCCESS :Checking member profile with member ID:1, Username: Micky
[12/08/2019 11:43 AM] – SUCCESS :
End of foreach (Member ID: 1)
(etc…)
Where do I begin trouble-shooting?
I thought we had everything configured properly, but it didn’t work…
All our accounts expire on Dec 31, 2019. (My personal membership expires on that date, too, so I should get a reminder.)
We enabled “Enable Auto Expiry Email Notification”
(Dashboard>wpEmember>Settings>General Settings)
We modified the renewal email, and selected 30 days before expiry
(Dashboard>wpEmember>Settings>Email Settings)
I understand that the renewal notices are sent out as a single message with BCCs.
We have 250 members. Because our web provider ignores messages with over 50 recipients, we installed a plugin to route outgoing mail through a gmail account. (The plugin seems to work for other notifications.)
However, I did not know how to calculate date and time of day when the notices will be mailed. (e.g. Nov 30, Dec 1, Dec 2 – midnight? – noon?)
Today is 25 days before the accounts are due to expire. No notices have been received. Where do I begin trouble-shooting?
* Can I manually trip the “send” function, or do I need to reset the number of days?
* What time of day is the message sent? The log file says the cron job runs at 11:something AM.
* Is there something in a log that indicated that something has been sent?
Where do I go next?
Thank you!
FYI, I had to do only a few things to recover from my early misconceptions about the fixed expiry date:
* Rename & add membership levels
* Rename & add PayPal payment buttons
* Edit one page (“Renew”) to change shortcodes
That was done once. Future changes:
* Annually: Edit PayPal payment buttons for new membership levels (everything else falls into place)
* By 2022, add new membership levels for 2023, 2024, etc.
___Details___
__Here are the specific steps I’ve taken in Membership Levels:__
Renamed level “Member” to “2019 Member” (Expire date remains 12/31/2019)
Renamed level “Family Member” to “2019 Family Member” (Expired date remains 12/31/2-19)
Added “2020 Member” (expiration date 12/31/2020)
Added “2020 Family Member” (expiration date 12/31/2020)
Added “2021 Member” (expiration date 12/31/2021)
Added “2021 Family Member” (expiration date 12/31/2021)
The membership levels now look like this:
2021 Member
2021 Family Member
2020 Member
2020 Family Member
2019 Member
2019 Family Member
Lifetime
Family Member (Pending)
Our Membership Director can choose only ONE of those from the pull-down menu. Obviously, if a member is paid through Dec 31, 2020, then their membership level will be “2020 Member.”
__I modified the payment buttons__
Renamed button “Family” to “Family Join”
Renamed button “Individual” to “Individual Join”
Added button “Family Renew”
Added button “Individual Renew”
We now have 4 paypal buttons:
Individual Join (pays 2019 Membership)
Individual Renew (pays 2020 Membership)
Family Join (pays 2019 Membership)
Family Renew (pays 2020 Membership)
__Page edits__
The “Join” page is unchanged and new members will have the 2019 membership
The “Renew” page now has PayPal “renew” buttons to pay for 2020 memberships
__Scheduled (Future) actions__
Jan 1, 2020: Change the “Join” PayPal buttons to pay for 2020 memberships
Fall (TBD), 2020: Change the 2 “renew” PayPal buttons to pay for 2021 memberships
Rick Jaggers (MyWP2.com)
You answer is confusing because the setup “I have now” does not have any NEW levels.
Is this the setup that “looks fine?”
__________|___________________________
1. Member | 2019-12-31
2. Family Member | 2019-12-31
3. Member (2020) | 2020-12-31
4. Family Member (2020) | 2020-12-31
5. Member (2021) | 2021-12-31
6. Family Member (2021) | 2021-12-31
7. Lifetime | No Expiry or Until Cancelled
Family Pending | No Expiry or Until Cancelled
WE DON’T HAVE THAT SETUP. It’s what I’m proposing as a solution.
I *think* you are saying that my next step should be to add those levels: 3-4-5-6.
I *think* the step after that would be to set up PayPal buttons to match each of the 4 new levels, then rotate those “Buy Now” buttons at the end of the year.
Yes? No?
My apologies for any confusion.
Our membership schema was put in place 5 months ago, and we added 300 members to a plan that ends on a specific date (Dec 31st). New members have already signed up online, and their expiration date is also Dec 31st.
__Here are our current membership levels__
Level Name: | Subscription Valid for:
Member | 2019-12-31
Family Member | 2019-12-31
Lifetime | No Expiry or Until Cancelled
Family Pending | No Expiry or Until Cancelled
Here are the pages that are already built and working:
[Join Us] pinellasgenealogysociety.com/member-login/join-us/
[Renew] pinellasgenealogysociety.com/member-login/renew/
All of this was built on wrong assumptions. Now I’m trying to recover.
The solution I was trying to describe is this:
_______________|___________________________
Member | 2019-12-31
Family Member | 2019-12-31
Member (2020) | 2020-12-31
Family Member (2020) | 2020-12-31
Member (2021) | 2021-12-31
Family Member (2021) | 2021-12-31
Lifetime | No Expiry or Until Cancelled
Family Pending | No Expiry or Until Cancelled
I will have to rewrite the “Join Us” and “Renew” pages so that only the current membership is shown, and short codes are the only tool I have for that.
Before I start making those changes I would like reassurance that is that BEST way for me to proceed.
* Do I have the correct understanding of how to do this?
* Are these multiple levels the easiest way to go?
— Rick
_____
PS: I cannot see how to use the existing eMember dashboard tools to do what you suggest: “When the members are renewing, they will get put into this new level which gives them access until the expiry date of the following year.” That needs to be automated and not repeated manually 300 times. I’m off to read about that…
I understand how that solution works for manual renewals.
Question: How do you automate that solution if a member renews online before 31 Oct?
Problem resolved, but it took too much digging around.
It appears that I can install this WordPress SMTP plugin (https://wordpress.org/plugins/easy-wp-smtp/) and configure it so that all outgoing email is routed through a remote sever (gmail.com) but still retain my webmaster name and email address.
Now, I won’t have to worry about any limitations imposed by my hosting provider. No need to throttle…
FYI, it’s worse because I have learned that eMember uses a single BCC to notify members, which means NONE of our members will be notified.
Please consider adding that functionality to eMember. I can envision settings:
Maximum BCC Renewals per message: [_] 50 [_] 100 [X] Unlimited
Email Frequency [_] per hour [_] per day [X] Unlimited
According to https://support.tipsandtricks-hq.com/forums/topic/not-receiving-emails-even-though-the-plugin-sent-the-email I have to install a 3rd-party SMTP plugin. That page was started 8 years ago. How current are those recommendations?
— Rick
