On Mon, 21 Mar 2005 15:07:50 +0000, Jim Higson <jh(a)333.org> wrote: Are you loading the edit page first and taking the wpEditToken? You need it. (It's used for various things, including detection of edit conflicts.)

On Mon, 21 Mar 2005 15:07:50 +0000, Jim Higson <jh(a)333.org> wrote: Are you loading the edit page first and taking the wpEditToken? You need it. (It's used for various things, including detection of edit conflicts.)

I hacked together something similiar. A lot of people new to wiki's stuggle with just creating a new article. It really isn't obvious. So I added a "new article" entry to the toolbox menu. When you press "preview" it will bounce you back to the wiki with: * "{{stub}}", some dummy headline/text and the category already included into the input box, * the preview already above it The user can then edit the new article and finally submit it.

Jim Higson wrote: Having thought it some more, I'm pretty sure the only way this can be solved is to add recognition for &action=getedittoken to mediawiki. This would return a tiny http response with just the token as text/plain. When the server gets the token back, it would send back an "ok" or "collision"- this is editing equivalent of action=raw. This would be useful for anyone who is trying to write a thick interface to mediawiki, or any other kind of alternate edit tool. Does this sound like an acceptable addition?

Jim _______________________________________________ Wikitech-l mailing list Wikitech-l(a)wikimedia.org http://mail.wikipedia.org/mailman/listinfo/wikitech-l

P.s.: not that I wouldn't mind something like a general robot interface, in fact, I voulenteer to (help) write one (if thats something the people with CVS access would be willing to accept that is).

P.s.: not that I wouldn't mind something like a general robot interface, in fact, I voulenteer to (help) write one (if thats something the people with CVS access would be willing to accept that is).

Rather than having some quick hack made just for you it would probably be better to consider well how to make a standard interface for something like this, something like action=robot which would return something in an easy-to-parse format, is there a bug open for this already where something like this could be brainstormed?

In the meantime, as I understand it what you need *now* is to just implement this on your own wiki, would it not be an option to just modify the code you use to not require the token?

A robot in this context is widely defined as any program that parses server responses and acts based on those responses, this would include your script As I said I'm thinking of a *general* interface for robots, not just something to get one single attribute on edit pages, although getting the token would be included it would only be a small part of it. For example, I wrote a robot to upload files two days ago, what has to be done to upload a file to wikipedia is: 1. Send a POST request with the following: (so far so good) wpUpload => 'Upload file', # actually it seems like this only has to be sent, not with these specific contents, the code that parses it is: } else if ( 'submit' == $this->mAction || $this->mUpload ) { where mUpload is this string. wpUploadFile => [ $file ], wpUploadDescription => encode($encoding, $description), wpUploadAffirm => 1, 2. Process whatever SpecialUpload spits out which can be * Error: ** The image page is protected, wfMsg( 'protectedpage' ) ** The filetype is not accepted, wfMsg( 'badfiletype' ) ** The name is not accepted, wfMsg( 'illegalfilename' ) * Warning: ** The filesize (too big) ** The name of the file (s/ /_/) ** The file is empty ** The file already exists * [.. probably something missing here] in the case of an error you'll find <h4 class='error'> on the page, and <ul class='warning'> if you'll get a warning, however nothing tells you *what kind of warning* so you'll have to resort to actually looking up the warnings in question in Language.php (this is assuming you're using english and not one of the ~80 other languages) to tell what kind of warning you just recived, this of course ignores all the excess html you just recived which you have no use for at all. So, what I'd like for Special:Upload is to be able to submit a POST request to http://commons.wikimedia.org/wiki/Special:Upload?action=robot and have it return something like: largefile,fileexists It could even return all possible strings as boolean values: largefile=0 fileexists=1 emptyfile=1 [...] or, in the case of ?action=robot on an article: token=1231asdfasdt.... The the format is something which can be agreed on, but the actualy point is that there's alot more that needs a robot interface than just your 32 character edit token.

On Mon, 21 Mar 2005 21:23:28 +0000, Jim Higson &lt;jh(a)333.org&gt; wrote: Maybe I'm missing something (wouldn't be the first time) but couldn't you just parse the page for the edittoken? It's pretty easy, for example this Perl code which takes the scalar $editpage containing page retrevied with action=edit would return the token as a variable: (my $wpEditToken) = $editpage =~ m#(?<=<input).*([\w\d]{32}).*(?=wpEditToken)#g;

Well, it may be because it doesnt work (for me :) I can do some things at your site, but of the buttons are nonfunctional, or I get wierd renderings etc. Firefox 1.01 (no privoxy this time) on linux. I DO have some problems with the new kernel, so maybe it is just me :)

I don't know. What is Google complete? (google so far works, AFAIK)

Ah, ok. I *thought* I already did shift+click, but apparently not. The page looks _much_ more complete now. Yeah, the life preview works now - very slick! Sorry for the noise! The only thing that is a bit of a problem is the "pause" that you experience when you type - e.g. when it renders the preview (I like how it does this only when I stop typing :) it pauses shortly or freezes. There is probably not much you can do, but these pauses interrupt my typing too much - so I think I would disable the life preview - which is a shame because this is real cool.

Actually, where is the token on the edit page? This sounds like a silly question, but I've just saved the HTML of an edit page and greped for 'token' without any hits! According to the DOM inspector form#editform fields are: "wpTextbox1" "wpSummary" "wpSave" "wpSection" "wpEdittime" Is the edit time used as the token?

Thanks for the help, I'm using 1.4beta6. There is definitely not any "wpEditToken" in the HTML. Maybe this is a known issue with beta6? When I get time I'll upgrade to 1.4rc1 and see if it persists.

The token isn't there unless you're logged in, it seems.

Actually, where is the token on the edit page? This sounds like a silly question, but I've just saved the HTML of an edit page and greped for 'token' without any hits! According to the DOM inspector form#editform fields are: "wpTextbox1" "wpSummary" "wpSave" "wpSection" "wpEdittime" Is the edit time used as the token?

Actually, where is the token on the edit page? This sounds like a silly question, but I've just saved the HTML of an edit page and greped for 'token' without any hits!