Problem: If you're using WPML with WordPress, Elementor, and the Elementor Pro Form widget, and you notice that when translating a form's dropdown field into Italian, the options appear incorrectly as a single string instead of separate lines, resulting in a broken dropdown. Solution: We are aware of this issue and it has been escalated to our developers. A fix is planned for a future release of WPML. You can track updates on this issue by visiting the errata page: Elementor Form Widget Select Field Breaks When Translated with CTE. In the meantime, we recommend using the Advanced Translation Editor (ATE). If you prefer not to use ATE, you can opt for a manual translation approach. For guidance on using different translation editors, please visit: Using Different Translation Editors for Different Pages.
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 at WPML support forum.
Problem: The client updated their website and noticed that the language switcher incorrectly displays 'IT' instead of 'DE' in the header of the Italian page. Solution: We reviewed the issue and identified that a specific CSS code was causing the incorrect display of the language in the header. We recommend removing this CSS code to resolve the issue.
If this solution does not apply to your situation, or if it seems outdated, we encourage you to check for related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If the problem persists, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is trying to have one integrated sitemap for all languages while using WordPress SEO by Yoast but is encountering separate sitemaps for each language. Solution: If you're experiencing this issue, we recommend you follow these steps: 1. Ensure you have taken a backup of your site for safety reasons. 2. Install the WPML SEO plugin, which is necessary for the Yoast SEO plugin to function with multiple languages. You can install it from your WP Dashboard under Plugins > Add New Plugin > Commercial tab, or directly download it from here. 3. Navigate to Yoast SEO > Settings page. 4. Disable the XML Sitemap option, save changes, then enable it again and save changes. 5. Check your sitemap at https://alpitools.com/page-sitemap.xml to see if the issue is resolved. For more detailed instructions, please visit this documentation.
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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client was unable to translate multiple widgets on their website. When setting the language for one widget and saving, it would change the settings of previously configured widgets to display in all languages. Solution: We recommended deactivating the WPML Widgets plugin as it was not necessary. Instead, the client should: 1. Go to Appearance->Widgets. 2. Add the widget twice. 3. Add the translation in the second widget. 4. Set each widget to a specific language, ensuring one widget is set for each language (e.g., one in English and another in Spanish). For further details on this method, visit Translating Widgets documentation. Additionally, we suggested installing the "Classic Widgets" plugin to potentially resolve interface issues related to legacy widgets.
If this solution does not resolve your issue or seems outdated, please check the related known issues at https://wpml.org/known-issues/, verify you have the latest versions of themes and plugins, and consider opening a new support ticket for further assistance at WPML support forum.
Problem: You are trying to translate the email texts of the 'Five Star Restaurant Reservations - WordPress Booking Plugin' for your Italian website. Although you have translated the strings in the WPML string translation tool, the email notifications are still being sent using the German (DE) template instead of the Italian (IT) one. Solution: First, ensure that you have translated the specific strings related to the booking notifications. You can find these strings by searching for '[rtb-settings]template-booking-user' and '[rtb-settings]subject-booking-user' in the WPML string translation tool. Here is the link to directly access the string translation page: Translate strings. If translating these strings does not resolve the issue, it is possible that the strings are stored elsewhere in the database by the booking plugin. We recommend contacting the support team of the 'Five Star Restaurant Reservations - WordPress Booking Plugin' to inquire about the storage of these strings.
Please note that the solution provided might be outdated or not applicable to your specific case. If the issue persists, 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 needed, do not hesitate to open a new support ticket with us for further assistance.
Problem: You are experiencing an issue where the current language is being automatically added to the menu on your site using WPML, without any action on your part. Solution: We recommend checking if the "Menu language switcher" option is enabled in WPML. Here's how you can address this issue: 1. Navigate to WPML >> Languages > Menu Language Switcher section. If the language switcher is added, you can remove it by clicking on the delete icon. 2. Alternatively, you can hide the secondary languages from frontend visitors by selecting the secondary language option under WPML >> Languages > Hide languages section. For more detailed guidance, please refer to our documentation on hiding languages on the front-end.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client needed to translate text within the WPML plugin but was unable to find where to add these translations. Solution: 1. Navigate to WPML->String Translations. 2. At the bottom of the String Translation table, click on "Translate text in admin screens". 3. Search for the strings there and if found, select them and add them using the "Add to string translation" button. 4. Click on "Return to String Translations" and proceed to translate the text. For more detailed guidance, visit WPML String Translation documentation. Additionally, if the above steps do not resolve the issue, adding a custom XML configuration might be necessary.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Also, check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, please visit WPML support forum.
Problem: The client is unable to change the translation option of their ACF text fields under WPML > Settings > translation customFields because there is a lock symbol next to the fields. Solution: We explained that when the ACF field group translation settings are set to either "Simple fields across languages" or "Different fields across languages" from the ACF >> Field Groups page, it automatically sets the text field translation preference to "Translate" and locks the setting. To change the translation preference of field group fields, follow these steps: 1. Navigate to ACF >> Field Groups. 2. Edit the field group where you want to change the settings. 3. Click on the "Change option" and select the "Expert" option. 4. Individually edit each field and set the translation preferences as needed. 5. Make a minor change in the default language page, then edit the secondary language page to see if the issue resolves. For more details on the Expert mode, visit Expert translation option.
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.
Problem: The client was experiencing an issue where the Elementor template title was not displaying correctly in the second language for an alternate loop item. The first loop item was translated correctly, but the alternate loop item was not showing the translated version automatically. Solution: We recommended the following steps: 1. Edit the template in the original language (German). 2. Make some changes and save the template. 3. Update the translation template using the WPML Translation Editor. It is important not to edit the translation template directly, as changes will be lost after updating the translation with WPML Translation Editor. We also provided a link to our documentation for further guidance: https://wpml.org/faq/why-arent-my-translations-showing/
If you're experiencing this issue, we recommend you try the steps outlined 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 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. Should you need further assistance, please do not hesitate to open a new support ticket with us.
