Plugin Author
Chouby
(@chouby)
I reproduced. And unfortunately this is related to a WordPress bug.
I proposed a patch. See #24802. Let’s hope it will be accepted.
Thanks fo you very quick reply.
Please, can you tell me if the bug is present also on simple blog instance (not network)?
Thanks you for you great plugin.
Plugin Author
Chouby
(@chouby)
It does not depend on multisite or not. The problem is coming from the taxonomy management in WordPress.
Nav menus, categories, post tags and languages are taxonomies. When you use the same name accross several taxonomies, by default, only one term is created.
Polylang normally includes a workaround against this. It works well for categories and post tags. And I discovered today that this protection does not work for nav menus because of a bug I reported. This is easy to correct but of course any modification in WordPress needs deep testing, to be sure that it does not break something else.
Waiting for this, one should not create a menu with the same name as a language. I will add a notice with the next version and go on working on this topic to see if I can improve the situation on Polylang side.
Ok, thanks for explanations.
Probably a notice should be sufficient.
Do you think there is a way to rename menu or language without loosing connections again?
Plugin Author
Chouby
(@chouby)
Normally we can change the language slug without loosing the translations… when this is done from the Polaylang languages panel. But here it was an unexpected way of changing it.
For the future, and waiting for the WordPress bug correction, I will prevent the creation of a menu with a language name. Starting from 1.1.3, the menu will be automatically renamed “Italiano-menu”. That’s a bit off-hand, but from far better than loosing translations and better than a notice that at least one person would not read.
