What initiates the Auto-Expiry Email?

[woodwardmatt]

Hey Guys,

I have gone through an implemented eMember onto a clients site. I have been able to test the registration and approval processes, along with using content protection as well. However, I’m still a little lost on the expiry process.

I can manually expire my account (to test) then when trying to access protected content I am (quite rightly) told to renew my account and pointed at the renewal page. However, I’m trying to look at this from a members point of view who (perhaps) may not visit the site for a week or two, during which period their membership expires. What controls the email being sent to that member so that I can test it for my client? I couldn’t see any cron jobs having been created, so I’m gathering this is not entirely “automated” but rather triggered by a user event at some point.

Could you clarify how this works within eMember?

Many thanks,

Matt

[admin]

There is a cronjob but you won’t be able to see it as it is created withing WordPress. Every night it checks for all accounts that are about to expire and it sends the email according to the settings in the “Expiry Email” section.

[woodwardmatt]

Ahh great thanks for the extra info Which file would I need to change if I wanted to change the time the reminder went out?

E.g. The client site is hosted in Canada but is for a membership base in Australia. I’m just trying to figure out which clock will be used for the timing of the email.

[admin]

The plugin will use GMT time for all things related to time. If you want to change that then this post should help:

https://support.tipsandtricks-hq.com/forums/topic/setting-a-different-timezone-for-time-calculation-in-the-plugin

[woodwardmatt]

Excellent! Thank you very much I’ll just give it a whirl and see how it turns out!

Matt

[woodwardmatt]

I’ve just had my expiry email through at 15:45 having set the Timezone to Australia/Adelaide. Not sure if that’s quite right or not but hey it came through so its a good start

I did spot that the {first_name} and {last_name} codes are not being replaced however. The codes have not been altered in anyway and I have had initial registration emails with information replaced correctly. Any thoughts on why this would not work for the expiry email?

[admin]

The {first_name} and {last_name} tags do no work on the mass expiry notification email as the same email is sent to all the members whose account is about to get expired. Use a generic email text there… for example:

Hi, Your account will expire soon.....

[woodwardmatt]

Ahh ok, thanks for the help

[woodwardmatt]

**ignore** – duplicate post

[Author]

Posts