Translations not working since update to 8.1.0

Hi @gerold1968,

By default, Stripe detects the browser’s locale and uses that as the default. More info: https://stripe.com/docs/stripe-js/reference#stripe-elements

Are you having difficulties translating the payment form placeholder text? If so, you can follow the guide shared here: https://woo.com/document/stripe/customization/translate-placeholders/

I hope this helps! Please let us know how it goes or if you need further assistance.

Hi, no it′s about some strings I cannot translate using the new checkout experience. I guess this is because everything there is loade via i-frame as I found out by inspecting the site.

In my case the strings for eps-payments and giropay-payments have to be changed to fit my needs, whcih was no problem with the legacy checkout…

Pls have a look at the screenshots: the translation for these strings has to be changed:

https://snipboard.io/0jW7b5.jpg

https://snipboard.io/jLvsN8.jpg

• This reply was modified 7 months, 4 weeks ago by gerold1968.

Hi @gerold1968,

In my case the strings for eps-payments and giropay-payments have to be changed to fit my needs, whcih was no problem with the legacy checkout…

In this case, you can continue using the legacy checkout. All you need to do is turn off the new checkout experience and use the shortcode on the checkout page.

the translation for these strings has to be changed:

You know that these are coming from Stripe, and unfortunately, there isn’t a built-in way to alter them. However, you can use custom code to make those changes. Feel free to create an enhancement or bug report in our Github repo. Our developer will then be able to check it out and provide further insights.

We also recommend asking development questions on the #developers channel of the WooCommerce Community Slack. Many of our developers hang out there and will be able to offer insights into your question.

You can also seek help from the following:

• A local web developer
• Codeable.io
• WooExperts

I wish I could help more, but hopefully, this gets you going in the right direction to get the job done.

In this case, you can continue using the legacy checkout. All you need to do is turn off the new checkout experience and use the shortcode on the checkout page.

Hmm… seems to be not such a great idea as the plugin itself says the legacy checkout will stop working for some payment methods in a month or so…

You can also seek help from the following:

Are you serious? You suggest to hire a paid expert to get false translations of a plugin correct?

?? hey @gerold1968

Kindly note, by default:

• Stripe detects the locale of the browser and uses that as the default. Please see the Stripe documentation for more details.
• These placeholders cannot be translated through your site since the form is loaded in an iframe — meaning that it’s not technically on your site.
  • Stripe handles the translation on their end.
  • This means that some of the standard methods for translation and localization outlined here will not work.

If you are not using the new checkout experience, you can change the locale with the wc_stripe_elements_options filter.

Further details can be found in the related document, linked here, for your convenience.

seems to be not such a great idea as the plugin itself says the legacy checkout will stop working for some payment methods in a month or so…

I’m not aware of such development, I’m afraid. Could you share further details on where this is published? Meanwhile, the additional payment method documentation can be found linked here.

I hope this is helpful!  We look forward to your response. In the meantime, please let us know if you have any further questions or concerns.

I’m not aware of such development, I’m afraid. Could you share further details on where this is published??

This is what can be read within your own plugin settings:

Enable the legacy checkout experience
If you enable this, your store may stop processing payments in the near future as Stripe will no longer support this integration.?Learn more

Furthermore giropay payment gateway isn′t working with the legacy version right now and customers cannot pay, but are shown an error message:

The Sources API has been deprecated, and we are no longer allowing new integrations. Please follow our migration guide to integrate with the Payment Intents API: https://stripe.com/docs/payments/payment-methods/transitioning

Hi @gerold1968,

Furthermore giropay payment gateway isn′t working with the legacy version right now and customers cannot pay, but are shown an error message:

Thank you for the additional details. We understand you’ll need to continue using the new checkout experience, however you need to customize some strings on it. However, please keep in mind our support scope is meant for the plugin as it is and to cover for any issue or bug related to the plugin’s functionalities. I’m afraid customization is beyond our support scope (learn more here).

I understand hiring a developer for this is not ideal for you at the moment, so I could recommend reaching out to Stripe about this to see what can be done on their end.

I can also recommend the Woo Developer Resources Portal for resources on developing for Woo, and you can also visit the WooCommerce Facebook group or the #developers channel of the Woo Community Slack. We’re lucky to have a great community of open-source developers for Woo, and many of our developers hang out there, as well.

Thanks!
-OP