I need some help - I've implemented the API using CodeIgniter for a
clients site and everything works on the site except for the wiki pages,
which are sluggish.
Here is my controller which lists the function calls being made and in
And here is my model where the actual API calls are made:
The api.php file exists on the same server that is making the calls, so
it should be instant but the pages are so very slow, and only in the
instance of using the MW API.
Any help or insight anybody could give would be MUCH appreciated.
-----BEGIN PGP SIGNED MESSAGE-----
As you may know, the current MediaWiki API was based on an earlier
interface, the BotQuery extension accessed via query.php.
During development of the new API, the old query.php was left in place
on Wikimedia's sites to provide backwards-compatibility for tools and
user scripts using it.
However it's a bit of a burden to keep it around -- being nearly
unmaintained it suffers from "bitrot":
* Queries sometimes break due to backend changes
* Security problems are sometimes discovered and must be patched
We've been reluctant to just turn it off since some user scripts still
use it (Lupin's Popups are rumored to be the most popular such), but I'd
like to go ahead and plan to kill it.
I'm currently scheduling the Death of query.php for Monday, August 25 --
a little less than 4 weeks from today.
This gives interested parties a chance to either migrate their scripts
to the current API ahead of time, or to start work on an adaptor to
replace query.php -- transforming queries to send them to the new API
and transforming the results back to a format compatible with the old one.
- -- brion vibber (brion @ wikimedia.org)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
I am currently developing a graphical browser for exploring and searching Wikipedia (or any MediaWiki based wiki for that matter). Now I am wondering if it is somehow possible to get the parsed content of an article without edit links at section headings (or whereever they might show up).
I have searched the API documentation and found nothing so far.
I am trying to update the contents of a page by using a cron job.
I am able to do it by writing a query whcih will update the "old_text" field
from the table "text" with the contents of a text file.
But even after reloading the page, the contents do not get updated.
I was told by one of the members that this was not the right way to do it. I
should try using the API which is available.
I tried to use the simple calls like login and action=query.
They seem to work fine.
But when i tried to use action=edit, I get the following error,
value for parameter 'action'";}}"
I am using Mediawiki 1.11.2 with PHP 5.1.6..
I have the following 2 lines in my LocalSettings.php,
$wgEnableAPI = true;
$wgEnableWriteAPI = true;
Is it that this action is not allowed on this version of mediawiki.
If so is there any other way around??
your help will be really appreciated..
Hi guys! I am trying to use project hawpedia using the mediawiki API. In this way, I can get a page with all images from wikipedia. When I am trying to change the API which I want to use from wikipedia API to a mediawiki API, I cannot see the images. I don't Know if the links to the images are bad, if there is a problem in API mediawiki ... It would be very grateful if someone could tell me something about it.
La vida de los famosos al desnudo en MSN Entretenimiento
As of r37270 , the prop=links, prop=templatelinks, prop=langlinks, prop=extlinks, prop=categories and prop=images modules have limit and continue parameters, just like the list= modules do. This means they no longer list all links/templates/whatever on a page (which can be bad for
the database), so you'll have to use the old query-continue song to get them all. Note that this doesn't hurt backwards compatibility, as pre-r37270 versions of MediaWiki will just give you all results at once,
without a <query-continue>. If you really must know in advance whether these prop= modules are limited, use action=paraminfo:
If the limits aren't in effect, the limit and continue parameters won't be listed (if you get an error about paraminfo being an invalid action, the limits are also not in effect, of course, since the introduction of these limits predates the introduction of action=paraminfo by a long time).
Roan Kattouw (Catrope)
> Thanks for the link Siebrand. It looks like 1.13 will have significant
> improvements to the API. I noticed an entry for deleting images but
> didn't see any entries relating to image upload. Are there plans to
> add image upload soon or is that a little lower on the list?
You could always use a script which uses the api but also has support for
uploading such as mine (low level api access for perl)
If you wanted to do it in another language, just look at the very simple
upload function noting that you need to be logged in on wikipedia to
upload (which can be done with the api).
I'm not a MediaWiki user myself but had a request to support
publishing of content from our documentation software to MediaWiki. I
found the API docs and I downloaded version 1.12 today and have been
experimenting with the API.
I noticed that the API does not yet support editing or creating pages
or uploading of images in version 1.12. I would like to support
publishing content to MediaWiki so I'm interested in what the roadmap
is for the API. I read a post in the archives about edit/create being
worked on, but didn't see any news about image upload. Any information
the developers can share about this?
Blue Mango Learning Systems
www.bluemangolearning.com - www.screensteps.com