Hi, Christian from Lingotek here.
We can reproduce the issue consistently with Polylang 3.1.0 + Lingotek.
It doesn’t matter if the translation is downloaded from Lingotek or created with Polylang.
This doesn’t happen with Polylang 3.0.6 + Lingotek.
We are looking at the diff to check what’s changed for other keys to be removed from post_translations.
The problem is that somehow \PLL_Translated_Object::save_translations has:
// Unlink removed translations.
$old_translations = $this->get_translations( $id );
foreach ( array_diff_assoc( $old_translations, $translations ) as $object_id ) {
$this->delete_translation( $object_id );
}
and that’s triggering the “disassociation”. That code hasn’t changed, so I’m not sure why now is triggered while 3.0.6 didn’t.
We identified the bug on Lingotek and a fix will be released really soon (1.5.1).
Not sure how this bug wasn’t triggered with 3.0.6, as the problem doesn’t look related at all with the changes there.
hi Penyaskito, thank you for your feedback, I’m waiting for the new version of lingotek, for the moment I do it manually because in my case it works only if I do it manually. I can make changes of the page without unlink the translated versions if I don’t use lingotek
We’ll have the new release coming out this week, probably tomorrow. Sorry for the wait.
