pods are not fully translated (even with WP standard editor)

This thread is resolved. Here is a description of the problem and solution.

Problem:

The client is developing a site and trying to translate several pods with various fields using WPML. They can only translate text fields and the WYSIWYG editor field, but not checkboxes or other fields. Despite setting fields as "translatable" or "copy once", checkboxes and option fields are not showing on the translated product page.

Solution:

1) Ensure that the fields are not set as COPY in WPML > Settings > Custom Fields Translation. WPML needs stored data for the custom field to detect it.
2) There are known limitations with translating PODS checkboxes and option field labels and values. Our compatibility team is working on a workaround.
3) For immediate relief, follow these steps:

- Visit WPML > Settings > Post Types Translation and set *Translatable - only show translated items* for Pod Templates, Pods, Pod Groups, and Pod Fields.

- In WPML > Settings > Custom Fields Translation, set *Don't translate* for fields like _pods_application_method, _pods_curing, and _pods_standards_complied_with.

- Set *Translate* for fields like application_method, curing, and standards_complied_with.

- Add the following code in the

template-parts/content/content-single.php

file:

<div align='center'>
    <?php echo "<br />".pods_field_display( 'application_method' ); ?>
    <?php echo "<br />".pods_field_display( 'curing' ); ?>
    <?php echo "<br />".pods_field_display( 'standards_complied_with' ); ?>
</div>

4) Update the post in the original language and its translation.

If this solution does not resolve your issue or seems outdated, we recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket at WPML support forum.

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.

Tagged: Bug

This topic contains 7 replies, has 3 voices.

Last updated by Bigul 4 months, 2 weeks ago.

Assisted by: Bigul.

Author	Posts
October 31, 2024 at 3:40 am #16349502
philippF-8	Background of the issue: I am developing a site and trying to translate several pods with various fields using WPML. I have read that WPML supports pods translation with the regular editor. Symptoms: I can only translate text fields and the WYSIWYG editor field, but not checkboxes or other fields. Questions: What am I missing in translating pods with fields like checkboxes using WPML?
October 31, 2024 at 7:39 am #16349854
Dražen Supporter Languages: English (English ) Timezone: Europe/Zagreb (GMT+02:00)	Hello, Thanks for contacting us. While you wait for my colleague to take over the ticket, let me try to help you with the issue quickly. 1) In order to expedite handling your support requests, can you please share WPML support debug information from your site. - To give debug information, login to your site and go to WPML → Support. From there click on the “debug information” link at the bottom of the page. - Once on the “debug information” page, select the entire content of the text box and copy it. - Now go back to our support forum, find debug information box and paste it. More information on the link: https://wpml.org/faq/provide-debug-information-faster-support/ 2) It is most likely that they are set as COPY, and not meant to be translated. Go to WPML > Settings > Custom Fields Translation to double-check the settings for your custom fields. (Note, WPML will only find the fields to offer settings where there is stored data for the custom field. It's not enough just to register a custom field in Pods, you must also save some content so that WPML can detect the field from the entries in wp_postmeta.) Let us know how it goes. Regards, Drazen
November 1, 2024 at 2:20 am #16353627
philippF-8	Hi Drazen, the fields were set as "translatable" (see screenshot) and I've also tried "copy once". I've tried both the WP editor and the Advanced Translation Editor - in the ATE the fields are actually translatable but they are not shown in the translated product page. Best, Philipp
November 1, 2024 at 5:14 pm #16355683
Bigul WPML Supporter since 01/2013 Languages: English (English ) Timezone: Europe/Vienna (GMT+02:00)	Hello, Thank you for the updates. Please fill in the private details fields after a full site backup{mandatory}. I would like to access the admin area of your site for further checking. Refer to the following links for more details about our private information sharing policies. https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/ hidden link -- Thanks! Bigul
November 4, 2024 at 4:41 pm #16362498
Bigul WPML Supporter since 01/2013 Languages: English (English ) Timezone: Europe/Vienna (GMT+02:00)	Hello, Thank you for the details and login information. We will test it further. Please allow me to make a copy of your site using the Duplicator plugin (https://wordpress.org/plugins/duplicator/) for debugging the issue on our local server (in case of escalation). -- Thanks! Bigul
November 5, 2024 at 3:21 am #16363925
philippF-8	Thank you, sure go ahead with the copy as needed.
November 6, 2024 at 2:03 pm #16372432
Bigul WPML Supporter since 01/2013 Languages: English (English ) Timezone: Europe/Vienna (GMT+02:00)	Hello, Thank you for the permission. I made a copy of the site and testing it now and will get back to you soon. Please wait. -- Thanks! Bigul
November 8, 2024 at 9:40 am #16381329
Bigul WPML Supporter since 01/2013 Languages: English (English ) Timezone: Europe/Vienna (GMT+02:00)	Hello, This looks like a compatibility issue. So I am consulting with our team for an expert opinion. We will get back to you as soon as possible. Please wait. -- Thanks! Bigul
November 13, 2024 at 3:32 am #16395287
philippF-8	Thank you, I'm still very much interested in a solution. This is a commercial project and WPML claims compatibility with Pods.
November 13, 2024 at 6:20 pm #16399095
Bigul WPML Supporter since 01/2013 Languages: English (English ) Timezone: Europe/Vienna (GMT+02:00)	Hello, We are still working on this issue. As a part of our debugging procedures, I have tried to reproduce the issue in a fresh installation on our sandbox server. Because it may be a compatibility issue. We are getting the expected results in my local copy and sandbox server after the following steps. 1) Visit WPML>>Settings>>Custom Fields Translation 2) Choose Show "Multilingual Content Setup" meta box on post edit screen option and save the changes 3) Visit ELPEGUARD>>All ELPEGUARD posts 4) Open the post for edit 5) Click on Show system fields link 6) Choose Translate option for the _pods system fields 7) Apply the changes 8) Update the posts Please check the following links and attached images for more details and let us know your feedback. Sandbox Login URL - hidden link hidden link hidden link -- Thanks! Bigul
November 14, 2024 at 4:15 am #16400591
philippF-8	Hi Bigul, not sure how that solves the issue. As I've written on Nov. 1st, I've also experienced the fields show up in ATE but the thusly translated fields are not picked up in the loop element or in a normal post. As WPML states that PODS is only compatible when using the WP Editor my thought was that we can't use ATE at all. Yes, we can translate the fields in ATE but they are not working in the template, please see screenshot for clarification. That the fields show up in your sandbox (and in my install) doesn't mean they can be used. Best, Philipp New threads created by Bigul and linked to this one are listed below: https://wpml.org/forums/topic/posts-translated-to-german-shows-fatal-error/
November 14, 2024 at 7:29 am #16400852
Bigul WPML Supporter since 01/2013 Languages: English (English ) Timezone: Europe/Vienna (GMT+02:00)	Hi Philipp, Thank you for the detailed confirmation. I have shared it with our compatibility team. We will get back to you as early as possible. Please wait. -- Thanks! Bigul
November 22, 2024 at 4:35 am #16431784
philippF-8	Dear WPML team, still no result after 3 weeks. Please support this topic, as I've seen from the I've managed to trim down the issue a bit and it appears to affect only relationship fields with multiple selection (see screenshot). In general I would like your feedback on the WPML statement that WPML is compatible with PODS and can be used but only with manual translation. As you can see from the screenshot, only the WPML ATE manages to translate the fields (but they are not shown), the WP standard editor doesn't offer translation of these fields. So is this still the general recommendation to use WP standard editor? And if so, how can these field values get translated? Please give me an update. Best, Philipp
November 22, 2024 at 6:14 pm #16435007
Bigul WPML Supporter since 01/2013 Languages: English (English ) Timezone: Europe/Vienna (GMT+02:00)	Hi Philipp, Sorry for the delayed response. Currently, there are limitations in translating the PODS checkboxes and option field labels and values. Our compatibility team is actively working on finding a possible workaround for this issue. We will get back to you as soon as possible. Thank you for your understanding and patience. -- Thanks! Bigul
November 28, 2024 at 3:57 pm #16456204
Bigul WPML Supporter since 01/2013 Languages: English (English ) Timezone: Europe/Vienna (GMT+02:00)	Hi Philipp, Sorry for the delay. We are getting the expected results on the sandbox site after the following steps. 1) Vist WPML>>Settins>>Post Types Translation 2) Choose the option Translatable only show translated items for the following Post Types and save the changes - Pod Templates (_pods_template) - Pods (_pods_pod) - Pod Groups (_pods_group) - Pod Fields (_pods_field) 3) Go to WPML>>Settings>>Custom Fields Translation>>Show system fields 4) Set the Don't translate option for the following fields and save the changes - _pods_application_method - _pods_curing - _pods_standards_complied_with 5) Set the Translate option for the following fields and save the changes - application_method - curing - standards_complied_with 6) Add the following code in the template-parts/content/content-single.php file of Twenty Twenty-One <div align='center'> <?php echo "<br/>".pods_field_display( 'application_method' ); ?> <?php echo "<br/>".pods_field_display( 'curing' ); ?> <?php echo "<br/>".pods_field_display( 'standards_complied_with' ); ?> </div> 6) Update the post in the original language 7) Update the translation Please check the following links and attached images for more details and let us know your feedback. Sandbox site login URL:- hidden link Post URLs:- hidden link hidden link -- Thanks! Bigul