Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Jonayed Hosen (woo-hc)

    (@jonayedhosen)

    Hi @bilalzhd

    Thank you for reaching out about the issue with the card input field not showing on some devices and browsers. I have tried to check the issue from my side, and it seems to appear as expected.


    To better understand and assist you, could you share more details about when this problem started? Specifically, has it been occurring since a recent change, such as an update to your site, theme, or plugins? Knowing if any modifications were made around that time would help narrow down potential causes.

    Additionally, could you let us know if this issue is consistent across specific browsers (e.g., Chrome, Firefox, Safari) or devices (e.g., mobile vs. desktop)? If possible, providing a screenshot of the checkout page where the card field is missing would be very helpful.

    Also, we recommend checking for any errors in your browser’s console on the affected devices. Errors in the console often provide valuable clues about what might be causing the problem.

    Once we have this information, we’ll be in a better position to guide you toward a resolution.

    Thread Starter bilalzhd

    (@bilalzhd)

    thanks for reaching out, this issue is there since I restarted using square, I was using it first then I got some issues with it, I replaced it with PayPal, then PayPal had issues so I started using Square again, I have disabled automatic updates in WordPress so I do not usually update any plugin or theme, but I had this issue so I manually updated the theme and plugins but the issue remained the same, so I do not think if this issue is related to updates in my opinion but you know better.

    Plugin Support Jonayed Hosen (woo-hc)

    (@jonayedhosen)

    Hi @bilalzhd,

    Thank you for sharing the details about the steps you’ve taken. Since you’ve already performed a conflict test, let’s take it a step further to narrow down the cause:

    • Please ensure that only WooCommerce and Square remain active during testing. Even if you’ve done this before, there might have been configurations or caching affecting previous tests. You can follow this detailed guide on how to perform a full conflict test: WooCommerce: Testing for Conflicts.
    • Since not all customers are encountering the error, there could be browser or device-specific compatibility problems. Could you gather more details about which browsers, devices, or operating systems are affected? This information might provide additional clues.
    • If you’d prefer not to test directly on your live site, I recommend creating a staging environment. The WP Staging plugin can help you set this up easily. This allows you to safely test changes without impacting your live site.
    • I would also suggest reviewing your error logs if you haven’t done so already. Check your WooCommerce logs under WooCommerce > Status > Logs, as well as your server error logs, as they may reveal relevant errors related to this issue.

    It would also help us to review your current System Status Report to gain more insight into your setup. You can find this report in your WooCommerce dashboard by going to WooCommerce > Status. From there, please select Get system report and then Copy for support.

    Once we have more details, we can explore further troubleshooting steps.

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