Tips and Tricks HQ Support Portal › Forums › WP eMember › WP eMember Troubleshooting › Renewals sometimes applied to incorrect member
- This topic has 9 replies, 3 voices, and was last updated 1 year, 9 months ago by admin.
-
AuthorPosts
-
December 7, 2022 at 12:29 pm #84761CVGSwebmasterParticipant
We require our members to login before selecting “renew”. Despite this, sometimes (not always) the renewal is applied to a different member, usually the person that renewed just prior. In these cases, the start date of the member trying to renew is not updated. The start date of the member that renewed prior is updated and they incorrectly receive the renewal email. The PayPal process is working fine. I have debug enabled, and I can see that the member ID is not correctly selected in these problem cases. I do not know what triggers the problem, nor do I understand why the problem sometimes goes away, then returns at a later date. Suggestions? I would be happy to share the debug file if that would help. Thank you very much.
Colleen
December 7, 2022 at 5:59 pm #84762wzpModeratorWe require our members to login before selecting “renew”. Despite this, sometimes (not always) the renewal is applied to a different member…
- Keep the debug logs turned on, until the situation is understood/Resolved. This will allow you to see what payment notification the plugin is receiving and if that matches with what is expected.
- Place the actual renewal button on a protected page, or in a protected section, that can only be accessed if the member is logged in.
- Are you using any page caching plugins on your site? If so, which one?
December 7, 2022 at 7:05 pm #84763CVGSwebmasterParticipant1. Yes, I have the debug logs turned on. In the problem cases, the ID the renewal is applied to doesn’t match the person who paid.
2. Yes, our renewal page is protected.
3. Our list of plugins is: all in one event calendar, maintenance, site kit by google, tablepress, updraftplus, wordfence security, wpforms lite, emember (plus email broadcast, bulk import, profile extended).
Thank you!
Colleen
December 8, 2022 at 5:13 pm #84765wzpModeratorCould you please show a complete log example, that demonstrates this issue? You do not need to redact anything.
- This reply was modified 1 year, 9 months ago by wzp.
December 10, 2022 at 9:34 pm #84768CVGSwebmasterParticipantCan you confirm that you received the debug log I sent on Dec 8?
Thanks,
ColleenDecember 12, 2022 at 3:55 pm #84771adminKeymasterNo, I haven’t received it. Did you submit a contact form with the same email address that you are using for this forum account?
December 12, 2022 at 4:15 pm #84772CVGSwebmasterParticipantI copied it into the “reply to” area in the support forum (just like I’m typing here). Can you clarify the “contact form”? Does that mean “contact us”? Or “customer support forum”?
Colleen
December 12, 2022 at 6:58 pm #84774wzpModerator“Contact Us”
December 12, 2022 at 7:57 pm #84775CVGSwebmasterParticipantThank you. submitted log through “contact us”.
December 14, 2022 at 6:04 pm #84776adminKeymasterThank you. I have received it and given a reply. In summary, it looks to be a caching issue on the site.
If a member is logged into a membership account and then makes a payment, the payment will be applied to whatever member ID the user was logged into. In your case, there seems to be some caching happening. So the page containing the payment button is cached and another user is using a button (which is using cached data from another member). So everything is getting messed up after the payment since it will have the Member ID of another user. I have explained the caching issue in the email.
- Keep the debug logs turned on, until the situation is understood/Resolved. This will allow you to see what payment notification the plugin is receiving and if that matches with what is expected.
-
AuthorPosts
- You must be logged in to reply to this topic.