Problema: Il cliente deve sostituire il testo "Sold" con "Coming soon" per i prodotti sul sito in inglese. Soluzione: Se "Sold" è la traduzione di una stringa già esistente in italiano, il cliente deve cercare la stringa da modificare nella sezione Traduzione Stringhe di WPML. Se invece "Sold" è la stringa originale, WPML non permette la modifica delle stringhe originali, ma solo delle loro traduzioni.
Se la soluzione proposta non è applicabile al tuo caso, potrebbe essere perché è obsoleta o non adatta alla tua situazione specifica. In tal caso, ti invitiamo a aprire un nuovo ticket di supporto. Ti consigliamo inoltre di controllare la pagina dei problemi noti, verificare la versione della soluzione permanente e confermare di aver installato le ultime versioni dei temi e dei plugin.
Problem: The client needed assistance with translating BuddyBoss Group Types using WPML. Solution: 1. Navigate to WPML > Settings > Custom Field Translation and click on "Show system fields". 2. Locate the fields as shown in the provided screenshot here https://wpml.org/forums/topic/buddyboss-group-type-translation/#post-15380730 and set them to "Translate". 3. When editing a Group in the WordPress Editor, ensure the correct Group Type is selected in the right sidebar. 4. Switch the language using the top admin bar and verify that the translation uses the translated Group Type.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we encourage you to check the related known issues and confirm that you have the latest versions of themes and plugins installed. If necessary, please open a new support ticket for further assistance.
Problem: The client inquired about the possibility of adding AI translators, such as the ChatGPT API, to the WPML translation widget. Solution: We informed the client that currently, there is no integration between ChatGPT/AI translation services and WPML. We do have plans for potential integration in the future, but we cannot provide an estimated time of arrival as it is still in the feature request stage. We have taken note of the client's interest and have added their vote to the feature request.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If so, we encourage you to open a new support ticket for assistance. We also 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.
Problem: The client is developing a site with WPML and needs to set Italian as the default language after initially creating content in English. They are concerned about potential issues with changing the default language in WPML and how to configure the site so that visitors who enter
https://mysite.com
are redirected to the Italian version of the site. Solution: We recommend setting Italian as the default language from the start and translating the theme from there. Theme strings will still be identified as English, but this will not affect the content. If the client has not yet created content, this is the best approach to avoid issues later on. .
If this solution is not relevant due to being outdated or not applicable to the client's case, or if further assistance is needed, we highly recommend 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. If the issue persists, the client should open a new support ticket: Contact WPML support.
Problem: The client is concerned about the convoluted HTML structure generated by WPML, specifically the excessive classes within the language switcher elements, and is seeking a simpler structure.
Solution: We acknowledge the client's concern and explain that the current structure is maintained for backward compatibility. However, we are open to considering this as a feature request and will register it in our system for potential review and implementation in the future. In the meantime, we recommend creating a custom language switcher by following the instructions in our documentation: Custom Language Switcher.
Please note that the solution provided might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we encourage you to 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. If further assistance is needed, please contact us through the WPML support forum.
Problem: The client wants to know if it's possible to bypass the frontend step when sending a login to a translator for review, allowing direct access to the advanced editor from the backend to save time. Solution: We currently do not have a feature that allows direct access to the advanced editor from the backend without going through the frontend. We have taken note of this request and suggested it as a feature request.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If this is the case, we recommend opening a new support ticket. We also 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. If you need further assistance, please contact us on the WPML support forum.
