Support » Theme: Responsive » Can’t type in credit card number on checkout

  • Resolved patjk

    (@patjk)



    I’m using Responsive theme and it works great. However, recently for some reason at checkout when the user selects Stripe as an option, the user can’t type in their number (Stripe uses the Stripe Payment Gateway plugin). When I change the theme to the default them, the problem is solved, so it appears to be an issue with the responsive theme or my customizations.

    The credit card box is there but can’t be typed in.

    I’m using:
    WooCommerce Stripe Gateway 4.0.7
    WooCommerce 3.3.4

    The issue looks like:
    https://www.dropbox.com/s/pzawrqugpufdxib/Screenshot%202018-03-27%2015.37.17.png?dl=0

    No characters can be entered into the field. I can’t leave the default theme live as the site is active. I’ve downloaded the theme files though below if that helps, contains the child and the theme itself:
    https://www.dropbox.com/sh/s77sz63gc8unnas/AABMP4ajf6aekIErdI__oPKza?dl=0

    Any thoughts to resolve it would be much appreciated. Also want to ensure it formats well on mobile as in the past it may misalign.
    Thanks

Viewing 6 replies - 1 through 6 (of 6 total)
  • Theme Author CyberChimps

    (@cyberchimps)

    Hi,

    Apologies for the delay in reply.
    Can you please let me know your site URL so that I can try the steps and check the issue?

    Moreover, can you please try activating your parent theme once? Check if the issue is getting resolved.
    This will help us to find out if the issue is with the parent theme or the child theme.

    Moreover, I checked the zip file you have provided and the version of the theme is 1.9.8.2 which was released 2 years back. The latest version of the Responsive free theme is 3.11. please update your theme and then check if you are still facing the issue.

    *Please keep a backup of your theme before updating.

    Thank you.

    Hello,
    Apologies about the delay, was seeking help with someone else and they couldn’t solve it. The URL of the site is snapupc.com.

    When I activate the parent theme, it does solve the issues (though there is some misalignment issues in the fields for stripe). Here is what it looks like with the parent theme:
    https://www.dropbox.com/s/9gojcciasjmxhk4/Screenshot%202018-04-24%2011.33.24.png?dl=0

    And here is what it looks like with the child theme (and none of the fields for stripe can be entered into):
    https://www.dropbox.com/s/a0e295duix3css4/Screenshot%202018-04-24%2011.35.00.png?dl=0

    Also when the child theme activated the dropdowns for state/country look/function strange:
    https://www.dropbox.com/s/wc9jhthf5krtdub/Screenshot%202018-04-24%2011.35.42.png?dl=0

    So it appears something is going on with the child. Here is a copy of the child theme files here. The Responsive Parent is up to date now:
    https://www.dropbox.com/s/xa94m3yvf7g15tn/responsive-child.zip?dl=0

    Any recommendations/ideas to resolve this ASAP would be much appreciated.
    Thanks!

    Theme Author CyberChimps

    (@cyberchimps)

    Hello,

    Thanks for sharing all details. Apologies but as the issue is with child theme we cant help you much with this.

    But I checked files in your child theme. Looks like you have not updated the child theme files header.php and footer.php. It may be not be related but just a suggestion. Also there are javascript errors on on checkout page related to stripe –

    Content Security Policy: The page’s settings blocked the loading of a resource at self (“script-src https://js.stripe.com”). Source: ;undefinederror

    I suggest checking this error as it may solve the issue.

    Thanks.

    Thanks for the info, I got someone to help me fix it, was indeed something with the child theme.

    Do you know what may cause this sort of issue?
    Content Security Policy: The page’s settings blocked the loading of a resource at self (“script-src https://js.stripe.com”). Source: ;undefinederror

    Cheers!

    Theme Author CyberChimps

    (@cyberchimps)

    Hello,

    It can be a plugin conflict or may be javascript errors. It can be some plugins are not compatible ot updated. Need more analysis to be sure :).
    So is the issue been solved ?

    Thanks, yes, issue solved and marked.

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.