An automated run of parserTests.php showed the following failures:
Running test TODO: Table security: embedded pipes (http://mail.wikipedia.org/pipermail/wikitech-l/2006-April/034637.html)... FAILED!
Running test TODO: Link containing double-single-quotes '' (bug 4598)... FAILED!
Running test TODO: Template with thumb image (with link in description)... FAILED!
Running test TODO: message transform: <noinclude> in transcluded template (bug 4926)... FAILED!
Running test TODO: message transform: <onlyinclude> in transcluded template (bug 4926)... FAILED!
Running test BUG 1887, part 2: A <math> with a thumbnail- math enabled... FAILED!
Running test TODO: HTML bullet list, unclosed tags (bug 5497)... FAILED!
Running test TODO: HTML ordered list, unclosed tags (bug 5497)... FAILED!
Running test TODO: HTML nested bullet list, open tags (bug 5497)... FAILED!
Running test TODO: HTML nested ordered list, open tags (bug 5497)... FAILED!
Running test TODO: Parsing optional HTML elements (Bug 6171)... FAILED!
Running test TODO: Inline HTML vs wiki block nesting... FAILED!
Running test TODO: Mixing markup for italics and bold... FAILED!
Running test TODO: 5 quotes, code coverage +1 line... FAILED!
Running test TODO: HTML Hex character encoding.... FAILED!
Running test TODO: dt/dd/dl test... FAILED!
Passed 421 of 437 tests (96.34%) FAILED!
I've gone ahead and switched in the AntiSpoof extension, based on Neil
Harris's code to check for mixed-script and similar likely-spoofed
usernames.
This has been on for a few weeks doing logging, and I'd meant to go
ahead and switch it in to actively block things but hadn't got to it
between other things.
An example of a similarity conflict as shown in the log:
2006-10-17 06:45:19 testwiki: CONFLICT new account 'Sp1arka'
[v1:5P1ARKA] spoofs 'Splarka'
If some of the similarity checks are too much of a problem we can add an
override or perhaps knock it back down into a partial mode.
-- brion vibber (brion @ pobox.com)
On 10/17/06, Parker Peters <onmywayoutster(a)gmail.com> wrote:
> On 10/16/06, Rory Stolzenberg <rory096(a)gmail.com> wrote:
> >
> > Temporarily, it can be useful, but admins tend to forget to unprotect it;
> > look at my user page for an example. While my userpage isn't a talk page
> > (and it doesn't matter enough to me to get it unprotected), it's an
> > example
> > of something that an admin protected from vandalism then completely forgot
> > about and never unprotected.
> >
>
> I was gone, but this one's piqued my interest, so here's what I have to say
> on the matter:
>
> Our backend code is stupid.
>
> Protection should not be "forever until it is turned off." Instead, like
> blocking any just about anything else, it should have a duration after which
> it automatically expires.
>
> We've got some article pages that have been "Protected" for weeks or longer,
> with no edit and next to no discussions on the talk pages, because either
> some admin is too damn lazy to remove the protection or enjoys keeping it
> protected because they feel they own the article that way.
There's been a feature request for this for some time:
http://bugzilla.wikimedia.org/show_bug.cgi?id=4133
Implementing this would probably require a fairly extensive change to
the database schema, so I don't know how willing the devs would be to
implement it, considering it's only really a feature request and not a
critical problem.
Perhaps what we need is something like Ipblocklist, but to show
protected pages. VoABot keeps WP:PP updated well enough, but a special
page would be a better solution.
--
Stephen Bain
stephen.bain(a)gmail.com
I know there was talk here (or maybe on Bugzilla - I forget) about improving
the edit links, and I guess someone is working on it, because currently they
are screwed on en and mw.org (and presumably all other WM wikis - not
checked).
They are appearing above the heading, i.e. at the bottom of the preceeding
section to the one they apply to... which is _incredibly_ confusing! It
even confused me - a long-time editor...
I'm sure someone is working on this right now, but they may not be aware
that the changes are live.
- Mark Clements (HappyDog)
Are there any kind of concrete plans for specific future versions of
MediaWiki, or is it just a matter of "we've got a bunch of bugs and feature
requests and we'll do the ones we feel like".
The reason I ask is that http://www.mediawiki.org/wiki/MediaWiki_roadmap is
quite prominently linked to from the main page of mediawiki.org, but
contains no useful content. It has dates for versions 1.9 and 1.10, but
under 'planned milestones' they both just say 'no plans yet'.
If there is a grand plan, or even a not-so-grand plan (or, to be honest,
even some small items that are definitely going to make it into the next
release) it would be good to get them on this page. If not, then we should
rework the page to say as much and remove the link from the main page.
- Mark Clements (HappyDog)
Following up from a discussion on unblock-en-l...
How much effort would it be to add an enhancement to treat blocked
user redlink clicks like we currently treat anon user redlink clicks
when anon article creation is disabled?
We're trying to minimize the number of people who are fundamentally
just readers, who click on a redlink and see a block message (mostly
AOL users, but it happens to others). If they click on the "edit" bar
and get it, that's fine, but if the default redlink behavior didn't
show the block message then that would be great.
Thanks.
--
-george william herbert
george.herbert(a)gmail.com
I was hoping to use Spam Regex to prevent users making ANY external
links from MediaWiki
something like this:
#Block external links:
$wgSpamRegex = "/\[*\.*\]$/";
But I can't get it to work...
Suggestions?
PY
--
Yellowikis is to Yellow Pages, as Wikipedia is to The Encyclopedia Britannica
An automated run of parserTests.php showed the following failures:
Running test TODO: Table security: embedded pipes (http://mail.wikipedia.org/pipermail/wikitech-l/2006-April/034637.html)... FAILED!
Running test TODO: Link containing double-single-quotes '' (bug 4598)... FAILED!
Running test TODO: Template with thumb image (with link in description)... FAILED!
Running test TODO: message transform: <noinclude> in transcluded template (bug 4926)... FAILED!
Running test TODO: message transform: <onlyinclude> in transcluded template (bug 4926)... FAILED!
Running test BUG 1887, part 2: A <math> with a thumbnail- math enabled... FAILED!
Running test TODO: HTML bullet list, unclosed tags (bug 5497)... FAILED!
Running test TODO: HTML ordered list, unclosed tags (bug 5497)... FAILED!
Running test TODO: HTML nested bullet list, open tags (bug 5497)... FAILED!
Running test TODO: HTML nested ordered list, open tags (bug 5497)... FAILED!
Running test TODO: Parsing optional HTML elements (Bug 6171)... FAILED!
Running test TODO: Inline HTML vs wiki block nesting... FAILED!
Running test TODO: Mixing markup for italics and bold... FAILED!
Running test TODO: 5 quotes, code coverage +1 line... FAILED!
Running test TODO: HTML Hex character encoding.... FAILED!
Running test TODO: dt/dd/dl test... FAILED!
Passed 421 of 437 tests (96.34%) FAILED!
I'd like to be able to set a limit on the number of words used in articles.
I thought that there was something like this in LocalSettings but I
can't find it.
Anyone got any suggestions?
PY
--
Yellowikis is to Yellow Pages, as Wikipedia is to The Encyclopedia Britannica