Thanks for the reply, and I stand corrected on MW's ability to merge versions. However:
Date: Fri, 5 Mar 2010 00:03:13 +0100 From: Roan Kattouw roan.kattouw@gmail.com Subject: Re: [Wikitech-l] External editor with merge capability?
To decide whether you've "seen" a certain change, MediaWiki uses the time at which you loaded the edit form: any edits made before this time will appear in the edit box, and any made after will be considered for potential conflicts. However, in certain cases (like restoring your browser session when you restart your browser), your browser may reload the edit page but substitute the old content (containing your work in progress) in the edit box. MediaWiki doesn't know about this, so it records the so-called starttimestamp "wrongly".
Right, this was also my understanding of how it worked internally, the question is how to work around this? Eg. the API offers "basetimestamp" and "starttimestamp" fields that can be sent along with the edit submission, but is there any way to send these or otherwise specify the last revision with a direct submit POST to MediaWiki?
Cheers, -j.
2010/3/5 Jani Patokallio jpatokal@iki.fi:
Right, this was also my understanding of how it worked internally, the question is how to work around this? Eg. the API offers "basetimestamp" and "starttimestamp" fields that can be sent along with the edit submission, but is there any way to send these or otherwise specify the last revision with a direct submit POST to MediaWiki?
You /can/ fake the values of wpStarttimestamp and wpBasetimestamp in the edit form submission, but using the API is recommended. For clarity:
starttimestamp: Used to detect whether the page was deleted since you started editing. Should be the time at which you clicked the edit button basetimestamp: Used to detect edit conflicts. Should be *exactly equal* to the timestamp of the most recent revision of the page at the time you started editing
Roan Kattouw (Catrope)
wikitech-l@lists.wikimedia.org