https://bugzilla.wikimedia.org/show_bug.cgi?id=52805
--- Comment #7 from Jesús Martínez Novo (Ciencia Al Poder) <[email protected]> --- (In reply to comment #5) > If you read the code for LQT's threadaction you'll see that it deals with > basetimestamp. We know this is happening because otherwise no conflicts would > be detected. As I said, when you save the edit, the server isn't getting that basetimestamp. Yes, I see how it's "dealing" with it: 'basetimestamp' => wfTimestampNow(), That's wrong, since there's no way to know from which "revision" the edit was started. Maybe someone else saved the edit before you, but LQT has no reference to detect it. The workflow should be: 1. A request is made to get an edit form of a message 2. LQT should send the basetimestamp of the current message along with the edit form 3. The user hits save. 4. A request is made with all the current fields plus the basetimestamp received in #2 5. LQT should use it to detect edit conflicts, instead of generating a reference basetimestamp from wfTimestampNow() Editing a message should be like editing any normal page (if I haven't understood it wrong). Every message is like a page. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
