Problem: The client's products are not visible on the Korean website. This issue arises because the 'HT Mega – Absolute Addons for Elementor' does not include compatibility code for WPML, affecting the translation of its widgets. Solution: To make the Tabs widget translatable, add the following custom XML configuration in WPML > Settings > Custom XML Configuration tab. The config can be found in this comment.
After adding this configuration, edit the Tabs widget on the original content, save the page, and then open the WPML Translation Editor. For Widgets that are using Elementor Templates, add the following code inside includes\widgets\htmega_tabs.php at line 1050:
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 issues persist, please open a new support ticket at https://wpml.org/forums/forum/english-support/.
Problem: The client wants certain pages or templates on their multilingual website to appear only in English, even though the default language of the homepage is Korean. Solution: If you're experiencing this issue, we recommend not translating the specific pages you want to appear only in English. In your WordPress backend, switch to English by selecting EN from the top black bar. Then, create the page under the English backend. This way, the page will only exist in English unless you decide to translate it to other languages.
If this solution does not seem relevant, or if it's outdated or not applicable to your case, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If you still need assistance, we highly recommend opening a new support ticket or visiting the WPML support forum.
Problem: You are inquiring about how to apply language changes to reCAPTCHA and Google Maps when the language change button is pressed, rather than relying on the browser's language settings. Solution: For reCAPTCHA, you can manually set the language by adding the "hl" parameter in the reCAPTCHA script URL. Here is an example:
Modify the parameter based on the active language using WPML hooks or JavaScript. Similarly, for Google Maps, to force a specific language, add the "language" parameter to the Google Maps script URL. For example:
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Also, 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. For further assistance, please contact us through the WPML support forum.
Problem: The client was having difficulty translating hexagonal graph elements from Graphina charts on their website, which was developed using Elementor and saved in the "Saved Templates".
Solution: 1. We inserted custom XML configuration for the client, which should allow them to translate the radar categories. We asked the client to edit and complete the translation as shown in the provided screenshot and then check if the translation appears on the frontend.
2. For the other templates, we advised the client to refresh the primary language templates by opening the templates and clicking "update". This action would resync the templates and reveal new contents to be translated.
If you're experiencing similar issues with translating Graphina charts or Elementor templates, we recommend trying the steps mentioned above. However, please note that the solution might be irrelevant due to it being outdated or not applicable to your case. If these steps do not resolve your issue, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Should you need further assistance, please do not hesitate to open a new support ticket in the WPML support forum.
Problem: The client installed the Graphina Charts plugin and could not find the option to translate Graphina Charts in the WPML settings.
Solution: We informed the client that since Graphina Charts adds Elementor widgets, there is no need to configure anything in WPML settings for translation. If the widgets have translation support, the client can translate the content within the widgets when translating the page/post. We also noted that Graphina Charts is not listed as a compatible plugin on WPML's website and suggested that the client check the compatibility list at https://wpml.org/plugin/.
If the provided solution is not relevant due to being outdated or not applicable to the client's case, we recommend opening a new support ticket. We also highly suggest checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that the latest versions of themes and plugins are installed.
For further assistance, please contact us through the WPML support forum.
Problem:
Some of the parts on home page were not being translated, while using Elementor as page builder.
Solution:
We recommend checking the guide on Registering Custom Elementor Widgets for Translation. It's possible that some Elementor widgets may need to be recognized by WPML. By following the guide, you can ensure that these widgets are translated and displayed correctly on the frontend.
Please note that the solution provided might be irrelevant if it's outdated or not applicable to your case. We highly recommend checking the related 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 so we can assist you further.
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.
