transcription not accepted after first line

In the transcription modal only manual corrections to the first line corrected are accepted. All other corrections for subsequent lines are NOT stored in the database. I assume this is linked to the previous issue.

added Bug important labels

Need more details, not reproducible naively by just correcting lines in the transcription modal. Something triggered this but what?

yup. I now cant reproduce it either. But it happened to several different people so we need to trace it. @achague watch out for this and notify your transcribers please

We can't reproduce on our side either.

Reproduced it by copying the entire page from an imported transcription into the manual transcription.

@rtissot We tried again to reproduce the bug but we were not able to see it appear. Could you please attach some screenshots and give us clear steps to reproduce? For each failing step, it could be helpful to know exactly what should be the expected behaviour.

On my side, I tried to copy the text in the DiploPanel (generated by an imported transcription) and paste it in the DiploPanel of the manual transcription, then I opened the transcription modal on the first line, edited it, I did the same for the second and third line. Finally, I reloaded the website with F5 and the transcriptions were correctly saved with their correction.

@x-EBardo I'm trying to track it down as we speak, to reproduce:

• copy at least 2 lines in the text panel (the last)
• click one of the 2 lines in the transcription panel and modify it through the modal
• go to the other copied line by any means (arrows or just click on it) and modify it too
  -> you get a 400 error

Apparently l.currentTrans.pk resolves to false in transcriptions.js->updateLineTranscriptionVersion
My best guess is that the manual update of the first line empties it somehow. Not sure what the text panel has to do with it.

If you have any idea don't hesitate as I'd like to go back to finishing the cluster conf :)

edit: Commenting updateContent->updateCurrentTrans fixes it but probably has undesirable side effects(?)

I'm able to reproduce locally by following your instructions.

We'll make a patch today for this issue. Thanks for the STR

I'm unable to reproduce several times the issue, I saw it once. We'll need more details duing the meeting later today

I'm finally able to reproduce the bug with my local documents, it seems that the bug only appears when the line is set for the first time. I'll investigate to find a fix quickly.

mentioned in merge request !64 (merged)

closed with merge request !64 (merged)

mentioned in commit d611cbe1