sadohage
Forum Replies Created
-
Hi mbrsolution,
Are you saying that this issue happened after you migrated your site to Kinsta? Do you know if your new host has a caching system setup in your server?
No, both the issue where the cancel button does not display properly and the issue where users were not being registered correctly occurred before migrating the site to Kinsta.
Fortunately, the root cause of the registration issue was identified, and it was resolved on the previous server. Since migrating to Kinsta, the same registration issue has not reoccurred.
However, the issue where the cancel button does not appear for users who registered before upgrading to SWPM 4.4.9 still persists, even after their subscriptions have renewed, even on Kinsta.Was this carried out after you migrated to Kinsta?
Yes, after the migration to Kinsta was completed, I accessed the page containing the cancel button shortcode using an old user account. The cancel button was not displayed, and no relevant errors were found in the debug log.
If the cancel button cannot be displayed for older users even after a subscription renewal, I am considering handling it by allowing users who do see the cancel button to cancel via the button, and guiding users who do not see the button to cancel via the Stripe Customer Portal.
Is there any possibility that the cancel button will become functional for older users as well?
(Asking users to cancel their current subscription and start a new one is not a practical solution.)I appreciate your continued support.
Hi mbrsolution,
Thank you for your reply, and I apologize for my delayed response.
Also, I must correct a mistake in the situation I mentioned in my previous message—my apologies for the confusion.
Previously, I stated, “Furthermore, the cancel button is also not functioning for newly registered users who have recently made recurring payments.”
However, it turns out that I was still logged in with an older account in another tab, which caused the confusion.
I have now confirmed that the cancel button is working correctly for users who recently became members through a recurring payment.
(When I accessed the page in incognito mode with the new user account, the cancel button displayed correctly.)However, the situation I mentioned—“Even for existing users whose cancel button was not functioning, the button should begin working once a new transaction occurs, but as of now, it still doesn’t”—remains unchanged.
Even though multiple payments have been processed after following the steps provided in the previous thread, the cancel button has not become functional for these users.Does this mean that for users who registered before the changes made in the previous thread, the only way to make the cancel button functional is to cancel their current subscription and create a new one?
(From the discussion in the previous thread, I understood that the cancel button would become functional automatically when the subscription was renewed.)Also, since the previous support thread, I have disabled bcache (as discussed in another thread:
https://ww.wp.xz.cn/support/topic/continuationmember-account-is-not-created-even-after-successful-payment/),
which resolved another issue.
After that, I migrated the site to Kinsta for ongoing operation.I have also checked the debug logs, but when accessing the page with the cancel button using an old user account, nothing was recorded in the logs.
I appreciate your continued support.
Hi mbrsolution,
Thank you for your reply, and I apologize for my delayed response.
I understand that, at this time, there is no way to set Tags when adding a contact to a Mailchimp Audience using the addon.
It would be very helpful if support for Tags could be considered in a future update.
Thank you again for your support.
Hi, wp.insider
Thank you for your support.
The issue was caused by bcache, and after asking the server management company to disable it, the problem was resolved.
Thank you very much for your continued support over this long period.Thank you for your response.
I have created and activated a new webhook with the latest version on Stripe and deactivated the old version of the webhook (currently, only the new version of the webhook is active). Additionally, I have created a new Stripe SCA Subscription Button and published it on my website.
In this situation, I will check if the cancel button appears for the existing users who were experiencing issues after a new transaction occurs.
Regards.
Thank you for your response.
I understand that for existing users, over time (with updates or the occurrence of new transactions), their subscriptions will gradually be replaced with new ones where the cancel button functions properly.
Thank you for providing the migration steps as well. When creating a button on Stripe, should I follow the documentation provided here?
https://simple-membership-plugin.com/sca-compliant-stripe-subscription-button/I will update the webhook version and follow the steps you mentioned. I will check whether the cancel button starts functioning for existing users who currently do not have a working cancel button once a new transaction occurs.
If there are any issues, such as the cancel button not working even after a new transaction, I will reach out for further assistance.
Thank you for your support.
I appreciate your continued assistance.@wpinsider-1
Thank you for your response.I would like to understand more specifically what you mentioned. Does it mean that after updating the Stripe API version (webhook version) to the latest one and recreating the subscription product, the cancel button will only be valid for new users? Or, once the webhook is updated, is it unnecessary to create a new subscription product?
Additionally, for already registered users, will the cancel button become active if a recurring payment occurs after updating the webhook?
Could you please confirm if my understanding of the cancel button shortcode’s functionality for the following scenarios is correct?
- Webhook updated, subscription product recreated, new users → work
- Webhook updated, subscription product recreated, existing users (no payments after webhook update) → Not work
- Webhook updated, subscription product recreated, existing users (payments after webhook update) → Not work?
- Webhook updated, subscription product not recreated, new users → Not work?
- Webhook updated, subscription product not recreated, existing users (no payments after webhook update) → Not work?
- Webhook updated, subscription product not recreated, existing users (payments after webhook update) → Not work?
Thank you for your detailed support.
I appreciate your continued assistance.@mbrsolution
I tested version 4.4.9 last night.
However, the issue with the cancel button has still not been resolved.
Regards.I have not tested with version 4.4.9 yet.
I will test it soon and report back with the results once the testing is complete.
Regards.Thank you for your response.
Yes, this issue does not occur consistently but happens very rarely. However, it is a critical problem for users. (I have confirmed it has occurred twice so far.)This website does not run any caching plugins or server caching.
Debugging was turned off until now, so I didn’t have any log files to submit. I have just turned on debugging, so if the same issue occurs again, I will share the debug logs with masked personal information and seek your assistance again.Thank you for your cooperation.
Sincerely,@mbrsolution I apologize for the significant delay in replying..
I have tested it with Simple Membership version 4.4.6, but I can confirm that the issue with the cancel button still has not been resolved.
Regards.
Thank you for your response.
I apologize for the significant delay in replying.I appreciate your escalation of the issue to the development team. If the cancel button is not functioning properly, manual cancellation becomes necessary, which is quite cumbersome. Therefore, I will continue my investigation to ensure the cancel button functions correctly.
Thank you for your support.
Thank you for your response.
I apologize for the delay.Did you log in as a member that belongs to a Stripe subscription membership level account? The reason why I am asking is because the button only appears if the person logging in has a Stripe subscription membership account. If not, the button will not appear.
Yes, I took the opportunity to log in to the site using the account of the user experiencing the issue and checked whether the cancel button was displayed. Of caurce, the account has a valid subscription payment through Stripe and is an active subscription membership in the SimpleMembership plugin. However, the cancel button is not being displayed.
Thank you for your continued support.Thank you for your response.
I have followed the troubleshooting steps you provided. Even after changing to the default WordPress theme (Twenty Twenty-Four) and deactivating all plugins except SimpleMembership, the cancel button did not appear. It seems that the issue is neither related to theme conflict nor other plugins conflict.
If there are other things I should check for a resolution, I would appreciate your advice.
Thank you once again for your ongoing support.
To add,
“メンバーとしてログインしていません” in image1 and image3 means ”You are not logged-in as a member”.
“利用中の定期購読はありません” in image2 means ‘No active subscriptions’.
The button “定期購読をキャンセルする” in image4 is the cancel button generated by shortcode [swpm_stripe_subscription_cancel_link]