Problem: You need to use PHP to check if the current page or a custom post type (CPT) post is translated into its secondary language. Depending on the translation status, you want to display different text messages. Solution: We recommend using the
wpml_element_has_translations
filter to determine if a post type or a taxonomy term has translations available. For implementing this, you can refer to the WPML Hooks Reference for detailed guidance on how to use this filter. For more information, please visit the WPML element has translations and the WPML Hooks Reference.
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 further assistance is needed, please open a new support ticket.
Problem: The client is developing a bilingual site (EN + FR) using WordPress and WPML plugins and is trying to fetch data for a custom post type called 'news-post' using the REST API. However, they are unable to retrieve both English and French data for the 'news-post' custom post type. Solution: If you're experiencing this issue, we recommend trying the following steps: 1. To access the French data for your custom post type, append '/fr' to your REST API URL like this:
https://***.ca/fr/wp-json/wp/v2/news-post/
. 2. If you need to retrieve the translated ID in the REST API response, you can use the wpml_object_id hook. This hook allows you to retrieve the corresponding translation of a post, page, or custom post type in the desired language. You can then modify the API output using a filter like rest_prepare_post to include the translated version’s ID based on the specified language. For more detailed information on working with WPML tables and hooks, you can check the following documentation:
Please note that this solution might be irrelevant if it’s outdated or not applicable to your case. 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: The client is using the Divi theme and WPML plugin to create a bilingual site and needs to translate the Global English footer into French using the Divi builder, without impacting the English layout. The client prefers not to use the WPML Advanced Translation Editor. Solution: We recommend manually translating the footer by following these steps: 1. Access your site's layout posts by visiting these URLs, replacing 'example.com' with your site's URL: - http://example.com/wp-admin/edit.php?post_type=et_body_layout - http://example.com/wp-admin/edit.php?post_type=et_header_layout 2. Edit the header in the default language, switch to the WordPress editor for translations, and make the necessary changes. Please note, this manual approach is not extensively tested and support may be limited. If you translate the template again via WPML > Translations Management, these manual changes will be overwritten. To avoid conflicts, stick to a single translation method. For more detailed guidance, refer to: https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages/
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are using Elementor Pro and WPML to create a bilingual site and need to translate the site footer into French. The English footer has four logos linking to external websites, and you want to modify the number of logos in the French footer. Solution: If the layout of the footer differs significantly between languages, we recommend creating separate footer templates for each language. You can learn how to do this by following our guide on Creating Different Elementor Templates per Language with WPML. If the changes are limited to different icons and external URLs, you can use the following methods: - For icons, utilize the Media Translation module. More details can be found here: Media Translation. - For external URLs, use the Advanced Translation Editor to locate and translate the URLs. More information is available here: Translate URLs using the Advanced Translation Editor.
If this solution does not apply to your situation, or if it seems outdated, please check the related known issues at WPML 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 if further assistance is needed.
Problem: The client is using Events Calendar Pro, Toolset Views, and WPML plugins to create an event directory. The issue arises with AJAX pagination on the Inuktitut language side of the site, where the 'load more' button does not display events in the correct language. Instead of showing the Inuktitut venue names, it displays the English ones.
Solution: We recommend replacing the shortcode used in the Toolset Views template with standard fields. Instead of using the original shortcode:
This change should resolve the issue with the AJAX pagination not displaying the correct language for event venues. Please check and confirm if this solution works for you.
If this solution does not seem relevant to your issue, please do not hesitate to open a new support ticket with us.
