RexAK

@ccolotti
Yes, same here, previous IT guy. I have a request in with CardConnect to see what can be done.

@ccolotti

I certainly will. I’ll update both you, and the plugin if a change happens. Thanks for your understanding.

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

Marking as resolved. If CardConnect gets back to us about possibly changing the range requirement, I’ll update this thread.

For further info about this change, please contact CardConnect support.

Marking as resolved.

• This reply was modified 5 years, 11 months ago by RexAK.

Hi @ccolotti

I am getting ready to contact SiteGround as well, to ask the same, since I host several sites with them.

CardConnect should have sent you an email about this change, as I think they sent the same email to all merchant account holders. I would ask that you reach out to CardConnect with your merchant number in hand, and let them know how this affects you. I’m reaching out to them today, as well, to ask if there can be some restriction on the IP address needed for the plugin to work.

CardConnect does have some testing dates, which you can get from their support channels. As of right now, I can only confirm the hard date of the switch, May 29th.

Yes, it does.
It supports the official Woo Commerce Subscription plugin, so as long as you’re using that, you’re good.

Hi @ignitemedia,

We would not be able to modify the plugin for your specific needs. Our dev is aware of your request, and it will be up to him to decide if this dependency is still needed. We will be issuing a new version of the plugin shortly for compatibility with Woo and the latest WP. I understand this does not help you with your scrolling issue, however, I can say, that if you use the WC_CC_ADVANCED constant as outline on this plugin’s page, you may be able to get around the scrolling issue by using turning off the IFRAME version of the plugin – it does additional checks for errors which may be causing the scrolling in your case. I spoke with a CC rep today and there currently does not seem to be any plans on turning off the JS API.

@askwpgirl Thank you for your assistance and suggestion!

@ccolotti
I apologize that we have no fixes for your particular setup. We don’t even know what site you’re having trouble with. We do our best to code for and test as many scenarios as possible, including the 3 major browsers and a handful of the most common themes out there, but there will always be outliers and things we cannot know.

You should be able to revert to the previous non-iframe version of the plugin and get it to work for you, with the dev tool I mentioned above. Test a checkout and if you get to the Woo Thank you page, BOOM!, you’re golden. The JS API tokenization version is not slated to be discontinued as far as I know.

I’ll pass alone your concerns with the iFrame styling to CardConnect, and let them know that you have an issue. If you reach out to CardConnect directly, and you can give them access to your server and WP site, they should be able to pass that info on to me, and let me see what I can do to help you specifically. Please note, I am not an employee or rep for CardConnect.

Lastly, there are just not enough users who have told us about their particular CSS customizations, for us to know what is common (0, in fact).

While we would hate to see you not use the plugin, we understand if it does not work for your particular setup. I you have further issues, or need more clarification, please open a new thread, this thread has been closed for a bit.

Hi @ignitemedia
Hmm, that was something I was unaware of. I’ll talk with our dev to see if that dependency is needed any longer.

You are free to modify the plugin for your needs. It is open source. You would just need to take into account the modification when WP plugin updating happens.

The plugin throws errors, like any other gateway plugin, and your theme responds to those messages. There is no code that scrolls the screen, or displays the messages in any particular way. Its up to WooCommerce, and your specific theme to handle the messages. If you are comfortable, you can try switch on the developer options, and see if something works for you.

What theme are you using, and do you have a page I can take a look at?

@ccolotti
Any CSS you add would be custom, so there are no common settings specific to your situation.

Turning off the iFrame reverts you back to the older methods that the plugin used for tokenization. If it works for you, keep using it. You’ll need to test checkout if iFrame is turned off, as we don’t support it, but left it in there for developer and power user troubleshooting.

@ccolotti Please see the above concerning adding your own CSS.

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?

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.