Hello Bobby,
I made what you said ; and it failed.
I have been wondering what could be the cause ... since you are most certainly American, and so, most likely have no clue about French or German ... well, WP-end points had been created in FR, DE, or EN ...
So, after the first trial (what you wrote) I deleted all of them.
Then, re-translated all of them
Then, flushed all caches
And it still does not work, leading to same result
Ready to share an admin access
Waiting for your feedback
Kind regards
Alina
So that you think about it ...
If I delete all end points ... they are first auto populate in EN.
Then, I change language ... I mean say those end-points are in EN.
Then, I translate them in FR and DE.
And then, they are re-populated in EN ... generating mess and confusion.
As you certainly don't speak any other language but EN and possibly ES, here attached are the false duplicates generated by WPML
regards
To add, your solution yet does not work on the staging site (see attached).
If it has, it's not stable.
As written above, it looks like WPML repopulate a certain mess in WP-endpoints
Indeed, the step by step:
- delete all WP endpoints in WPML strings translation
-> then, they are regenerated with English flag but French text (see image wpml-step-1)
- change language of all former WP ends to FR
- translate all WP endpoints in EN and DE
-> then, all translations are considered as new chains to be translated
Pretty sure it's due to 4.7 version.
For sure, the reason is that endpoints are erroneously generated with FR text and EN flag
I will take a duplicator package of your website and share it with our team to further debug this as yes, it looks like something is happening that is creating these additiional endpoints, I can confirm that this is not expected nor have I seen any other known reports therefore if the workaround provided did not work or is not stable we need to escalate this further.
Hello Bobby,
Sorry for late feedback, I am an artisan, work alone, and had a very busy week.
Re. your feedback, you have all info re. staging site, which you can use for your tests and replicate, correct?
Re. problem itself, I found a way to cope with ... since WPML consider that the first translations of end-points become new strings to translate ... well, you "simply" need to keep the same string for all languages and them, it's stable and works
Concretely, translate eg "edit-address" in "edit-address" for all languages.
Something that could help, 2 oddities with different behaviors:
1. As said, after deletion, wp endpoints are regenerated in FR and declared as EN. Except one: waitlist in EN and declared as EN
2. editer-addresse, which is "edit-address" in FR is the string generated after deletion of all. It has a spelling error: in French, adresse has only 1 d.
The why of those 2 could put you on the track for original cause
Kind regards
Alina
If you are OK with the workaround you are using you could continue using it as keeping them the same would prevent such issues.
However, if you would like us to further investigate the next steps are to migrate a copy of the site onto our cloudways servers for further investigation and escalate this issue.
