Forum Replies Created
-
Posts
-
I have now confirmed this issue again by setting a test account to expire today (a couple days ago I set the expiry date for the account to be today, to ensure that it would be automatically expired by the system).
The account has now been automatically set to expired by the system, and yet the expiry email was not sent.
Can someone please help to resolve this issue? This is a critical issue for us, as the expiry emails are not being sent when an account expires.
Sorry, I’m not quite following how the other thread is related to this?
That thread is discussing the time of expiry and the “X days after expiry” email.
What I have reported here is that the “Day of expiry” (or “Day after expiry”) email (the email that should be sent when the account expires) is not being sent at the proper time. Rather it is being sent 10 days after expiry. This is resulting in members having their accounts expire without them knowing it.
I have just confirmed again that this is the case. The most recent batch of that email was sent yesterday evening, Oct. 28th, and yet all of the accounts to which it was sent expired on Oct. 19th.
Again, this is NOT the “X days after expiry” email, but rather the “Email After Account Gets Expired” email (“day of expiry” or “day after expiry” however you want to term it).
Yes, we have enough members that at least one account would be logging-in each day.
Please help us sort out this issue, it is rather critical now as our member accounts are expiring without them being notified of it until 10 days after the fact.
Sorry, can you please just clarify – does the CSV importer plugin need to be used? Or can we just export wp_eStore_tbl via phpMyAdmin and then also import it via phpMyAdmin on the new install? Or it is better to use the CSV importer plugin?
Is the wp_eStore_tbl the only table that needs to be exported/imported in order to import the eStore products into a new install?
We are following up with this again now because we have a new membership level whose registration form we do not want to include some of our standard custom fields.
Previously you directed us to use the eMember Form Builder add-on plugin for this purpose. However, we never ended up using the eMember Form Builder add-on plugin at that time because of the duplicate fields issue mentioned above.
We were able to get by before by just letting all custom fields appear in all registration forms, as happens by default. But now, with this new membership level, it is really a necessity that we be able to exclude some of the custom fields from this registration form.
Can you please tell us:
1) Is there any way that standard custom fields can be excluded from certain membership level registration forms without using the eMember Form Builder add-on plugin?
2) Or, is there any way that the custom fields created with the eMember Form Builder add-on plugin can be made global (so that they are not created anew / duplicated for each membership level that uses them)? If a fix for this does not already exist, could it be achieved through some custom paid development?
Also, to clarify for you the issue that zora_db was reporting:
This is the same exact issue that we reported previously. That is, when multiple membership levels need to use the same custom fields, the eMember Form Builder add-on plugin forces those fields to be created anew in each case, essentially creating separate new / duplicate versions of the same custom fields for each level that uses them.
When she said, “I need 6 different registration forms with customs fields that do overlap between registration types. I need all the data to be in the same place.” This is the exact same issue that we already reported. That is, to have multiple registration forms, some of which contain some of the same custom fields, without those custom fields actually being separate fields in the database as eMember Form Builder seems to do. Rather, we need those custom fields to actually BE the same field within the database, not new duplicate separate versions of the same field. This seems like it should be pretty straightforward, and we don’t quite understand why anyone would want the duplicate behavior that currently exists (if there is a need for a separate field than you can just create a separate field; if you are using the same field, presumably you want that to be the same field).
If this functionality is not currently available with the current setup, can it be achieved through some custom development? The existing functionality of not being able to specify which custom fields appear in a given registration form is very limited and it is really a necessity for us that this be fixed.
Thank you!
We had understood, according to the answer from this thread, that if we change the expiry date to be more than 10 days in the past, then the ‘After 10 Days of Expiry’ email will not be sent: https://support.tipsandtricks-hq.com/forums/topic/emember-dont-want-to-send-auto-expiry-emails-on-bulk-update#post-69110
In that thread it states: “If the expiry is more than 10 days in the past, then it won’t generate any auto-expiry notification email. So when you edit the membership level, set the expiry date of the level accordingly.”
Is that not the case?
One of our member groups is of a unique type and their renewal process is different as it depends on a few different variables, in particular a course that they are enrolled in. As such we do not want them to receive the standard expiry / renewal reminder emails.
To get around this we went ahead and set the expiry date for that membership level to ‘No expiry’ just before the 10 days before expiry email was set to be sent. Then, after 10 days have passed after the original expiry date we will then set the expiry date for the membership level back to the original expiry date.
As we understand, this will solve it.
Could you please just confirm that this will work in preventing that membership level from receiving each of the 3 expiry reminder emails?
Sorry to bother you but we’re just checking in to see when it might be possible to add this option. Is there any chance that it could be added in the near future?
Ok thank you – so this is the reason that we are asking, which may not actually be related to the original question:
On May 13th one of our members received the ‘Email before the account expires’ email. We have the ‘Number of days before the account expiry when the reminder notification is sent’ set to ’10’ for that email. And then within the text of that email we of course explain to the member that their account will expire in 10 days.
10 days from the 13th (when the email was sent) would be the 23rd. However, the expiry date for that member’s account was actually the 22nd (which is only 9 days from the date that the email was sent).
Then on May 22nd the member tried to log into their account (as they understood that their expiry date was the 23rd), was unable to do so, and submitted a complaint to us about that.
So it seems like the ‘Number of days before the account expiry when the reminder notification is sent’ value may actually be 1 less than what is entered into that field?
Should we enter that value as ’11’ instead of ’10’ in order to ensure that the account does not expire before the stated timeframe?
Or, is it possible to fix the sorting function so that the sorting the eMember members list by expired “Account State” would appear in proper order based on expiry date?
Hi,
We have tried sorting the eMember members list by expired “Account State” but the problem with this is:
1. It does not display them in order of expiry date.
2. Even if it did display them in order of expiry date, we would still have to scroll through to find those that have expired within the range that we need to search for.
Would it not be possible to add a ‘Display Recently Expired Member List’ option in the same vein as the ‘Display Soon to Expire Member List’? Or otherwise adding settings to allow for viewing a list of member accounts that have expired within a past ‘X’ number of days?
If this is not something that you could add normally, would it be possible to have this option added via custom development?
Thank you
