Problema: Dopo l'aggiornamento di WPML alla versione 4.8.6, non è chiaro come attivare il nuovo editor con "Traduzione dei Media" e se è attivo o disattivo. Soluzione: Dalla schermata che hai inviato, possiamo confermare che la funzione "Traduzione dei Media" è attivata correttamente. Quando traduci una pagina, i testi ti appariranno direttamente nell’editor di traduzione di WPML, dove potrai tradurli e salvarli senza problemi. Per le immagini, il titolo e l’alt verranno assegnati automaticamente; anche se non desideri tradurre il titolo di un’immagine, ti apparirà comunque il campo title nell’editor di traduzione e potrai semplicemente copiarlo.
Se la soluzione proposta non risolve il tuo problema o sembra non essere più attuale, ti invitiamo a consultare la pagina dei problemi noti e a verificare che tu abbia installato le versioni più recenti dei temi e dei plugin. In caso di ulteriori dubbi o problemi, ti consigliamo di aprire un nuovo ticket di supporto sul forum di supporto WPML.
Problem: You are developing a site using WPML in Elementor and are trying to integrate language switching functionality. You are unable to find a way to activate the WPML language selector/editor within Elementor and view it on the frontend for quick translation modifications. Solution: Unfortunately, it is not possible to directly access the translation or switch to a version in another language from within Elementor. To modify a translation, you should go to Pages → Edit Page and open the translated version from there.
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 this does not resolve your issue, please open a new support ticket.
Problema: Stai riscontrando un problema con i formati dei post e in particolare con la galleria che non funziona quando WPML è attivo, ma funziona quando WPML è disattivato. Il problema si verifica specificamente con il tema ArcHub. Soluzione: Abbiamo testato con il tema Twenty Twenty One e non abbiamo riscontrato problemi, il che suggerisce che il problema potrebbe essere specifico del tema ArcHub. Se l'autore del tema non riesce a risolvere il problema, può contattarci attraverso il nostro programma Go Global per aiutarlo a rendere il tema compatibile con WPML.
Se questa soluzione non risolve il tuo problema o se ritieni che sia irrilevante perché potrebbe essere superata o non applicabile al tuo caso, ti consigliamo di aprire un nuovo ticket di supporto. Ti raccomandiamo inoltre di controllare i problemi noti, verificare la versione della correzione permanente e confermare che hai installato le ultime versioni dei temi e dei plugin.
Problem: The client has an issue with a custom post type created with ACF not being translated on the frontend, even though translation was activated in ACF and the field was translated. Solution: We recommended that the client should translate the 'poltrone' post-type slug into English ('seats') via WPML>>Settings>>Custom Posts Type Translation. It is important to perform a full site backup before making changes. After translating the slug, the client should visit Settings>>Permalinks and resave the settings. Following these steps, it is also advised to clear all types of caches to check if the issue persists. For more detailed instructions, we provided a link to our documentation: Translating page slugs.
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 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 with us.
Problem: The client encountered an issue with strings that are indicated as Italian but are actually in English, coming from the Theme. Solution: We advised the client that plugins and themes typically use English as the default language for strings. If the incorrect strings are not visible on the frontend, they can be ignored. However, to change the source language of a string or string domain, we recommended navigating to WPML >> String Translation. We provided a step-by-step guide on how to change the source language of strings, which can be found in our documentation: https://wpml.org/documentation/getting-started-guide/string-translation/how-to-change-the-source-language-of-strings/
Please note that the solution provided might be irrelevant due to being 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 you still need assistance, please open a new support ticket with us.
Problem: The client was confused about why a term was translated several times across different translation methods in WPML, including the Advanced Translation Editor and ACF. Additionally, there was an issue with the translation of a page slug not matching the translation in the Advanced Translation Editor. Solution: We explained that once a string/text is translated using the WPML Advanced Translation Editor, it is stored in the Translation Memory. If the text is encountered again, it will be automatically translated without consuming additional credits.
We also provided documentation for further reading on how WPML tracks translations:
If the provided solution is outdated or not applicable to your case, we recommend opening a new support ticket. We also highly suggest checking related known issues at WPML 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 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.
