Problem: The client reported that all languages of a specific custom post type are listed together in the backend, ignoring the WPML language filter. Additionally, the language switch was missing in the frontend for that post type. This issue appeared without any recent updates to WPML. Solution: We identified that the issue might be related to server-side caching, as nothing had changed on the WPML side and the problem resolved itself. We recommend clearing your server cache to see if this resolves the issue. Furthermore, we are addressing similar caching issues in the upcoming WPML 4.9 release. You might want to test the beta versions to see if they resolve your issue:
If this solution does not apply to your case, or if it seems outdated, we highly 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 issue persists, please open a new support ticket.
Problem: You are trying to synchronize a 'Post' relationship field automatically when translating content using the Advanced Translation Editor (ATE). You have two Custom Post Types (CPTs): a parent CPT and a child CPT. The child post uses a 'Post' relationship field to select the parent, but when translating from English to German, the field in the German post does not automatically populate with the ID of the corresponding German parent, leaving the relationship field empty. Solution: This issue is recognized and will be addressed in a future WPML release (version 4.8). Meanwhile, you can use the
wpml_object_id
hook as a workaround. Set the custom field to 'COPY' so that the translation retains the POST ID (even if it's not the translated one). Use the following PHP code to translate the POST ID in the current language:
This code will help display the correct translated post ID on the frontend. Remember, the empty field in the backend is a visual bug and does not affect the actual functionality.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Also, check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, please contact our support at WPML support forum.
Problem: The client is experiencing an issue where WPML replaces German strings with English strings in custom fields when a translator updates an existing post. This problem occurs across multiple post types and is suspected to be related to the Advanced Translation Editor.
Solution: We recommend setting the affected custom fields to "copy" so they are not editable in the translation editor and are always copied directly to the translation. This should prevent the fields from being overwritten. Here is a guide on managing custom field translations: Translating Custom Fields.
If the issue persists, consider disabling the WPML editor and continue using the manual method for translations. Alternatively, if using the Advanced Translation Editor, ensure that numerical values are correctly configured for translation by adding a specific code snippet to the functions.php file of your theme. More details can be found here: Translating Numbers.
If these solutions do not resolve the issue or if they seem outdated or irrelevant to your specific case, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket for further assistance at WPML Support Forum.
