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.
Problema: Dopo l'installazione di WPML, le pagine del sito sono sparite nonostante l'aumento del limite di memoria in wp-config.php. Soluzione: 1) Svuotare la cache del sito web, inclusa la cache lato server, e verificare se il problema si risolve. 2) Se il problema persiste, effettuare un backup completo del sito e poi: - Andare su WPML -> Supporto -> Pagina di risoluzione dei problemi. - Premere sui seguenti pulsanti: - Cancella la cache in WPML - Sincronizza le tassonomie degli articoli - Rimuovi voci fantasma dalle tabelle di traduzione - Risolvi la collazione degli elementi - Risolvi la collazione delle tabelle WPML - Sincronizza gli ID di lavoro locali con i lavori ATE - Sincronizza i traduttori e i responsabili delle traduzioni con ATE - Assegna lo stato di traduzione ai contenuti duplicati - Risolvi l'assegnazione del tipo di post per le traduzioni - Imposta le informazioni sulla lingua Dopo aver eseguito questi passaggi, verificare nuovamente se il problema è stato risolto. La soluzione potrebbe non essere più attuale o adatta al tuo caso. Se il problema persiste, ti consigliamo di controllare la pagina dei problemi noti, verificare la versione della soluzione permanente e assicurarti di avere installato le ultime versioni di temi e plugin. In caso contrario, ti invitiamo ad aprire un nuovo ticket di supporto nel forum di supporto WPML.
