Sometime between yesterday and today, the edit summary field on
en.wp's edit page lost its "type=text" attribute. It now reads:
<input name="wpSummary" size="60" value="" id="wpSummary" maxlength="200" tabindex="1" />
Lo and behold, type=text is the default, so it doesn't actually
break a standards-compliant browser, but it's kind of an an odd
change. (I noticed because it mildly broke a bot of mine, that
assumed type=text only by accident, and after printing some
extraneous error messages.)
Hi all,
After a few weeks on test.wikipedia.org, the Abuse Filter is rolling
out for wider testing. For the moment, it's active on MediaWiki.org,
but we're interested in deploying it to other small projects
interested in targetting pattern vandalism.
The Abuse Filter extension allows very specific rules to be defined
about the sorts of edits that may be made. It can take actions in
response to edits ranging from simple tagging of an edit with a
special mark indicating it needs extra attention, all the way up to
emergency desysopping. Projects can ask for any subset, or all of
these actions to be enabled on their wiki, and for advanced
permissions to be required to use the higher-level ones.
The extension includes considerable useful tools for testing and
debugging filters, and for evaluating their performance. A study last
year indicated that a particular filter, if applied in August 2007,
would have blocked 60% of all page-move vandalism on English Wikipedia
over the subsequent year, with just five false positives (0.6%).
Primarily we're looking at the performance impact of the extension, so
English Wikipedia (which the extension was written for) can't quite
have it yet (as we're not sure that it will perform adequately under
such high load). If other medium or small projects such as Meta,
Commons, Wiktionary, Wikibooks, Wikisource and similar are interested
in deploying this extension, they're free to develop a rough consensus
and request deployment on Bugzilla.
If, after a few weeks, we find that the extension seems to work fine,
we can hopefully deploy it on English Wikipedia (hooray!).
Thanks!
--
Andrew Garrett
The discussions about the open of rollback and patrol right are in progress
at Chinese Wikipedia (zh.wikipedia.org). Some suggested that we can have two
ways to grant right to the qualified users. One is auto-promote (by system),
and one is by hand (by admin). That's mean two requirements are needed. The
requirement for auto-promotion is higher, and if user met this requirement,
he must be promoted by system. Before that, if users met another
requirement, he can make an application, and admin can consider whether or
not. I would like to know that, is this possible to run out practically?
We're trying to get some more traffic onto the new mobile gateway for
testing -- and figuring out how best to get people to the
mobile-optimized site if they hit a regular Wikipedia link while on
their mobile phone.
For the moment I've slipped in some JavaScript onto English Wikipedia
which (intermittently for now) pops up a big link if it detects you’re
on an iPhone, iPod Touch, or Android-based device.
Pretty screen shots at:
http://leuksman.com/log/2009/02/18/mobile-browser-links/
:D
-- brion
Hi,
I'm working on optimizing MediaWiki for front-end performance and came
across a problem that seems to be an issue even on Wikipedia - images all
get requested from the server for the subsequent requests even though all of
them didn't change - this means that images that are cached in a browser are
re-requested again. The problem is that even though all those requests
return 304s and none of the images are actually transmitted, it still makes
all those requests which delays rendering of the page.
I've wrote a patch and created a bug for this in Bugzilla:
https://bugzilla.wikimedia.org/show_bug.cgi?id=17577
Let me know what you think.
Thank you,
Sergey
--
Sergey Chernyshev
http://www.sergeychernyshev.com/
Greetings,
I have been searching online for the possibility of using the name wikipedia
to name a server but I could not find information about this anywhere.
Basically, we are duplicating the enwiki locally at Concordia and searching
whether we are allowed to use wikipedia.concordia.ca for the server.
Is this allowed?
Is there any policy on the usage of the name?
Thanks in advance.
bilal
>>>>> "FC" == Faue, Caralynn <Caralynn.Faue(a)mts.com> writes:
FC> Hello,
FC> I am so sorry for the intrusion, but I have come across your
FC> comment on bugzilla
FC> (https://bugzilla.wikimedia.org/show_bug.cgi?id=8473) regarding
FC> allowing search engines to crawl specialallpages.php. I am
FC> somewhat of a MediaWiki / php newbie, however our organization
FC> does have a WIMP installation of MediaWiki installed. I have been
FC> maintaining code in specialallpages.php that allowed Microsoft
FC> Search Server 2008 to crawl the wiki. The code is similar to this:
FC> $wgOut->setRobotpolicy( 'index,follow' );
FC> This was working, but recently it appears that my customization of
FC> this file is being ignored (when I view source the
FC> meta tag shows noindex, nofollow again). Do you have any insight into
FC> why this might be happening? I am not sure exactly
FC> when it started, however I did notice it after our upgrade to
FC> MediaWiki version 1.13.3. I have verified that the source
FC> code did not get overwritten during the upgrade.
FC> $wgOut->setRobotpolicy( 'index,follow' ); is still contained in
FC> specialallpages.php.
FC> Again, I am sorry to just email you directly, I have been watching the
FC> bugzilla site for updates, but none have been
FC> posted.
I'll Cc the newsgroup.
I ended up using sitemaps, but I would love to not make sitemaps, if
the aforementioned bug was fixed.
(I never stray outside of LocalSettings.php with my changes.)
FC> Thanks in advance,
FC> Caralynn Faue
FC> Application Developer
FC> MTS Systems Corporation
It appears that since r45973, there is an enhancement to MediaWiki that
allows the software to follow double redirects, and conceivably triple- and
higher-level redirects, up to a configurable limit ($wgMaxRedirects). This
raises a few questions:
1) Should [[Special:DoubleRedirects]] be changed to show only those
redirect chains that exceed $wgMaxRedirects in length, since those are the
only ones that really need fixing under the current software?
2) If not, should there be a new Special: page to list such "excessive"
redirect chains?
3) How can the users (not sysadmins) of a given wiki determine what the
value of $wgMaxRedirects is for their wiki? In particular, what value is
being used currently on enwiki and other WMF projects?
4) Shouldn't this configuration change have been announced to the user
community of each project so that they could consider how it affects their
internal policies on what types of redirects to allow?
Russ
2009/2/19 Michael Snow <wikipedia(a)verizon.net>:
> I'm likely going to put the general issue of biographies on the board's
> next agenda, for what that's worth. Though as I say, there's no simple
> blanket solution, and I don't know if we can promise anything beyond
> more discussion and more awareness of the issues.
What's the schedule on the flagged revisions trial on en:wp?
(cc: to wikitech-l)
- d.
Hi,
I'm running Mediawiki 1.11.2 on Ubuntu 8, and after a recent update,
I'm now getting the error:
Warning: Missing argument 5 for MediaWiki::initialize(), called in
/usr/share/mediawiki/index.php on line 89 and defined in
/var/lib/mediawiki/includes/Wiki.php on line 52
Fatal error: Call to a member function getCheck() on a non-object in
/var/lib/mediawiki/includes/Wiki.php on line 137
Why would an update break Mediawiki's homepage, and how can I fix it?
Interestingly, Google returns lot's of sites with this error, but
they're all Mediawiki sites containing the error, and not anyone
discussing why the error occurs or how to fix it.
Regards,
Chris