Exception

Problema:
Se stai riscontrando problemi con la visualizzazione delle traduzioni per le metabox di Jet Engine caricate tramite Traduzione Stringhe, come nel caso del sito venerecosmeticinaturali.com.
Soluzione:
Per risolvere il problema, segui questi passaggi:
1. Vai in WPML → Impostazioni → Traduzione → Campi personalizzati, e controlla la sezione Mostra campi di sistema.
2. Assicurati che tutti i campi siano impostati correttamente come traducibili quando necessario, applicando questa verifica solo per il campo _prodotto.
3. Elimina la traduzione inglese se risulta duplicata, e rifai la traduzione utilizzando l’Editor di traduzione di WPML.
Questo dovrebbe garantire che il campo sia correttamente tradotto e visibile.

Se la soluzione proposta non risolve il problema o se sembra non essere più attuale, ti consigliamo di verificare le questioni note, controllare la versione del fix permanente e confermare di avere installato le ultime versioni dei temi e dei plugin. In caso di ulteriori difficoltà, non esitare a aprire un nuovo ticket di supporto.

Problème :
Le slug /category/ ne se traduit pas dans les URLs, par exemple, il devrait apparaître comme "categoria" en espagnol mais reste en anglais.
Solution :
Nous avons ajouté et traduit le préfixe /blog/categoria/ dans les paramètres des permaliens de votre site. Vous pouvez vérifier ces modifications ici : Paramètres des permaliens et ici pour les traductions : Paramètres de traduction. Les URL des articles individuels devraient également fonctionner correctement sans le préfixe, conformément aux réglages des permaliens.

Si cette solution ne résout pas votre problème ou semble dépassée, nous vous recommandons de vérifier les problèmes connus, de vérifier la version du correctif permanent et de confirmer que vous avez installé les dernières versions des thèmes et plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support sur notre forum de support.

Problem:
The client reported that some translated pages are not displaying updated content and are causing CSS issues.
Solution:
1. We asked the client to confirm which pages and languages are affected and to provide recent examples or URLs.
2. We inquired about any recent changes to the original content, the steps followed in the translation workflow, and whether the site cache or CDN has been cleared.
3. We recommended resaving or retranslating the affected pages and checking for CSS differences between the original and translated pages.
4. We emphasized avoiding generic troubleshooting and focusing on a personalized, step-by-step analysis with clear requests for additional details.

If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we 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 further assistance is needed, please open a new support ticket.

Problem:
The client is experiencing 404 errors on some translated pages, even after resetting permalinks.
Solution:
If you're encountering 404 errors on your translated pages, we recommend the following steps:
1. Ensure that the WooCommerce Multilingual & Multicurrency (WCML) plugin is active.
2. Check your WPML and WooCommerce settings for permalink and slug translations.
3. Review and correct the translated product slugs in WCML.
4. Reset your permalinks multiple times if necessary.

If these steps do not resolve the issue, it might be due to a configuration that is either outdated or not applicable to your specific 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 problem persists, please open a new support ticket at WPML support forum for further assistance.