Hello
I am Manpreet Kaur, an undergraduate engineering student. I am interested
in contributing to a PyWikiBot project of extending PWB's support to all
sites listed in the InterWikiMap and a feasible wiki engine. XML-RPC is an
interface supported by many wiki-engines and hence I also wish provide
James Forrester wrote:
>On 30 October 2014 09:53, Chad wrote:
>> New hardware is in place and we've got plenty of breathing room to wrap
>>up the migration to the new search engine.
>
>Excellent news!
Indeed! Thanks to all who made this possible. An independent search engine
is an incredibly im
Hi, it has been almost a week since we opened
https://bugzillapreview.wmflabs.org/ for community review.
Thanks to some reviewers with excellent attention to detail, some new bugs
have been found, and some new discussions have have been held. The current
status of the preview is reflected in
https
On Thu, Oct 30, 2014 at 11:53 AM, Jack Phoenix
wrote:
> There's a lot I'd have to say on the subject, but I think the one thing we
> all can agree is this: it should be easy for people to share their code
> with others via Wikimedia's git service(s). We want third parties to share
> and go open,
There's a lot I'd have to say on the subject, but I think the one thing we
all can agree is this: it should be easy for people to share their code
with others via Wikimedia's git service(s). We want third parties to share
and go open, not close down their repositories and pretend that sharing
their
Hi,
I've wasted a great deal of time today trying to figure out what was
causing issues in resource loader, whereby execution of JS seemed to
randomly abort without any errors. It turns out that a harmless call to
jQuery's .data() within RL was the cause. But not because of mediawiki
code... it wa
On 10/30/14 2:11 AM, Petr Bena wrote:
> Hello,
>
> I am receiving lot of these warnings:
>
> WARNING: API query (revisions): The rvtoken parameter has been deprecated.
>
> According to current documentation for mediawiki at
> https://www.mediawiki.org/wiki/API:Rollback which I follow, in order
>
On 30 October 2014 09:53, Chad wrote:
> All,
>
> New hardware is in place and we've got plenty of breathing room to wrap up
> the migration to
>
> the new search engine.
Excellent news!
[Snip]
> If someone could forward this to wikitech-ambassadors for me, I'd be
> grateful.
>
Don
All,
New hardware is in place and we've got plenty of breathing room to wrap up
the migration to
the new search engine. The only wikis not already on it are: frwiki,
zhwiki, dewiki and enwiki.
We're planning to switch frwiki next Wednesday, Nov. 5th.
If all goes well with that, I'd like us to do
Hello everyone,
I would like to announce the first 1.24 release candidate. Release
candidates are intended to provide you with an opportunity to test a
release and let us know of any problems that you encounter that should
be fixed before a final release.
Download links are given at the end of
Indeed, that was it, thanks
On Thu, Oct 30, 2014 at 1:40 PM, Grunny wrote:
> On 30 October 2014 21:42, Petr Bena wrote:
>> Btw, I don't know if it's a bug or not, but
>> http://www.mediawiki.org/w/api.php?action=query&meta=tokens&rawcontinue=1&type=watch|patrol|rollback&format=xml
>> returns no
On 30 October 2014 21:42, Petr Bena wrote:
> Btw, I don't know if it's a bug or not, but
> http://www.mediawiki.org/w/api.php?action=query&meta=tokens&rawcontinue=1&type=watch|patrol|rollback&format=xml
> returns no tokens even when I am logged in. According to
> always-up-to-date api.php I don't
Btw, I don't know if it's a bug or not, but
http://www.mediawiki.org/w/api.php?action=query&meta=tokens&rawcontinue=1&type=watch|patrol|rollback&format=xml
returns no tokens even when I am logged in. According to
always-up-to-date api.php I don't need to provide any more parameters
for this to work
Hi,
I said that I don't know how to do this correctly, so I can't fix the
documentation. So no, I will not fix it, because I can't.
Regarding your suggestion, it might be a good idea, but apparently
even the "always up-to-date" API documentation returned by api.php is
outdated and its example que
Why not use the always up-to-date API documentation returned by api.php itself?
Rollback should be this doc-page:
http://www.mediawiki.org/w/api.php?action=help&modules=rollback
Maybe you can help us fixing the API documentation, so, if you know, how to do
a rollback, you can fix the doc on mw.o
More ranting:
proper deprecated-message should look like this:
"foo is deprecated. Please use bar instead (see
http://awesomedocs.net/how-to-use-bar.htm)"
It would be cool if mw devs who keep deprecating things would consider this.
Thanks
On Thu, Oct 30, 2014 at 10:12 AM, Petr Bena wrote:
> B
Before someone come with something like: if documentation is wrong, fix it
I don't know what the correct way is, because I am following the
documentation which is wrong, so until someone who knows how to do
this right fix it, I won't know that either.
On Thu, Oct 30, 2014 at 10:11 AM, Petr Bena
Hello,
I am receiving lot of these warnings:
WARNING: API query (revisions): The rvtoken parameter has been deprecated.
According to current documentation for mediawiki at
https://www.mediawiki.org/wiki/API:Rollback which I follow, in order
to get a rvtoken I should use this query:
https://en.w
18 matches
Mail list logo
