Problem: If you're experiencing issues where the translated content of your custom post types is displayed using the default single post template instead of your custom template, this might be due to the templates not being translated. Solution: We recommend translating your Site Templates and Template Parts to ensure they apply correctly in different languages. First, check if these templates are available for translation at WPML > Translation Management > Dashboard. If they are not translated, create a translation job for each template or template part. You can then access and complete these translations to 100% using the WPML Translation Editor or automatic translation at WPML > Translations. Additionally, be aware of potential display condition issues when editing templates in a second language within the Site Editor. A workaround for this issue can be found at https://wpml.org/errata/template-is-not-applied-to-translated-page/.
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 is concerned about data security when using the DeepL translation option with WPML. They want to know if the data for translation leaves the site, if the AI learns from their data, and if there is a more secure translation option that doesn't involve data leaving the site. Solution: 1. When using WPML with the DeepL option, the translations are sent to our Advanced Translation Editor server, translated, and then returned to your site. 2. Our AI translation engine, which is different from the DeepL engine, does learn from your content to improve translations for your site. However, this data remains on our servers and is not transferred to external servers. For more details, you can visit our documentation on WPML AI WordPress Translation. 3. For more information on our privacy and security policies, please check Privacy and Security When Providing Debug Information for Support. 4. If you require a more secure translation option that doesn't involve data leaving the site, we recommend using WPML's Classic Translation Editor, which involves manual translation. You can switch to this editor by navigating to WPML -> Settings -> Translation Editor.
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 further assistance is needed, please open a new support ticket.
Problema: Stai cercando di tradurre alcune stringhe del plugin YITH Request a Quote utilizzando WPML, ma le traduzioni inserite non vengono applicate. Soluzione: Se stai riscontrando questo problema, ti consigliamo di seguire la procedura descritta in questa documentazione: perché le mie stringhe tradotte non vengono visualizzate sul front-end del mio sito?. Questa soluzione potrebbe non essere più rilevante a causa di aggiornamenti software o potrebbe non essere applicabile al tuo caso specifico. Se il problema persiste, ti consigliamo di verificare i problemi noti, controllare la versione della correzione permanente e confermare che hai installato le ultime versioni dei temi e dei plugin. Se necessario, apri un nuovo ticket di supporto qui.
