[Resuelto] Can't translate Repeatable Field Group with WPML Classic Translation Editor

[Autor]

Mensajes

[fred-r.M]

I am trying to: W are having in a Field Group a Repeatable Field Group with 3 additional fields. We like to translate them but this isn't working, as we don't see the translation in the WPML Classic Translation Editor

We followed this document: https://toolset.com/course-lesson/translating-repeatable-field-groups/

Link to a page where the issue can be seen:

I expected to see:

Instead, I got:

[Jamal]

Hello and thank you for contacting Toolset support.

I logged into your website and inspected the existing RFGs, there is only RFG out there. It is assigned to the Products post type. I am afraid, you missed the first step of our tutorial. The associated post type(product) is not configured to be translatable. Check this screenshot enlace oculto
https://toolset.com/course-lesson/translating-repeatable-field-groups/#1-make-the-associated-post-type-translatable

Make the Products post type translatable, and try to translate a post, I am sure you will get the RFGs item in the translator editor.

I hope this helps. Let me know if you have any questions.

[fred-r.M]

Dear Jamal

I checked all settings as described, but I still not see the fields to translate:

The fields I need are:

wpcf-itinerary ((Repeatable Group))
wpcf-itinerary-intro-title
wpcf-stage-title
wpcf-meals
wpcf-description

We don't use the WPML's Classic Translation Editor.

If You might check it out, what I might have done wrong?

Regards,

Simon

[Jamal]

All the settings seem correct to me. I will need to take a copy of your website and analyze it locally. Can I install a plugin(Duplicator) to take the copy?

[fred-r.M]

Dear Jamal

You find the package from the duplicator already ready to download.

Regards,

[Jamal]

Thank you! I took a copy and confirm the issue on my local setup. It also seems to be a new bug, because I was able to reproduce this issue on a clean install too. I am escalating this to our 2nd Tier team for further analysis, and I'll get back to you as soon as possible.

On the other hand, if I disable WooCommerce Multilingual(WCML), and update the RFG items of a product, they get picked for translation.
I wouldn't recommend temporarily disabling WCML as a workaround. Especially, because several parts of the store rely on WCML(checkout, cart, etc.). So, if you would like to try it, please take a database backup before doing it.

[fred-r.M]

Dear Jamal

Thanks for the reply, and sorry for our late reply.

We are somehow aware about the WCML disabling. So You advise as first, to disable it, to get the fields for translate, then enable it for all other stuff we need for it?

[Jamal]

Well, I did reproduce the issue with the Classic Translation Editor(CTE), but the issue was not reproduced with the Advanced Translation Editor(ATE). You can log in to my test site with this URL enlace oculto

And you can see on this product, that the RFG fields are picked for translation, and translated, using the ATE enlace oculto

So, I'd like to ask, what editor would you want to use for translating the products? The classic or the advanced editors?
If you want to use the Advanced editor, enable it in WPML->Settings, then try to translate a product and let us know if the RFGs will be picked and translated.

If you would want to use the Classic Translation Editor or to translate manually, I'll check again with our 2nd Tier team and get back to you.

[fred-r.M]

Dear Jamal

We prefer to use the Classic Editor, especially as we already did a lot of translations with it.

For a futured project I will keep in mind, to use the Advanced Editor.

[Minesh]

Jamal is on Vacation. This is Minesh here, let me step-in here.

We emphasize to use Translation Editor that is the suggested workflow for the translation. Even I will report the issue if confirmed then it will take long time as its totally depends on our Devs predefined priority and current engagements and there is no ETA when will the official fix will be offered for this issue.

I suggest you should go with translation editor as of now.

[fred-r.M]

For now, this issue is resolved. Even if we not use the Advanced Translation Editor(ATE). We was able to get it done, as the fields was "copied" over, and we was able to fill with the translation. Only the item title we kept in English, the fields in each item we could add our translation.