just as a belated response to this archived thread - you can get around the &prop problem (where curl encodes &prop as and HTML character before sending it) by passing the parameters to CURLOPT_POSTFIELDS as an array, rather than as a string. just explode the string on the ampersands, if it's already in string form.
________________________________________ Man is the only animal that blushes. Or needs to. - Mark Twain --- On Thu, 10/23/08, Platonides <[EMAIL PROTECTED]> wrote: > From: Platonides <[EMAIL PROTECTED]> > Subject: Re: [Mediawiki-api] editing and timestamp confusion > To: "MediaWiki API announcements & discussion" > <[email protected]> > Date: Thursday, October 23, 2008, 2:44 PM > Russell Blau wrote: > > "Roan Kattouw" <[EMAIL PROTECTED]> > said: > >> Actually, using a different timestamp than the > last revision's timestamp > >> will fail: the edit conflict check requires that > the timestamp are > >> *exactly the same*, so timestamps of earlier > revisions *or* later > >> revisions *will* *not* *work*. You really need to > get that one > >> timestamp. (I apologize for overusing the * in > this paragraph.) > > > > This confused me. How can there be a "later > revision" than "the last > > revision's timestamp"? Either the revision > is the last one, or it is > > not.... > > > > Russ > > You could be trying to trick mediawiki by passing > timestamps in the > future, or timestamps to newer, now-deleted revisions. > > _______________________________________________ > Mediawiki-api mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/mediawiki-api _______________________________________________ Mediawiki-api mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/mediawiki-api
