Plugin Author
RexAK
(@rexak)
Those ports should be open to allow the plugin to work in general.
Are you using the plugin in sandbox mode, or…
Out of the box, subscriptions (the official Woo plugin) works, however, you may have another conflict with another plugin or something I can’t see.
Without more details, I’m not sure how to assist, but Ill check that WooSubscriptions latest version is still working correctly.
No on the sandbox mode. The site is processing transactions successfully otherwise.
I do wonder how its working in that case. It’s entirely possible they are open but its on a shared sitegrounds account, so my assumption is they are closed. I’ll double check there.
What happens when they are not open? Should all transactions fail?
What possible reasons could there be for this behavior?
Namely;
1) First order succeeds
2) User is able to store card and use later
3) Subscriptions are not creating new orders on renewal
Thank you very much for your prompt reply.
Plugin Author
RexAK
(@rexak)
Hmm. So, the renewal order never gets made? As in, the subsequent order does not show up in the woo order list?
In the past, for each Siteground shared account, I’ve had to have them open the ports, but if your initial order is working fine, then I would say the ports are open.
Wether a user saves a card, or not, should not impact subscriptions.
Do you get enough traffic to trigger the subscription wp-cron jobs? Is cron disabled somehow? Would you test subscriptions with the testing methods in their docs, and let me know the result?
Yes, renewal order is never made. “Next Payment” is in the past as well.
Can confirm the ports are open.
What is “enough traffic”? It’s a very small site and there are only about 8 active subs. Two have lapsed. I’m assuming this is under the threshold.
F*#@
I just realized this site is still on WP 4.9.8. Could this be the problem?
Here is a gist of my woo status
Plugin Author
RexAK
(@rexak)
WP version 4.9.8 should be fine, but you’ll need to check the requirements of Woo Subscriptions to be sure.
As a follow up, you can see if manually triggering WordPresses built in cron system fixes your issue – if you’re still having it.
You may not have enough traffic to trigger it normally.
Here’s a link that discusses the WP Cron issue:
https://www.itworld.com/article/2982356/tips-for-scheduling-tasks-in-wordpress-with-wp-cron.html
