George Botsev

Hello!
We are working on fixing this.
Can you check if you go to woocommerce-multilingual/classes/multi-currency/payment-gateways/class-wcml-currencies-payment-gateways.php
and add this:
add_action( 'init', array( $this, 'init_gateways' ) );
In the add_hook() method

Hello!
I could not reproduce this issue in my test setup.
Do you have anything in the browser console?
Have you tried to activate debug logging and check if there are notices and warnings there?

Perhaps you should try a minimal setup with all latest versions of our plugins on a staging site if you can reproduce the issue?

Hello and thank you for contacting us.
Cloning is not needed.
When you translate with WPML, a translated product is being created.
You can check our documentation in https://wpml.org/documentation/related-projects/woocommerce-multilingual/#translating-products

Hello and thank you for reporting this case.
My colleague Sergey is vacation this week, however I have reproduced the problem and escalated the issue to our developers.

Hello and thank you for contacting us.
Sorry for my late reply here but I missed the notification for your ticket.

I suggest that you try our latest beta of the WPML plugin and WooCommerce Multilingual.
You can read more here: https://wpml.org/2019/08/wpml-4-3-beta-1-with-much-faster-string-translation/

If you have further performance issues, please open a ticket in our support forum at wpml.org where we can help you with the analysis process for the performance.

Hello and thank you for contacting us.
As far as I am aware, WooCommerce Germanized offered custom payment methods / gateways that were different from the ones that come with WooCommerce.
Having said that, I guess you already scanned the plugin from WPML > Theme and Plugin localization page and you already translated the string in question?

Can you check for the strings that were not translated in the e-mail and perhaps remove their translation in WPML > String Translation and try and re-translate them? Sometimes this fixes the problem.

If this does not help, then I am afraid that we would need to debug this in more detail, so I suggest that you open a new ticket in our forum at wpml.org where we can get access details to your site securely and check the issue.

Hello and thank you for contacting us.
I will consult with our developers.
However, I know for a hook: wcml_before_multi_currency_ui that might work for you probably.
You might want to check that out.

I am sorry for that.
I am sure that your ticket will be taken and assigned to one of our supporters soon.
Please link the ticket here if possible.

That is strange.
Would it be possible that you open a ticket in our support forum at wpml.org so that we can better help you – we need to get access to your site and debug the issue further, as I was unable to reproduce that issue in my testing environment with all of our latest plugin versions?

Hello and thank you for contacting us.
This is a bug and I will report it to our developers.
Thank you for reporting that.

Hello and thank you for contacting us.

Can you tell me how can I try to reproduce the problem – do you have some steps that you take, or some page that you visit and you see that problem?

You also mentioned that the problem started two days ago – do you recall what changed in the past days?
Did you update something or change some settings?

Hello again!
I tried to check for that problem that you mentioned.
Unfortunately, I did not manage to get the plugin that you are using as that is a premium plugin.
Looking at our code I can only guess where the problem could be – it might be in the class WCML_Url_Filters_Redirect_Location in \woocommerce-multilingual\classes\url-filters\class-wcml-url-filters-redirect-location.php

If the plugin that you mentioned uses the hook woocommerce_get_checkout_payment_url, it is possible that it is redirected.

However all this is just a guess and we will need the plugin in question and to setup a test environment where we can debug this properly.

Please open a new ticket in our support forum at wpml.org where we can securely ask you for access or plugin versions/test environments so that we can help you with this problem.

Hello!
Sorry, for the late reply – for some reason I missed the notification for this topic thread.
I am attempting to check the issue now.

Hello!
As far as I see, the data from that plugin is indeed saved to “_gravity_form_data”
I am not sure if this is going to work, but perhaps you should try to add this to the custom wpml-config tab in WPML > Settings

<wpml-config>
<custom-fields>
 <custom-field action="translate">_gravity_form_data</custom-field>
</custom-fields>
</wpml-config>

After that, you might be able to translate that field and just change the ID part of that field to be the Gravity Form that you want to display there.

Another way would be to set the field to “ignore” (translate may also work) instead and perhaps then use the native WooCommerce editor and edit the translation and change the value.

I am not sure if this is going to work, as this is somewhat of a workaround/hack that is not officially supporter in my opinion.

Hello!
Depends very much on the site setup, which features it uses and the changes that you would want to do and the time and if the site would be accessible during the time that you switch off the plugin.
If you change things that should be the same between languages – there could be huge issues. Like prices, stock quantity, availability and others

Yes, stopping the plugin will affect the end-users that visit the site and orders, emails, currencies and stock quantity would be affected so using a maintenance mode for the duration of the change is a must if you ask me.

In the end, I would not recommend disabling the plugin – especially for bulk changes as some values that need to be synchronized between original and translations might not be synced and that could cause bigger problems in the works of the site after that point. Perhaps you need to select a smaller batch of products to process or rising your server parameters to accommodate the increased load during that operation.