Skip to content Skip to sidebar

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.

Sun Mon Tue Wed Thu Fri Sat
- 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 -
- 12:00 – 16:00 12:00 – 16:00 12:00 – 16:00 12:00 – 16:00 12:00 – 16:00 -

Supporter timezone: Europe/Zagreb (GMT+02:00)

This topic contains 3 replies, has 2 voices.

Last updated by Dražen 3 years, 11 months ago.

Assisted by: Dražen.

Author Posts
May 18, 2022 at 11:33 am #11246631

村岡 利紀

I am trying to:
I created a new post in the wordpress admin with a custom post.
The post is a repeater only.

Pattern 1 that causes the bug.
I created a Japanese post, duplicated it into English, and pressed the Translate independently button on the English page.
Edited the Japanese post, added a line above the first line of the repeater, put the contents of the field and saved.

When I opened the duplicated English page, the post was broken.
The bug is as follows
Bugs that always happen
1・ The last repeater line of the post on the English page is lost.
2. An empty line is created on the first line of the English page.

The bugs that happen are as follows
1. A part of the contents of a submitted field on a Japanese page is duplicated.

Pattern 2, in which the bug occurs.
A Japanese post is created, duplicated in English, and the Translate independently button is pressed on the English page.
Edit the English post, add a line above the first line of the repeater, put the contents of the field and save. Repeat to add 2 more rows. (Add 3 lines to line 0 of the total repeater)

Bugs that always occur
1. The contents of fields other than the added line disappears or the contents of a field are moved to another field.

Configuration
All repeater field settings are Copy Once.
Synchronise translations is checked.

What is the date to fix the WPML ACF?

We do not want the following support methods.
1・Uncheck Synchronise translations correspondence.
2・Correspond with "define ('ACFML_REPEATER_SYNC_DEFAULT' , false);".
3・Correspond with "add_filter( 'wpml_sync_deleted_custom_fields', '__return_false' );".

Link to a page where the issue can be seen:
Pattern 1
hidden link
hidden link

hidden link
hidden link

Pattern 2
hidden link
hidden link

May 20, 2022 at 6:57 am #11262733

Dražen
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+02:00)

Hello!

Welcome to WPML Support. I'll do my best to help you solve this issue.

1) Can you please confirm the issue does not happen and works fine when you uncheck "Synchronise translations"?

2) As I understand you do not wish to uncheck that option, which leads me to believe you want to have the same order and number of fields in both languages?

But since you are using COPY Once that might not work correctly. If you are using COPY ONCE and want to have a different number of subfields you might need to uncheck that option since it can not sync correctly if it is a different layout.

Please check if the issue still happens when the main repeater field is set to COPY, and the subfield to TRANSLATE or COPY.

Let me know how it goes.

Thanks,
Drazen

May 23, 2022 at 11:25 am #11279461

村岡 利紀

Hi,

Thank you for your reply.

I will answer your questions.

1) yes.

2) Because this check is in by default. Some developers forget to uncheck it, so please fix it so that it works correctly even if it is checked.

3) When I add an alternate first line in two languages and save, some field contents disappear or the bottom line is lost.

Thanks,
Naoki

May 23, 2022 at 12:45 pm #11280591

Dražen
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+02:00)

Hello Naoki,

thanks for getting back.

For now as a workaround please uncheck this or use the constant you mentioned in your first reply.

From our side, we have a fix ready for ACFML 1.11.0., which should help and fix also issue you reported here.

I will add your ticket in the dev queue and update you when versions with the fix is out.

Kind regards,
Drazen