Forum Replies Created
-
Posts
-
Could you please implement this at some point?
Since you force the “Edit Profile” button onto the logged-in widget, and since there are no classes applied to those {li} items, there is no way for us to hide that button using CSS.
So, because we do not want that button to appear, we leave the “Member Profile Edit Page” URL field blank as that is the only way for us to get that button to not appear. However, since that URL field is a mandatory field, every time we update to a new version of eMember the eMember system automatically populates that field again and creates a new page for it, which we then have to delete, which is rather frustrating.
If you could please add a unique CSS class or ID to the {li} within the [wp_eMember_login] (i.e. the eMember_logged_widget) so that we can have display control over them, that would be much appreciated.
Just a note that we were contacted directly by another eMember customer who is also having this same issue.
Unfortunately there seems to be an issue on our site that is preventing this from working.
When we enter an address into the “To Email Address for Batch Emails” within the eMember settings, then for some reason none of the bulk expiry emails get sent at all.
We have confirmed this now multiple times: when that field is enabled and an email address is entered into it, none of the expiry emails then get sent. When we remove the email address from the field and leave that field blank, then the emails do get sent.
Since we can’t leave that field blank (due to the data security reasons mentioned previously), we have left that field enabled and so presently none of the expiry emails are being sent and we are having to send out expiry notifications to our members manually.
We also tested on a separate base install with no other plugins or themes and the issue did not occur. So this means that there must be something on our website that is causing this issue and preventing the emails from being sent when the “To Email Address for Batch Emails” field is enabled.
Could we please pay for some custom troubleshooting from the eMember team in order to look into this issue on our site and hopefuly get it resolved?
Could you please add a unique class or id at some point to the {li} items within the [wp_eMember_login] form, when logged-in, so that we can have control over the display of those items. This is for the “Logout” and “Edit Profile” buttons that appear within the
{ul} of that form when the user is logged-in.
This is not an urgent request at all, but if it’s possible to add a class or id to those items at some point that would be much appreciated as it would be great to have control over the display of those elements.
Many thanks
Just as a follow up here –
Our decision makers have decided that this is a clear breach of GDPR legal guidelines to be making customer email addresses available to others without their consent. As such, we have now had to disable the eMember expiry notification emails all together. We cannot have our customer emails shared publicly and be breaching data protection laws that way.
This means that we are either going to have to start sending out expiry notifications manually, or else our members will receive no notification that their account expired.
Please provide a solution if you can, to either be able to specify a global/default/organizational email address as the “To” recipient, or to remove the “To” recipient all together. In either case we must be able to avoid having a member’s email used as the “To” recipient on those bulk emails, it is a data and security issue and puts things in violation of the European data laws.
This is a rather critical issue, please help, thank you
Just as a follow up –
As a workaround we have now set the “X Days After” setting to 1 day, instead of the 10 days that it was set to before. This way both the main expiry email and the “X Days After” expiry email will go out 1 day after expiry, instead of 10 days as before.
While it would still of course be great to have both emails sent separately and at different times, as intended, from a critical functionality standpoint this workaround should more or less solve the problem for us, as it means that our users will no longer be waiting 10 days to be notified of their account expiry, and instead will now be notified of that fact as soon as possible after expiry.
Just posting this here in case it is of help to any other users or websites:
There seems to be a fundamental flaw with the eMember plugin, whereby the main expiry email is not sent at the correct time when the account expires.
There are 3 expiry emails: one X days before expiry, then the main expiry email (when the account expires), then one X days after expiry.
The “X days before” and “X days after” emails are sent at the proper time. However, the main expiry email (when the account expires) is not sent when the account expires, but rather is sent at the same time as the X days after expiry.
This issue has been confirmed on multiple websites on multiple servers with no other plugins or themes.
We have tried to request a fix for this with eMember support via email but they refuse to address the issue.
So if you are expecting your members to be notified at the time their account expires, know that this functionality does not work properly and that email is not actually sent until after the account has expired, and you can save yourself any trouble in asking for a fix for this as we have already tried.
Best of luck
Ah got it, thank you!
We have already got things set up now using the duplicate sections but this is very helpful in case we decide to go back to the php method.
Many thanks!
Thank you for your reply.
We have tried using the referenced PHP code, however even with that we aren’t quite able to achieve the solution because we need the output within that code to contain an eStore “buy now” shortcode: [wp_eStore_buy_now_button id=20]
All we are wanting to do is to have different renewal options for different membership levels on our renewal page.
Since, as we have covered, the existing eMember shortcodes allow for protecting content for a membership level if the account is EITHER Active OR Expired, but not both, the only solution that we can figure out is to duplicate our content sections and have each renewal option appear multiple times within the code, once with scope=”expired” and once without.
For example, one section using the standard [emember_protected for=”2″] shortcode and then another with the exact same content using the expired attribute [emember_protected for=”2″ scope=”expired”]
This seems like a rather clunky solution, since we have to do this multiple times and it means we have to include and manage several duplicate sections within our page code. But at least it works and achieves the necessary result of having the content display for that membership level in both Active and Expired states.
If there is a simpler way to achieve this result, please do let us know.
Otherwise, we would humbly suggest that it would be an improvement to the eMember plugin to add the allowance for an additional parameter for the scope, to allow for content to be displayed for both Active and Expired states.
For example, scope=”active,expired” or scope=”active-expired”
Thank you
Hello,
Could someone please help with this? We would like to be able to display some content on our renewal page that is only for a specific membership level. But we need that content to be viewable by that membership level even if the account is expired.
Could you please help us understand how we can display content for a specific membership level both when the account is Active and when the account is Expired?
Many thanks
Hello,
Can you please tell us how we can display content for a specific membership level, regardless of whether the account is Active or Expired?
For example the standard shortcode makes the content available if the account is active (but not if it’s expired): [emember_protected for=”2″]
And the expired shortcode makes the content available if the account is expired (but not if it is active): [emember_protected scope=”expired” for=”2″]
How do we make the content available to that membership level whether the account is active or expired?
We tried using [emember_protected scope=”verified_users_only” for=2] but as you have stated above the “verified_users_only” code does not work in this manner.
Can you please tell us what is the proper method of displaying content for a specific membership level, for both Active and Expired states?
Thank you
Thank you! Yes we have the debug enabled.
Please just let me know the best way to send that to you – should I just send that to the support@ email address?
I’ve just confirmed the issue again – it seems that both the “X days before expiry” and “X days after expiry” emails are being sent correctly at the properly scheduled time. But the standard expiry email is not being sent until 10 days after expiry (from what I can tell, it seems that the standard expiry email and the “X days after expiry” email are both being sent together at the same time, 10 days after expiry).
Please just let me know the best way to send you the log file.
Thank you!!!
