Home›Support›English Support›[Escalated to Compatibility team] pods are not fully translated (even with WP standard editor)
[Escalated to Compatibility team] pods are not fully translated (even with WP standard editor)
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.
WordPress 6.7 has introduced a new issue that impact translations, please update WooCommerce and WPML to the latest versions before you report issues. More about this here - https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/
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?
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.)
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
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.
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).
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.
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.
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:
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?
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.
