Credit Card input fields not being replaced correctly

Hello @studiomondiale

Thanks for reaching out to us, we’re here to help.

This problem may be related to a conflict with your current theme or another plugin on your site. To help resolve this issue, I recommend conducting a full conflict test. You can do this by setting up a staging site, which is a duplicate of your live site but where changes won’t affect your live operations. On this staging site, please switch to the default theme, such as Storefront, and deactivate all plugins except for WooCommerce and PayPal Payments. Test to see if the issue with the credit card fields still occurs under these conditions.

If the issue is resolved in this minimal environment, begin reactivating your original theme and other plugins one by one. After activating each one, check to see if the problem reappears. This method will help you identify the specific cause, whether it’s the theme or a particular plugin causing the interference.

Once you complete these steps, please update us on the results.

Kind Regards,

Krystian

Hello,

It works fine with Storefront. But given that it worked fine with 2.8.3. and is broken with 2.9.0, it must be something within your plugin that has changed.

I’m using the rather popular Enfold theme, but unfortunately I can’t open a support ticket over at Kriesi, the creators of Enfold, due to their support policy, which means I’m forced to stay with 2.8.3 until that has been resolved (or deactivate advanced credit card processing).

You can have a look at the issue here: https://www.mondiale-testing.de/web/testumgebung0322/de/produkt/prufung-telc-deutsch-a1/ (just put that product in your cart and proceed to checkout).

Thank you!

Hello @studiomondiale

We don’t have a copy of that theme, but we’ve tested various others and haven’t been able to reproduce the issue.

What seems to be happening is that the plugin displays both the old hosted fields and the new card fields simultaneously, which shouldn’t occur. We’ll need to conduct more thorough testing to pinpoint the cause. A temporary fix might involve using the following code snippet: add_filter('woocommerce.feature-flags.woocommerce_paypal_payments.card_fields_enabled', '__return_true');

However, sticking with version 2.8.3 might be the safer choice for now. While hiding the hosted fields with CSS is an option, it’s not ideal compared to using the more stable version 2.8.3.

Kind regards,
Krystian

Hello,

Thanks for the reply.

I’m afraid the snippet does not work, no change.

Maybe it’s a compatibility issue in combination with Polylang, because with 2.9.0 the inserted PayPal credit card fields are in English (Card number), even on the German version of the shop, while with 2.8.3. these are in German (Kartennummer), just like the ones they are replacing (see screenshot https://imgur.com/a/23lZIwG).

I’ll stick with 2.8.3 for now, since this works perfectly so far.

Hello @studiomondiale

We suggest you contact us directly for further assistance. We may need to examine your system report or logs to better understand what’s happening and how to reproduce it. You can open a ticket with our service desk. Here’s how you can request support:?Request Support. Please make sure to include the URL of this thread in your ticket for reference.

I’m looking forward to your response.

Kind regards,
Krystian

Ciao, ho lo stesso problema, nel mio caso il problema si risolve disattivando Elementor Pro.

Frontend: https://snipboard.io/dMcXSq.jpg

Code: https://snipboard.io/LqTpU3.jpg

Hello @studiomondiale @simonedegasperin

Look like we found what could be causing this and can provide a potential test package with a fix later in the day. I will update the thread accordingly.

Kind regards,
Krystian

Awesome!

I was about to fill out the support form, but I’ll wait for the potential fix now.

Hello @studiomondiale & @simonedegasperin

We would like to provide an update on this issue. We have managed to put in a fix on this pre-release version?2.9.1-alpha. Please bear in mind that this is a preview on the next update, which means it hasn’t been fully tested, but we appreciate any feedback that you might have as you try it.

When introducing new features or making significant changes to your website, it is crucial to test these modifications in a controlled?Staging?environment before deploying them to your live site. We highly recommend that you initially implement and test any new features on a staging site.

Let us know if that works for you.

Kind regards,
Krystian

Hi, I installed the new beta version of the plugin in my staging environment, in my case the problem was solved!

I can confirm that this fixes the main issue ??

However, it still inserts English strings (e.g. “Card number” instead of “Kartennummer”) on the German version of the website, so the replacement fields seem to ignore the language setting of the target website (see https://imgur.com/a/SsOp19t). This was introduced with 2.9.0 as well, because 2.8.3 correctly inserts German strings on the German website version.