Page MenuHomePhabricator

ContentTranslation bug - collective translation
Open, Needs TriagePublic

Description

In Content Translation, if someone started a translation for a page, nobody else can use Content Translation tool to re-translate again that page. Even if the original translation was abandoned and deleted you can't translate again the source page. Error appears when trying to publish the page, after you worked a lot translating the content.

Event Timeline

Thanks for reporting about this, @XXN.
Currently, topics get blocked when a user starts translating them, this is a limitation of the tool and there are plans to avoid such blocks in the future. The ideas are captured in this ticket for tracking and discussion: T86151: Allow different users to translate the same topic independently

You also mentioned that the warning is given at publishing time. that's not how the tool is expected to work. The information about the block should be presented as soon as possible. So this is probably a bug.

Something else related:

if user U1 starts a translation draft of page P1 from wiki A1 to wiki B2,
then,
user U2 starts a translation draft of the same page P1 from wiki A1 to wiki B2,
no one of them publishes his translation,
but then user U1 deletes his draft, after that user U2 can't delete his own draft.

Amire80 subscribed.

Adding this to the quarter to take a deeper look into it—bugs of this kind are reported frequently lately, and we need to understand why is this happening.

Something else related:

if user U1 starts a translation draft of page P1 from wiki A1 to wiki B2,
then,
user U2 starts a translation draft of the same page P1 from wiki A1 to wiki B2,

This should not happen i.e. User 2 should not be able to translate the same page. If it is happening then it is a bug. More details about the article name and language pairs would be great.

no one of them publishes his translation,
but then user U1 deletes his draft, after that user U2 can't delete his own draft.

Sounds like something that should be connected with T146345. If so, it should be a separate ticket. The current title of this ticket is misleading. Thanks.