WikiBlame would be a *fantastically* useful tool to put into
MediaWiki, if it didn't cause too much load.
- d.
---------- Forwarded message ----------
From: Florian Straub <flominator(a)gmx.net>
Date: 05-Feb-2007 20:16
Subject: [Commons-l] One new and one old tool
To: commons-l(a)lists.wikimedia.org
Hi there,
I just wanted to share two of tools with you:
* Flinfo fetches a complete picture description from Flickr by a given
picture ID like 151898652:
http://wikipedia.ramselehof.de/flinfo.php
* WikiBlame searches different versions of an article for one specific
string:
http://wikipedia.ramselehof.de/wikiblame.php
I just wanted to hear your opinions and to tell you, that I'm always open
for suggestions and translations of WikiBlame :))
Best regards,
Flo
PS: I know that fetching the license from flickr as well would be perfect
.... I'm working on it ....
_______________________________________________
Commons-l mailing list
Commons-l(a)lists.wikimedia.org
http://lists.wikimedia.org/mailman/listinfo/commons-l
An automated run of parserTests.php showed the following failures:
This is MediaWiki version 1.10alpha (r19802).
Reading tests from "maintenance/parserTests.txt"...
Reading tests from "extensions/Cite/citeParserTests.txt"...
Reading tests from "extensions/Poem/poemParserTests.txt"...
4 new PASSING test(s) :)
* Interlanguage link [Has never failed]
* Double interlanguage link [Has never failed]
* Interlanguage link, with prefix links [Has never failed]
* Double interlanguage link, with prefix links (bug 8897) [Has never failed]
3 previously passing test(s) now FAILING! :(
* Blank ref followed by ref with content [Introduced between 05-Feb-2007 08:15:29, 1.10alpha (r19781) and 06-Feb-2007 08:15:27, 1.10alpha (r19802)]
* Regression: non-blank ref "0" followed by ref with content [Introduced between 05-Feb-2007 08:15:29, 1.10alpha (r19781) and 06-Feb-2007 08:15:27, 1.10alpha (r19802)]
* Regression sanity check: non-blank ref "1" followed by ref with content [Introduced between 05-Feb-2007 08:15:29, 1.10alpha (r19781) and 06-Feb-2007 08:15:27, 1.10alpha (r19802)]
18 still FAILING test(s) :(
* URL-encoding in URL functions (single parameter) [Has never passed]
* URL-encoding in URL functions (multiple parameters) [Has never passed]
* TODO: Table security: embedded pipes (http://mail.wikipedia.org/pipermail/wikitech-l/2006-April/034637.html) [Has never passed]
* TODO: Link containing double-single-quotes '' (bug 4598) [Has never passed]
* TODO: message transform: <noinclude> in transcluded template (bug 4926) [Has never passed]
* TODO: message transform: <onlyinclude> in transcluded template (bug 4926) [Has never passed]
* BUG 1887, part 2: A <math> with a thumbnail- math enabled [Has never passed]
* TODO: HTML bullet list, unclosed tags (bug 5497) [Has never passed]
* TODO: HTML ordered list, unclosed tags (bug 5497) [Has never passed]
* TODO: HTML nested bullet list, open tags (bug 5497) [Has never passed]
* TODO: HTML nested ordered list, open tags (bug 5497) [Has never passed]
* TODO: Inline HTML vs wiki block nesting [Has never passed]
* TODO: Mixing markup for italics and bold [Has never passed]
* TODO: 5 quotes, code coverage +1 line [Has never passed]
* TODO: dt/dd/dl test [Has never passed]
* TODO: Images with the "|" character in the comment [Has never passed]
* TODO: Parents of subpages, two levels up, without trailing slash or name. [Has never passed]
* TODO: Parents of subpages, two levels up, with lots of extra trailing slashes. [Has never passed]
Passed 490 of 511 tests (95.89%)... 21 tests failed!
Note: The following topic is not about namespace names and not about names of
special pages.
Vanilla Mediawiki UI strings contain hardcoded localised link targets. For
example have a look at MediaWiki:Blockedtext (if you want to get all (?)
affected messages grep for {{ns:project}} in the sources). Well again in
monolingual wikis no problem. These linked pages are supposed to exist but
now consider a multilingual wiki...
For example "Project:Administrateur" is linked in MediaWiki:Blockedtext/fr
from vanilla Mediawiki. Imagine using someone French in a wiki with a
non-french default language which is commonly the case in multilingual wikis
such as Wikimedia Commons (note: French is just an example this holds for
every of the zillions of languages supported by Mediawiki). So UI messages
were created with monolingual wikis in mind and never considering simultanous
usage of different languages.
So in vanilla Mediawiki please do not hardcode any wiki page in message
strings.
Well how to localise embedded link targets in the future?
Use a mechanism that points to mediawiki namespace pages that define these
link targets (like the mediawiki namespace pages defined by
MediaWiki:Sidebar). A possible syntax could be done with
{{subst:Mediawiki:PAGENAME}} templates (however this syntax has some problems
as this would need to expand to a given sub page and would need to check if
that sub page exists and fall back to default if not). Another possible
syntax could be the use of named variables such as $MediaWiki:PAGENAME in
interface strings.
Arnomane
On Swedish Wiktionarys common.js,
http://sv.wiktionary.org/wiki/MediaWiki:Common.js , is a script that
takes the visitors IP-addresses and transforms it into a non-revertable
number, and then sends it to an external private server that belongs to
one if the administrators on Wiktionary. The script is used for
statistics on visited articles.
To me it seems like this kind of script is a violation of the privacy
policy, since it is possible to get the IP-numbers of all visitors, even
though it is not done in this case. I should also mention that a
discussion was held before this script was activated and that no one
objected to it.
Are these kind of scripts allowed?
--
http://sv.wikipedia.org/wiki/User:StefanB
Hi,
I'm currently working on deploying a mediawiki installation
(IIS/W2K3/MySQL5, if it matters) for the company I work for. I've got
everything pretty much done, and people are using the wiki already with
positive reviews. The problem I'm having at the moment is with file storage.
We don't want to upload all the files, as some files need to change
regularly and be stored on a network drive.
I've gotten far enough with this using meta and mediawiki.org, and have
enabled file:// links and a bunch of other stuff to make this posisble, even
changing the browsers so file:// links are supported from the site. The only
problem I've got left is what to do when there's a space in the file or
directory name being linked to.
For example, if a file is stored in p:\docs\some user documentation.doc, I
can't link to it in the wiki without setting $wgRawHtml and using the a
href=... tag directly inside html tags. Not a very secure option, and also
not very user-friendly. Substituting spaces for %20 doesn't work (IE renders
the %20 directly for file:// links, it seems), and using [blah] doesn't
work, becuase the first space gets regarded as the split between the url and
the title of the link to be displayed. And an a href tag just gets ignored,
despite my efforts to try and add it to the attribute whitelist.
I've been messing around for options for a few days now, and I've broken and
unbroken everything a few times, by screwing with stuff like Sanitize.php,
Linker.php, Parser.php, and so on. But despite being a long-term PHP
developer, I can't figure this code out despite my best efforts.
So I'd like to ask the community if they have any suggestions on how I can
achieve this? None of the code changes I made seemed to have any effect, so
I'm at a loss as to what to do next.
Thanks everyone for your time and any assistance you can offer.
Cheers,
Michael.
Anthere wrote:
> Hello Mike,
>
> Apologies, but it was unclear to me whether there is a wiki page set up
> for the 2007 hacking days.
> If there is no such page, can you set up one so that it is easier to
> follow plans and discuss programmes ?
>
> One feedback I had from hacking days 2006 was that it was necessary to
> have more cool time in small groups, and less "academic-type"
> presentations in front of 20 people. In short, they need not only a room
> with some presentations going on, but also a nice and cosy place to sit,
> with drinks etc...
Indeed there was a strong feeling that the hacking days were
overproduced last year, with too many outsiders, too heavy scheduling,
too many talks.
The hacking days are meant to be informal and, hopefully, productive. :)
Some really nice points did get made in the middle of it, but I and
others found the overall experience rather frustrating. In contrast, in
2005 we really weren't organized enough, and while there was good
socializing which helped build team spirit we didn't come out with much
directly productive.
My recommendation: don't invite too many people, don't have lots of
talks. Talks would be more appropriate for a tech track during Wikimania
proper.
A few small workshop-type sessions to let people strategize, socialize,
roadmap, experiment, and accept tasks to work on for the coming months
would be a lot nicer, and would better justify having a distinct
"hacking days" period before/after the main conference.
-- brion vibber (brion @ pobox.com)
An automated run of parserTests.php showed the following failures:
This is MediaWiki version 1.10alpha (r19781).
Reading tests from "maintenance/parserTests.txt"...
Reading tests from "extensions/Cite/citeParserTests.txt"...
Reading tests from "extensions/Poem/poemParserTests.txt"...
1 previously failing test(s) now PASSING! :)
* Gallery
18 still FAILING test(s) :(
* URL-encoding in URL functions (single parameter)
* URL-encoding in URL functions (multiple parameters)
* TODO: Table security: embedded pipes (http://mail.wikipedia.org/pipermail/wikitech-l/2006-April/034637.html)
* TODO: Link containing double-single-quotes '' (bug 4598)
* TODO: message transform: <noinclude> in transcluded template (bug 4926)
* TODO: message transform: <onlyinclude> in transcluded template (bug 4926)
* BUG 1887, part 2: A <math> with a thumbnail- math enabled
* TODO: HTML bullet list, unclosed tags (bug 5497)
* TODO: HTML ordered list, unclosed tags (bug 5497)
* TODO: HTML nested bullet list, open tags (bug 5497)
* TODO: HTML nested ordered list, open tags (bug 5497)
* TODO: Inline HTML vs wiki block nesting
* TODO: Mixing markup for italics and bold
* TODO: 5 quotes, code coverage +1 line
* TODO: dt/dd/dl test
* TODO: Images with the "|" character in the comment
* TODO: Parents of subpages, two levels up, without trailing slash or name.
* TODO: Parents of subpages, two levels up, with lots of extra trailing slashes.
Passed 489 of 507 tests (96.45%)... 18 tests failed!
Marking people's bugs as INVALID is great, but do add a word why.
Which bug? I mean in general. Customer relations principles still
apply, paid staff or volunteer.