RexAK

@askwpgirl
May I ask, what version did you update from? And, when?

You should always clear your caches after updating your site, this is true for plugins, themes, and posts/pages.

Hopefully, your hosting company provides a way for you to update caches yourself, without the need to contact them.

Hi,

If it works for some, and not others, I would guess that you’re site may be loading too slowly in some cases. I have not heard of the input field not working for some users and working for others.

We added a new method of customizing the CardConnect card number input box’s CSS.
You can inject the height of that box via CSS if you enable the setting described here:
https://www.ads-software.com/plugins/cardconnect-payment-module/#where%20are%20the%20developer%20css%20options%3F

and then visit the CC setting in WooCommerce’s settings area.

This is due to the way card connect displays their iframe CC field – it needs CSS injected into its API. We have to do a “best guess” on how tall the input field will be, and, since there are a impossible amount of themes that may alter this field normally, it cannot always get it right.

Once you enable the dev options, you’ll have a slew of other options available to you, and one of them is turning off the new iframe API and reverting to the old CardConnect JS methods. This may also help in your case.

If you decide to go with the iframe and inject CSS of your own, make a backup of your DB, or test on a dev version of your site.

If you decide to revert to the older CC JS methods by turning off the iframe setting, you’ll need to test the checkout process to insure orders are working correctly, since this method is no longer recommended.

If you need addition personal assistance, contact CardConnect, and have them forward your site’s login info to me. I’ll need to install a plugin to edit your files, and then test various settings to best accommodate your needs.

Truly sorry to hear that. Again, we’ll look into adding this idea in the future, we just haven’t added it yet.

We look forward to welcoming you back when we can get the feature added.

Marking this closed. See latest update for options to fix the missing CC field that occurs on some themes.

I’m wondering if there is any other way, outside of the checkout page, for my customers to manage their payment options, say, in the my-account page?

Not at this time. This may be something we can add in a future update.

Furthermore, any cards that i manually add to a customer does not show up in the saved card drop down.

Currently, saved cards from the hosting site can only be added while the customer is logged into their account. There is no method available to pull in saved cards you may have added in the Virtual Terminal, or another place.

Edit: spelling

• This reply was modified 6 years, 1 month ago by RexAK.

Awesome! Glad we could fix the issue, for you.

If you would, take a second to drop a review about our service, on these forums.

Hi @jburgeson,

Give the newest version a try (3.1.1.) and let me know the results.

I’ll take a look. Please keep running the 3.0.4 version until I can get back to you.

Would you mind telling me what version of Woo Subscriptions you are running?

I’ll pass on your requests to CardConnect, then.
From what I understand, we’re only passing in some acceptable parameters that the IFRAME ultimately controls, and not actually controlling any JS in the IFRAME ourselves.

The same goes for the custom CSS, we’re passing that as a parameter, and it’s somewhat limited as to what is passable.

Since this is not technically a bug, I’ll set this thread to resolved.

Haven’t heard back, closing thread

Take a minute to update the plugin, and turn on the new developer options for the plugin. (See the FAQ)

You should be able to now override the css for the plugin’s card number input.
Let me know if this works for you.

Hi,

Please try the newest version of the plugin, and pay attention to the new Developer CSS options noted on the plugin’s WP repo home page under FAQ section.
This may get you somewhat where you need to be.

A “.error” class is added to the input when card number validation fails, but this class is added by the iframe on CC servers, if I recall correctly. All other validation of the field also takes place within the iframe, and not within the plugin. Also, alpha/numeric validation occurs on the CC servers, and not locally.

If you want to give the WC_CC_ADVANCED constant a try, turn off the IFRAME capability in the plugin settings, and see if the JS implementation (non-iframe) works for checkout in your specific case. If so, you have a ton more control over the CC# field, and could do some card highlighting of VISA, MC, etc. Due to requests from CardConnect, we may not be updating the JS version going forward. It has been left in for legacy reasons and may not be supported going forward from the 3.0 release.

To go a bit deeper, the plugin uses the CardConnect IFRAME api, and has a limited set of CSS that you can inject (see new features), and the CSS is sanitized on the CC servers. Due to CORS policies, this is the CardConnect prescribed method of CSS injecting onto the field. You cannot inject your own JS, as that is handled by CardConnect inside the iframe. If you dig through the plugin, and find something that you can get working to solve your other customization questions – or you find some amazing secure workarounds, I would love to take a look at your code and run it through testing. I could offer contribution attribution, if that ends up being the case.

If all else fails, I can speak with CC and see if they could implement some of this stuff on their side.

Also, if you would, take a chance to rate the plugin…

Try this:

In your wp-config.php file, place the following line, near the bottom of the file, just before the line “/* That’s all, stop editing! Happy blogging. */”

define('WC_CC_ADVANCED', true);

Then, in the WooCommerce settings for CardConnect, at the bottom of the page, you’ll see new settings fields for advanced users and troubleshooting.

You can either turn off the “Enable IFRAME API” checkbox altogether and revert to a non-iframed version.

Alternatively, you can turn off the “Autostyle” checkbox, and and see if you can style it yourself with custom CSS, although styling a Iframe my get blocked by CORS – https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS.

These extra settings are all checked by default, and the default for the “Timeout” field is 500 – just in case you want to revert to the defaults.

If you cannot get it working using the above, respond here, and I’ll see what other options are available.

My apologies, that info does not mean anything to me, as I’m not a iptables/server person.
This is not a plugin issue, as far as I can see. If the ports are open, and the server is configured correctly, the plugin should work.

I suggest again, you reach out to Card Connect and give them admin login access to your WP site, and the cPanel login details. They should be able to log in and check that the server is configured correctly, or work with your host to properly troubleshoot.

I would suggest reaching out again to CC support, and explaining your situation, and seeing if they can put you in contact with someone on their team that you can give cPanel and WP access to.