Translated posts shows fatal error

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.

This topic is split from https://wpml.org/forums/topic/pods-are-not-fully-translated-even-with-wp-standard-editor/

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	12:00 – 14:00	12:00 – 14:00	12:00 – 14:00	12:00 – 14:00	12:00 – 14:00	-
-	17:00 – 21:00	17:00 – 21:00	17:00 – 21:00	17:00 – 21:00	17:00 – 21:00	-

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

Tagged: Bug

This topic contains 4 replies, has 0 voices.

Last updated by Bigul 4 months ago.

Assisted by: Bigul.

Author	Posts
December 11, 2024 at 2:43 pm #16504081
philippF-8	Dear Bigul, I've recreated the post template and populated 4 products in the sandbox. The EN works as expected, but the FR throws a critical error. PHP Fatal error: Uncaught TypeError: str_contains(): Argument #1 ($haystack) must be of type string, array given in /var/www/sites/modern-mandolin/wp-includes/blocks.php:1816 Best, Philipp
December 11, 2024 at 4:45 pm #16504722
Bigul WPML Supporter since 01/2013 Languages: English (English ) Timezone: Europe/Vienna (GMT+02:00)	Hi Philipp, Welcome to the WPML support forum. I will do my best to help you to resolve the issue. The issue is existing after the initial checks. But surprisingly it is working as expected for the Dutch language - hidden link So I have escalated the ticket to our compatibility team for further debugging. We will get back to you as early as possible. Please wait. -- Thanks! Bigul
December 24, 2024 at 3:11 am #16542277
Bigul WPML Supporter since 01/2013 Languages: English (English ) Timezone: Europe/Vienna (GMT+02:00)	Hi Philipp, This bug was happening becuase of a conflict in the settings. It is working as expected after the following steps. 1) Visit WPML>>Settings>>Custom Fields Translation>>Show system fields 2) Set application_method field as Translate 3) Set _pods_application_method field as Don't translate 4) Scroll down to Post Types Translation section of WPML>>Settings 5) Set the following Custom Post Type as Not translatable Pods (_pods_pod) Pod Groups (_pods_group) Pod Fields (_pods_field) Please check it now and let us know your feedback. hidden link hidden link We have a suggestion: You can create a Taxonomy for the ELPEGUARD (elpeguard) post type (for example Application Method taxonomy) and use it instead of the Application Method checkbox field for easy workflow. -- Thanks! Bigul
December 27, 2024 at 4:02 am #16547881
philippF-8	Dear Bigul, It seems all items are translatable but not all show in the frontend. The relationship fields in the FR post still show the EN content or nothing even though they have been translated in the ATE. hidden link Please check attached screen shots. Best, Philipp
December 30, 2024 at 11:37 am #16552994
Bigul WPML Supporter since 01/2013 Languages: English (English ) Timezone: Europe/Vienna (GMT+02:00)	Hi Philipp, Sorry for the late response becuase of the holidays. Thank you for the details. I have shared the details with our compatibility team for an expert opinion. The best workaround in this case is to use taxonomies instead of Pods relationship fields, with a simple custom list and multiple select options. The translation workflow will be as follows: 1) Create a new taxonomy, Application Method Taxonomy, to replace the Application Method Pods custom field. Connect this taxonomy to the CPT Elpeguard. 2) Edit the Elementor template to use "Terms >> Taxonomy >> Application Method Taxonomy" as a dynamic field instead of "Pods field >> Application Method WPML". 3) Translate the Elementor template using ATE. 4) Translate the posts from the CPT using ATE. 5) Translate Application Method Taxonomy terms via "WPML >> Taxonomy Translation" or directly within the post's translation. -- Thanks! Bigul

The topic ‘[Closed] Translated posts shows fatal error’ is closed to new replies.