jamaan

and that apply if I move the site to a new domain or subdomain following your steps? and it won’t affect the subscriptions at all e.g. the expiries?

• This reply was modified 4 weeks, 1 day ago by jamaan.

Can you please response if changing the domain to another or moving the site to a sub domain would affect the subscriptions? I have Stripe payment as active to receive subscription payments.

Stripe only

Hey Support,

Do you have any update for me on my last query?

Also, if I have to change the domain, would that affect the existing/new subscriptions?

Alright, I’ll have it set up this way to see how it processes.

But the “pms” crons run every 24 hours, so I don’t think there would be any changes needed on the server level.

So by default, the retry payment is set at 3 days? in my case if I have the “Maximum number of retries” set at 20 and the “Retry Interval” set at 20, does that mean:

When the payment fails the payment will be retried after 20 days, if the payment fails again, then again after 20 days, and so on until 20 attempts are made?

If I set the “Maximum number of retries” at 5 and “Retry Interval” at 1. Will the payment be retried 5 times after each day?

Hi again:

So for the subscriptions, I guess what’s confusing is “Payment Retry” section under “Misc” > “”Payments” tab. Can you please explain how the “Retry Interval” works? If I have the “Maximum number of retries” set at 20, how would that work?

One more thing:

If a user’s subscription status changes to pending, can we still manage to retry payment? E.g a user who tries to subscribe but fails for some reason or the number of retries reached right now what I do is, change their status to active again and then retry the payment.

I did it. I would really appreciate if you can expedite the process.

Here the website link:

Negozio online – Ager Oliva

Settings are:

https://drive.google.com/file/d/1iOf_jf307yHzOhmg9zXDWOS5CpHsz1NE/view?usp=sharing

I came here to address the same issue but seems like the author is not interested in resolving the issue.

Here’s what I did to overcome the issue:

1. Downgraded wordpress version to 6.2.3 since the plugin conflicts with the higher versions and the problem gets solved.