Problem: When you view the website/news section and select a different language using the switcher in the header menu, the English version still displays. This issue does not occur when logged into WordPress and viewing the website/news from there. Initially, custom code was used to load posts, which likely disregarded the WPML language switcher settings. After switching to the standard Elementor Post module, the translation from English to other languages failed. Solution: We recommend checking for any technical differences between your staging and live environments, such as server caching or configuration variations, which might be affecting the translation functionality. It's important to ensure that the Elementor Post module is properly configured to work with the WPML language switcher. If this solution does not resolve the issue or seems outdated, please visit our support forum to open a new ticket. We also 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.
Problem: The client is experiencing a deprecated error message when editing the Elementor Header using the WPML SEO plugin. The error message indicates an issue with the 'urlencode()' function in the 'class-wpml-wpseo-filters.php' file. Solution: We recommend disabling the debug mode in WordPress to prevent this warning from being displayed. This can be done by editing the
wp-config.php
file and ensuring the following line is included:
define('WP_DEBUG_DISPLAY', false);
For more details on debugging in WordPress, please visit: https://wordpress.org/documentation/article/debugging-in-wordpress/ Additionally, updating the WPML SEO plugin to the latest version (2.2.3 or higher) might resolve the issue. Updates can be checked and applied from the 'My Account → Downloads' section on our site or through the 'Plugins → Add New Plugin → Commercial' tab in WordPress.
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 at WPML support forum for further assistance.
Problem: The client is experiencing 'Undefined array key "value"' errors when translating a CF7 form and other elements using WPML with Advanced Custom Fields Pro. The errors occur specifically in the Spanish translations and are related to the settings of ACF field groups. Solution: 1. Ensure that the ACF Pro plugin is updated to version 6.4.3 or higher. 2. Set the ACF Field Groups to 'Not translatable' in WPML > Settings > Custom Post Type Translation. 3. Remove any duplicated field groups for languages other than the default site language. 4. After making these adjustments, re-translate the affected content. 5. If the issue persists, check if all field groups have a location setting and that they are not set for a post type that no longer exists on the site.
It's important to note that setting field groups to 'Translatable' is not recommended using the ACF Multilingual addon. For more details on configuring ACF with WPML, visit WPML's ACF documentation.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please open a new support ticket. We also 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.
Problem: The client is experiencing issues with the WPML language switcher on their privacy page. Although translations exist in the backend, only English is available in the frontend language switcher. Additionally, some translated pages open with the default WordPress editor instead of the WPML Advanced Translation Editor. Solution: 1. Ensure that all translated versions of the page are set to 'Published'. Translations in 'Draft' will not appear in the frontend language switcher. 2. To verify the default language of a page, look for the absence of the 'This is a translation of' indication. Check this option to confirm that all translations are correctly linked to the default language page. 3. Manually check each translation's publication status in the Translation Management, as there is no automatic indication. 4. To quickly identify untranslated pages, compare the number of pages listed in each language in the backend. A missing 'pencil' icon indicates that the page is not fully translated. 5. If a translation opens in the default WordPress editor, switch the translation method to the WPML Translation Editor for that page. Follow the steps outlined here: Using different translation editors for different pages
If these steps do not resolve your issue, or if the solution seems outdated or irrelevant to your specific 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 further assistance is needed, please open a new support ticket at WPML support forum.
