[Resolved] xml config option to translate repeater custom fields

Hello,

Thank you for the updates. I review your settings and noticed the fields are being setup with the Advanced Custom Fields plugin, we have specific instructions to deal with ACF fields you can find at: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/. In your case it seems you are defining the fields using a code approach, in those cases, you would indeed need to register the fields for translation manually by code. Reviewing your code once again, I don't think it is correct, you have the following:

<wpml-config>
    <custom-fields>
        <!-- START: Generated by wpmlConfigUpdate.js -->
        <custom-field action="copy">
            itbl_customers_cs_*_itbl_customers_cs_results_rows_*_itbl_customers_cs_results_row_image
        </custom-field>
    </custom-fields>
</wpml-config>

Here there's no direct reference to which fields should be registered, there's no 'key name' attribute being used, also, the wildcards is not correct, the correct syntax should be something like that:

<wpml-config>

<custom-fields>
    <custom-field action="copy">parent-field-key-name</custom-field>
</custom-fields>
 
<custom-fields-texts>
 <key name="parent-field-key-name">
   <key name="*">
     <key name="attribute-to-be-copied" />
   </key>
 </key>
</custom-fields-texts>
 
</wpml-config>

Please, review our instructions carrefully at: https://wpml.org/documentation/support/language-configuration-files/#custom-fields if you need to keep your manual registration approach and register it accordingly instead of using the script to generate your custom XML code. It is recommended to follow the procedures at: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/ for fields created using ACF as said before.

Please, let me know if it helps, have a nice day.

Hello,

Thank you for the updates. I think you are missing some concepts here, at first it always recommended that you register your fields right from the WordPress Dashboard > Custom Fields > Fields Groups exactly as instructed at: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/ this is how you could garantee the correct worflow to define the translation preferences for your fields.

The wildcard syntax wouldn't apply for your particular case (I didn't entirely understand your request previously, this is why I mentioned the XML code approach), instead you can set the preference for these fields right from the post editing screen at the 'Multilingual Content Setup' section. So, no need for XML configuration, just set your translation preference for your field and you should be ready to go. Is there any reason to choose a different workflow?

Hope it brings some more clarifications, have a nice day.

Hello,

Thank you for the updates. I understand your points, before asking for a second opinion from our second level suppor team, I would like to give a step further and digging more into this issue. For that, I would appreciate the complete instructions on how to see the code where you are defining your custom fields and also I would need to proceed with a copy of your website, so, I can inspect it without interfering in your website. Please, consider:

To best troubleshoot the issue, please make a snapshot of your site using the Duplicator plugin: https://wordpress.org/plugins/duplicator/. This will allow me to try and duplicate the error so that I can run further tests without interrupting your live site.

Once the snapshot is complete, either upload the snapshot ZIP file and the installer.php file to a file sharing service such as Dropbox (and share the link in your reply) or right click the Duplicator links in your wp-admin and paste in your reply.
Please note: It is important to reduce the size of the package so please exclude some paths like /cache or /uploads and also exclude archives and media files.I will also need the username and password of an account that was created BEFORE creating the duplicator package.I will enable the next reply to be private so only you and I have access to it!

Thank you for your collaboration. Have a nice day.