Problem: The client needed to translate the 'Next' and 'Previous' expressions on the Blog page of a multilingual website using the Avada theme and WPML. The expressions were saved in the admin but not displayed on the front-end. Solution: After gaining temporary admin access to the site, we discovered that the strings in question were located under the 'Avada' domain in the WPML String Translation interface (it was also needed to scan the theme for strings on WPML -> Theme and plugins localization
). We guided the client to navigate to WP-Admin -> WPML -> String Translation to find and translate the necessary strings.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, 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 you still need assistance, please open a new support ticket.
Problem: The client needed advice on translating Gravity Forms into English, German, and Czech, and inquired about the use of .po files for translations.
Solution: We informed the client that the .PO file included with the Gravity Forms plugin is mainly for translating the plugin's static strings and does not cover the translations for the default forms. We advised the client to use the WPML plugin to translate the forms, as they already have the Gravity Forms Multilingual plugin installed. We provided a step-by-step guide on how to translate Gravity Forms:
Additionally, we mentioned that if the client has a .PO file containing the form translations, they can import it via
WPML > String Translation
in the Import / export .PO section, which will apply the translations to the form.
If this solution is not relevant due to being outdated or not applicable to your 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 you have installed the latest versions of themes and plugins. If further assistance is needed, please contact us in the WPML support forum.
Problem: The client is transitioning from mqTranslate to WPML and wants to maintain the SEO settings for the Czech version of their website. Specifically, they wish to keep the URL ending with '/cz' instead of the default '/cs' that WPML creates.
Solution: 1. We informed the client that changing the hreflang field for SEO purposes will not alter the language slug in the URL. 2. We advised the client to create a new language with the desired 'cz' slug by following the instructions here: Editing WPML's Languages Table. 3. Next, we instructed the client to duplicate or copy all content from the current Czech language to the new one, as detailed here: Displaying Untranslated Content on Pages in Secondary Languages. 4. We clarified that the name of the new custom language should be different from 'Czech' and that the translation field on the right should contain the desired display name for the language switcher.
If this solution does not seem relevant to your situation, please open a new support ticket in the WPML support forum.
Problem: The client is receiving a pop-up warning when trying to save the English version of a page using the standard WordPress editor or the Avada Builder. The warning indicates that the site is configured to use the WPML Translation Editor. Solution: If you're experiencing this issue, we recommend switching to the manual translation mode. This will allow you to have full control over the translation and enable you to use the WordPress editor or the Avada Builder without receiving the pop-up warning. For detailed steps on how to use different translation editors for different pages, please refer to our documentation:
