55XX Casino login Philippines.Claim Your Free 999 Pesos Bonus Today

Resolved mundial
(@mundial)

4 years, 12 months ago

Hi,
Few weeks ago I reported a conflict between Translatepress and WooCommerce Redsys Gateway:

“The problem comes when I try to make the payment from the checkout page translated, when I am on the payment gateway (accessing from xxxx.com/checkout/?lang=en ) in the product description I see:
Product description: #! Trpst # trp-gettext data-trpgettextoriginal = 5684 #! Trpen # Order #! Trpst # / trp-gettext #! Trpen # 6761
Instead of
Product description: Order 6761
”
Your response was:

“We’ve checked at your site and noticed the issue.
We will try to investigate further in the next days, but we don’t guarantee that we will have a reasonable solution.”

Please give me some feedback about the state of the issue as if it’s not compatible I must change the translation plugin.

Thanks

Viewing 5 replies - 1 through 5 (of 5 total)

Thread Starter mundial
(@mundial)

4 years, 11 months ago

The question is Redsys Lite and Woocommerce are creating the endpoint ?WC_Gateway_redsys? and then creates the URL https://xxx.com/?wc-api=WC_Gateway_redsys then your plugin add /?lang={en} to the endpoint, so the new URL is https://xxx.com/?wc-api=WC_Gateway_redsys/?lang={en} this cause the error as the URL is not valid.

Is not possible to add exceptions in your plugin?

Best

Dragos
(@dragosvrejiu)

4 years, 11 months ago

Hello,

Yes , it is possible to exclude certain elements from being translated using the data-no-translation attribute.

Please check our documentation:https://translatepress.com/docs/developers/exclude-certain-text-or-element-from-being-translated/

With the best regards,

Thread Starter mundial
(@mundial)

4 years, 11 months ago

With this attribute is possible to exclude elements from being translated, but is possible to exclude the “?lang={en}” after the URL and change to xxx.com/en/ only in checkout page? if the “permanlink” of the URL created by WooCommerce is the URL of the Gateway callback I think problem should be resolved.
Thanks

Paul
(@paulschiretz)

4 years, 11 months ago

Similar issue but with Stripe for Woocommerce Gateway here: https://www.ads-software.com/support/topic/conflict-with-stripe-gateway-for-woocommerce/

Any help would be welcome!

Thanks
Paul

Dragos
(@dragosvrejiu)

4 years, 10 months ago

Hello @mundial,

I have tried replicating your issue and didn’t come across the gettext problem.

However, can you try disabling our Language by GET-parameter add-on ?

That’s the reason why “?lang={en}” is added to the endpoint.

We recommend using that add-on only if your permalinks are not working.

Please keep me updated on the state of your issue.

With the best regards,

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Translatepress conflict with WooCommerce Redsys Gateway’ is closed to new replies.