Problem: The client was experiencing an issue where Elementor container templates translated into Russian were still displaying in English on the Russian version of the site, despite using the correct translated shortcodes.
Solution: The issue was resolved by modifying the code snippet used in the template. The original code forced the template to revert to English after switching languages, which prevented the Russian translation from displaying. The corrected code snippet ensures that the template switches back to the original language after fetching data in English, allowing the Russian version to display correctly. Here is the corrected code:
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 problem persists, please open a new support ticket.
Problem: The client was unable to see shortcodes within HTML table cells in the translated version of their page. The shortcodes were not appearing in the WPML Advanced Translation Editor (ATE) or on the translated page itself. This issue was observed even after switching between the old and new versions of the ATE.
Solution: The client discovered that the issue was related to how data was being fetched and displayed based on the site's current language. They resolved the problem by ensuring that the data fetching function always operated in the default language, regardless of the current language of the site. This was achieved by adding the following lines of code around the data fetching function:
This solution ensured that the data was correctly fetched and displayed in all languages. If you're experiencing similar issues, we recommend checking your data handling functions to ensure they are compatible with WPML's language switching functionalities.
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 has translated a formidable form using WPML, but some translations are not displaying correctly. Specifically, certain fields remain in the original language despite being translated. Solution: We recommend checking the WPML -> Strings Translation section to ensure all necessary strings are translated. For fields not showing as translated, such as '147_field-2941-description', it's crucial to verify their translation status in WPML and update them if they are incomplete. Additionally, if encountering issues with specific strings like '[2850]', which refers to another field ID, it may help to remove and re-add the entry or adjust the string directly in the formidable form settings or WPML string editor. If duplicate strings are found in the string editor, deleting the outdated versions can resolve display issues.
Please note that this solution might be outdated or not applicable 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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client needed to access translated product attributes in WPML and was attempting to modify the code to get attributes in a specific language ('ru' for Russian), but the applied changes were not working.
Solution: 1. We informed the client that custom coding is beyond our support scope and directed them to our support policy for clarification. 2. We provided links to our hooks reference, which could help in finding the necessary information to solve the problem:
3. We requested the client's Debug information to better understand the site configuration. 4. We provided a code snippet that retrieves the translated value and label of product attributes, which works based on the page's language. The code is available on Pastebin: https://pastebin.com/0HqyaRqw.
If this solution does not apply to your case, or if it seems outdated, we recommend opening 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. For further assistance, please visit our support forum: WPML Support Forum.
Problem: You need to update a stored exchange rate for a currency using an API call with WPML and WooCommerce Multilingual.
Solution: 1. WooCommerce Multilingual (WCML) settings are stored in the
1
wp_options
table, under the option name
1
_wcml_settings
. You can update the rate in that option with custom code. 2. Use the filter hook
1
wcml_exchange_rates
to set the exchange rate programmatically. For more details, refer to our documentation. 3. Alternatively, you can use a third-party plugin to update the exchange rate automatically from an API. However, please note that third-party plugins are not tested by us, so we cannot guarantee compatibility with WCML. For an example of such a plugin, see this article. 4. If you are not comfortable with coding, we recommend contacting one of our certified partners from this list: WPML Contractors.
If this solution doesn't look relevant, please open a new support ticket in our support forum.
당사는 웹사이트와 서비스를 최적화하기 위해 쿠키를 사용합니다.
사용자의 동의를 통해 탐색 행동과 같은 데이터를 처리할 수 있습니다.
동의하지 않으면 일부 기능에 영향을 미칠 수 있습니다.
기능적
항상 활성화
웹사이트가 올바르게 작동하고 통신하는 데 필요합니다.
기본 설정
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
통계
당사는 이를 사용하여 사이트의 통계를 분석합니다.
수집된 정보는 완전히 익명으로 처리됩니다. 익명 통계 목적으로만 사용되는 기술적 저장 또는 접근입니다. 소환장, 인터넷 서비스 제공자의 자발적인 협조 또는 제3자의 추가 기록 없이, 이 목적으로 저장되거나 검색된 정보는 일반적으로 귀하를 식별하는 데 사용할 수 없습니다.
