Background of the issue:
We are developing a site and using WPML to translate pages. We encountered an issue where some pages do not automatically translate URLs or page names in the administration area. We tried deleting and re-translating the problematic pages, but it didn't help. We also tried translating the same page into another language, but the translation was still missing.
Symptoms:
Some pages do not automatically translate URLs or page names in the administration area. This issue is not consistent across all pages.
Questions:
Why are some pages not automatically translating URLs or page names in the administration area?
What steps can we take to ensure that all pages are translated correctly?
Unfortunately I don't have a solution for you right a part from manually editing the translations. The issue has been escalated to the developers of our Advanced Translation Editor (ATE). Hopefully they will detect the root cause of the issue. I'll get back to you once I have some feedback.
Just a quick message to let you know that our team found the issue (I think it's related to the an edge case where you have several fields with the name "title". One of our developers created a merge request with a fix. So it should be fixed in the next ATE update. Unfortunately I don't have an ETA right now, but those updates are quite frequent (once or twice a month).
Thanks for reporting this issue, it helps us to improve our product.
thank you. Is it possible to test it on our end before you release new version of the plugin? Does this fix have some relation also with the page slug/url, as we described above?
What you could already try is to rename your "title" ACF fields. To see if it helps prevent the issue. As for the update that the question I can't answer right now as the Advanced Translation Editor (ATE) is actually outside of the WPML plugin, so ATE and WPML updates are not always tighten together.
Regarding the slug, you set the it to be auto-generated from the title. That's the default behavior in WordPress, this means that the slug is generated from the title at the moment you create the translation. So here I see this issue as a side effect of the first issue: If the title didn't get translated, the auto-generated slug won't be neither. Fixing the first issue will avoid this.
For already translated pages, you can manually update the slug by editing the page directly in the WordPress editor.
- Go to Pages and use the language switcher in your top admin bar to switch to English.
- Edit the English translated page in the WordPress editor and edit the slug (the field is right below the title).
- One tip: if you edit the title and translate it, then click on the slug to edit it and simply delete it completely, the WordPress "auto-generated" feature will kick in and generate a new slug for you based on the title. So, it's not ideal but for now it can save you time as you don't have to type it manually.
We've updated to your new version(4.6.12), but unfortunately we don't see this bug fixed there. Is there anything else we need to do for this or was this bug not fixed in this update? So when will it possibly be?
I tried again, I deleted all the mistranslated pages in French and had them translated from Czech to French again, and a lot of pages still don't have the title translated. Re-translating some pages fixed it - the title translated, but a lot of pages did not. So the problem still persists. So you have probably only partially solved the problem or it is somewhere else. Can you please take a look at it? You still have access.
I think that the issue here is that some of your translations were already published and therefore the translation is saved in the translation memory.
1. Could you please confirm that it is working correctly with new translations?
2. Regarding previous translation, unfortunately the solution remains a manual edit (see my answer from July 3rd)
