Problem: You have translated the slug of a custom post type and are using different domains for each language. In English, the domain is numatours.com. After translating the slug 'actividades' to 'tours', both URLs (https://www.yourdomain.com/actividades/ and https://www.yourotherdomain.com/tours/) are functioning, which was unexpected as you anticipated only the translated URL to be active. Solution: It's common for WordPress to try to "guess" the correct links in the target language, which might be happening in your case. If the page at the original slug does not exist and can only be accessed by directly typing the URL, it's unlikely to be discovered by users. However, you can request Google to set it as noindex to ensure it does not get indexed. For managing redirects with different domains, the process is the same as any other redirect. WPML does not handle redirects, so you will need to add them via .htaccess or using a redirect plugin.
If this solution does not apply to your situation, or if it seems outdated, we recommend opening 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. For further assistance, please visit our support forum at WPML Support Forum.
Problema: Il cliente sta cercando di tradurre i menu di navigazione del sito. Quando crea un menu nella seconda lingua, questo non appare nell'elenco dei menu e tentando di modificarlo viene rediretto alla pagina di creazione di un nuovo menu. I menu tradotti vengono visualizzati come duplicati del menu nella lingua di default. Soluzione: Per risolvere il problema, il cliente ha seguito questi passaggi: 1) Disattivato WPML String Translations 2) Acceduto alla pagina admin Appearance > Menus 3) Riattivato WPML String Translations È importante eseguire il passaggio 2) poiché disattivare e riattivare WPML String Translations da solo non è sufficiente.
Se questa soluzione non risolve il problema o sembra non essere più applicabile, ti consigliamo di verificare i problemi noti, controllare la versione della correzione permanente e assicurarti di avere installato le ultime versioni dei temi e dei plugin. Se il problema persiste, ti invitiamo a aprire un nuovo ticket di supporto.
Problem: The client is experiencing an issue where the default language values overwrite the selected values in the second language for ACF Relationship and Post Object fields on an Options page, despite setting these fields to 'different fields across languages'. Solution: We found that the field groups were initially set to 'Same fields across language', which caused the settings to be overwritten as the relationship fields were set to copy. Changing the setting to 'Different fields across language' removed the lock icon and allowed the settings to be saved correctly. Remember, when using 'Different fields across language', the Relationship field is set to copy once, meaning the fields are initially copied from the default language, and only afterwards can they be modified.
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 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 problems persist, please open a new support ticket at WPML support forum.
Problem: You started translating a post using the translation editor but decided to delete the translation job to link another existing post as the translation. Despite attempting to delete the job from the jobs page and manually from the icl_translate_job table in the database, the job keeps reappearing. There are no errors in debug.log, and this issue does not occur on a local copy of the website. Solution: We recommend completing the translation first and then attempting to delete the page. If this solution does not resolve your issue or seems outdated, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket at WPML support forum for further assistance.