Please make sure to update to WPML 4.3.6 and check our list of Known Issues before reporting

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Author Posts
November 2, 2019 at 8:42 pm

sophieZ-2

Hi,

since the update from version 4.6.7 to 4.7.2 the instruction text for bank transfer and the bank data (see screenshot 1) are placed twice in the confirmation mail which is sent to the customer (see screenshot 2):

Screenshot 1: hidden link
Screenshot 2: hidden link

If I deactivate the WooCommerce Multilingual plugin or return back to 4.6.7 the information is placed only once in the mail correctly. (But returning back gives me a warning in the backend that I should update to have WPML work correctly).

Could you help?

Thanks!

Best,
Georg

November 5, 2019 at 8:38 am #4886261

Carlos Rojas
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/Madrid (GMT+01:00)

Hello Georg,
Thank you for contacting WPML support.

1.- We released a new version of WPML plugins, including WCML plugin too. I would like to ask you to update all WPML plugins and double check if the issue persists with this latest version.

2.- Please increase the PHP Memory Limit. Minimum requirements are 128Mb: https://wpml.org/home/minimum-requirements/
You can add this to wp-config.php to increase WP memory:

/** Memory Limit */
define('WP_MEMORY_LIMIT', '128M');
define( 'WP_MAX_MEMORY_LIMIT', '128M' );

- Add it above the line /* That's all, stop editing! Happy blogging. */

Kind regards,
Carlos

November 5, 2019 at 3:27 pm #4890911

sophieZ-2

Hi Carlos,

Thanks for your reply. I have updated all plugins and the WP Core to the latest versions and increased the PHP memory to 256MB. The error still occurs though:

Order with active WooCommerce Multilingual:
hidden link

Order with DEACTIVATED WooCommerce Multilingual:
hidden link

Still need help.

Thanks a lot!

Best,
Georg

November 5, 2019 at 3:33 pm #4891023

Carlos Rojas
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/Madrid (GMT+01:00)

Hi Georg,
Thank you very much for your feedback.

Could you describe the step to edit the original text in the confirmation email?

Regards,
Carlos

November 9, 2019 at 2:21 pm #4918307

sophieZ-2

Hi Carlos,

since it's easier to explain via video you you can find my answer here:
hidden link

Thanks!
Best,
Georg

November 9, 2019 at 7:59 pm #4919075

Carlos Rojas
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/Madrid (GMT+01:00)

Hi Georg,
Thank you very much for the screencast 🙂

I'm consulting our specialists about this issue. I will get back to you as soon as I get an answer from them.

Thank you very much for your patience.
Regards,
Carlos

November 12, 2019 at 8:02 am #4929453

Carlos Rojas
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/Madrid (GMT+01:00)

Hi Georg,

Our specialists kindly requested to reproduce this issue in a new test site. I have created a fresh new WordPress install with WPML plugins installed and setup already so you can reproduce the issue. I leaved Woocommerce and Woocommerce Multilingual so you can configured and reproduce the issue.

You can automatically log in the test site by following this link: hidden link

You can see the emails sent in this link: hidden link

Could you tell me if you where able to reproduce the issue?

Regards,
Carlos

November 16, 2019 at 3:50 pm #4958849

sophieZ-2

Hi Carlos,

Unfortunately I am not able to reproduce the error in your test site. I was able to find out that the error occurs only if the Woocommerce Multilingual plugin AND the plugin "
PayPal for WooCommerce" are enabled (which I need for PayPal Express). As soon as one of both plugins are disabled this error doesn't appear anymore. Would you be able to debug this on my site with the login data I provided in my initial post?

Thanks a lot!
Best,
Georg

November 18, 2019 at 11:27 am
November 25, 2019 at 5:03 pm #5015875

sophieZ-2

Hi Carlos,

my issue is not resolved yet (I did not have the time yet to try the new test environment) but the ticket has been set to resolved.
Could it be reopened, pleas?

Thanks!
Best, Georg

November 25, 2019 at 5:11 pm #5015901

sophieZ-2

Hi Carlos,

Thanks for providing the staging setup. But how is this different from the staging set-up I provided (including login data) in my initial e-mail? There you can reproduce the problem and all plugins are installed. It would take me hours to install and set-up all the plugins in your staging environment (install woocommerce, set-up products and payments, install paypal and so on). I do not see the benefit how this could help your better debug compared with my staging setup.

Thanks!
Best,
Georg

November 26, 2019 at 8:22 am #5018987

Carlos Rojas
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/Madrid (GMT+01:00)

Hi Georg,
I'm sorry for the delayed answer, it seems I lost track of this ticket because it was automatically closed by mistake.

I didn't know the site you shared was a staging site. I have updated our specialists and I'm waiting from an answer on their side. I will get back to you as soon as possible.

Thank you very much for your patience and understanding.
Best regards,
Carlos

November 27, 2019 at 2:26 pm #5030055

Carlos Rojas
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/Madrid (GMT+01:00)

Hi Georg,

Could you tell me if the issue persists with the lates version of the plugins (WPML 4.3.5 / WCML 4.7.5).

Regards,
Carlos

November 27, 2019 at 6:01 pm #5031775

sophieZ-2

Hi Carlos,

I have just updated all WPML related plugins to the latest versions. Unfortunately the error still persists.
Thanks a lot for the debugging!
Best,
Georg

November 28, 2019 at 10:24 am #5034801

Carlos Rojas
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/Madrid (GMT+01:00)

Hi Georg,
Thank you very much for your answer.

I just updated our compatibility specialists that are working on this issue.

Regards,
Carlos