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
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.
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.
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.
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
