An automated run of parserTests.php showed the following failures:
This is MediaWiki version 1.9alpha (r18685).
Reading tests from "/home/brion/src/wiki/phase3/maintenance/parserTests.txt"...
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: message transform: <noinclude> in transcluded template (bug 4926)... FAILED!
Running test TODO: message transform: <onlyinclude> in transcluded template (bug 4926)... FAILED!
Running test Thumbnail image caption with a free URL... FAILED!
Running test BUG 1887: A ISBN with a thumbnail... FAILED!
Running test BUG 1887: A RFC with a thumbnail... FAILED!
Running test BUG 1887: A mailto link with a thumbnail... FAILED!
Running test BUG 1887: A <math> with a thumbnail- we don't render math in the parsertests by default,
so math is not stripped and turns up as escaped <math> tags.... FAILED!
Running test BUG 1887, part 2: A <math> with a thumbnail- math enabled... FAILED!
Running test Image caption containing another image... FAILED!
Running test Bug 3090: External links other than http: in image captions... 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 Fuzz testing: image with bogus manual thumbnail... 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: dt/dd/dl test... FAILED!
Running test TODO: Images with the "|" character in the comment... FAILED!
Running test TODO: Parents of subpages, two levels up, without trailing slash or name.... FAILED!
Running test TODO: Parents of subpages, two levels up, with lots of extra trailing slashes.... FAILED!
Running test TODO: Don't fall for the self-closing div... FAILED!
Running test TODO: Always escape literal '>' in output, not just after '<'... FAILED!
Reading tests from "/home/brion/src/wiki/phase3/extensions/Cite/citeParserTests.txt"...
Reading tests from "/home/brion/src/wiki/phase3/extensions/Poem/poemParserTests.txt"...
Passed 463 of 490 tests (94.49%)... FAILED!
On 28/12/06, Anthony <wikilegal(a)inbox.org> wrote:
> On 12/28/06, Gregory Maxwell <gmaxwell(a)gmail.com> wrote:
> > On 12/28/06, Anthony <wikilegal(a)inbox.org> wrote:
> > > You shouldn't buy another 300 servers in the first place.
> > What a great idea.
> > When will you have your implementation of "distributed mediawiki" completed?
> It's already completed. I just need you to transfer over the domain names.
whuh??? Project page?
Your post actually started me thinking on this. A Freenet (for
encryption and to avoid a [[:en:trusted client]] problem) or
BitTorrent (for convenient distribution with a program lots of people
have) method of distributing Wikipedia. A peer-to-peer network with
WMF as the only body supplying content files. The downsides that
spring to mind are (a) doesn't work through any old web browser (this
is a big one) (b) trusted client problem (how to ensure rogue clients
don't redistribute corrupted content in our name).
- d.
On 29/12/06, Chris McKenna <cmckenna(a)sucs.org> wrote:
> On Fri, 29 Dec 2006, David Gerard wrote:
>> On 29/12/06, Chris McKenna <cmckenna(a)sucs.org> wrote:
>>> On Fri, 29 Dec 2006, David Gerard wrote:
>>>> (Mind you, I already get phone calls from journalists who can't work
>>>> out what the hell is where on the typical image description page. The
>>>> current format *sucks* for reusers, even when they find their image.
>>>> Anyone want to work out an Image: page that looks more like something
>>>> you'd see in a commercial photo archive, or on Flickr?)
>>> What about the current layout do journalists not understand/not like?
>> Finding the author/uploader or even being able to work out which bit
>> of the interface is the username. Working out that clicking on that
>> will take them to the uploader's user page. If the uploader has a
>> userpage on Commons at all. Etc.
> Well the {{information}} template that is the encouraged standard has a
> prominent field for Author. In that all of my images that I upload are
> shown as:
> Author - Chris McKenna (Thryduulf)
Yes, that's useful. Though for images one is not the original creator
of, a reuser may want to contact the original uploader in the hope of
a better-quality image.
(The image in question was a public-domain image scanned at web size
from a book published almost a hundred years ago. So the uploader
would be the person to contact for a better-quality scan.)
It should be easy enough to make "Original uploader:" clearly stated
on the page.
> I am not certain that a redesign of the page is needed,
I think it could really do with some UI review. I was having trouble
over the phone even directing her to the place with the link to the
uploader's user page when we both had the page in front of us on our
computers. To a technophobe, the stuff below the image appears to be
technical gibberish in UI terms.
> but perhaps
> mandatory use of the {{information}} template - possibly with an
> auto-generated link to the userpage of teh uploader if this is possible.
Putting {{information}} templates on all Commons pages without them
would also be good.
> Is it technically possible to include a blank {{information}} template on
> the image description page for new uploads? Or maybe redesign the upload
> page to have several input fields corresponding to the template rather
> than one single free-form box as now? Would this require a hack to
> MediaWiki?
Not sure. cc: to wikitech-l for opinions. (Did the German UI review
cover Image: pages?)
- d.
An automated run of parserTests.php showed the following failures:
This is MediaWiki version 1.9alpha (r18664).
Reading tests from "/home/brion/src/wiki/phase3/maintenance/parserTests.txt"...
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: message transform: <noinclude> in transcluded template (bug 4926)... FAILED!
Running test TODO: message transform: <onlyinclude> in transcluded template (bug 4926)... FAILED!
Running test Thumbnail image caption with a free URL... FAILED!
Running test BUG 1887: A ISBN with a thumbnail... FAILED!
Running test BUG 1887: A RFC with a thumbnail... FAILED!
Running test BUG 1887: A mailto link with a thumbnail... FAILED!
Running test BUG 1887: A <math> with a thumbnail- we don't render math in the parsertests by default,
so math is not stripped and turns up as escaped <math> tags.... FAILED!
Running test BUG 1887, part 2: A <math> with a thumbnail- math enabled... FAILED!
Running test Image caption containing another image... FAILED!
Running test Bug 3090: External links other than http: in image captions... 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 Fuzz testing: image with bogus manual thumbnail... 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: dt/dd/dl test... FAILED!
Running test TODO: Images with the "|" character in the comment... FAILED!
Running test TODO: Parents of subpages, two levels up, without trailing slash or name.... FAILED!
Running test TODO: Parents of subpages, two levels up, with lots of extra trailing slashes.... FAILED!
Running test TODO: Don't fall for the self-closing div... FAILED!
Running test TODO: Always escape literal '>' in output, not just after '<'... FAILED!
Reading tests from "/home/brion/src/wiki/phase3/extensions/Cite/citeParserTests.txt"...
Reading tests from "/home/brion/src/wiki/phase3/extensions/Poem/poemParserTests.txt"...
Passed 463 of 490 tests (94.49%)... FAILED!
>Infoboxes on Wikipedia generally use CSS classes defined in
MediaWiki:Common.css or MediaWiki:Monobook.css. You can >"borrow" these from
Wikipedia itself; visit http://en.wikipedia.org/wiki/MediaWiki:Common.css,
and click "view source",
>for instance(...)
Rob,
Thanks SO MUCH. Your advice helped me to get rid of that problem. I
downloaded the two php-files and edited the Localsettings for the
Parser-problem, and copying the infobox-stuff into the css did the rest.
Thanks again for your quick reply, I really appreciate this, and I hope I
wasn´t being too much of a nuisance with such a "noob"-question =)
Have a great day!
Dan
Hey everyone, this is my first message sent to the list.
I have a problem with my wiki-page. I just installed it, PHP and MySQL are
appropiate versions, and so far, everything works smoothly.
However, I do have a problem with infoboxes.
I did create the correct Templates, but on the pages I use infoboxes on,
they´re messed up. Instead of actual tables / infoboxes as seen on
Wikipedia, the data which is supposed to go into the box is printed without
a box around it, and I get a lot of "{{#if:"
Is it possible that this has to do with the class="infobox"-tag? I lack a
lot of experience here, and from what I gathered from tutorials at
mediawiki... is it possible I have to add tables to the MySQL database for
the class="infobox" to work?
I hope this makes sense... I could post the URL of one of the pages in my
Wiki that has such a messed-up infobox, if that´ll help.
Any help would be greatly appreciated!
Dan
------
Most people get a fair amount of fun out of their lives, but on balance life
is suffering, and only the very young or very foolish imagine otherwise.
George Orwell
I'm working with a MediaWiki instance that uses lots of custom extensions,
some of which affect the skin. What is the best way to get a hold of the
template that will be rendered so that I can set() or setRef() things that
my custom skin will use to display?
The obvious solution to me is to insert a hook at the beginning of the
execute function that hands in &$this. I was just wondering if anybody had
a more elegant solution.
Thanks for any help,
Jacob Pappe
simetrical(a)svn.wikimedia.org schrieb:
> Revision: 18598
> Author: simetrical
> Date: 2006-12-26 15:53:34 -0800 (Tue, 26 Dec 2006)
>
> Log Message:
> -----------
> (bug 7169) Use Ajax to watch/unwatch articles. Patch by Dan Li with some modification by me.
Should/Could/Will we activate this feature at WMF sites?
Raymond.
Hoi,
In the past I have urged for a better support for the translators who
work on the localisation of MediaWiki. I expressed that in BetaWiki we
have an environment where it is much easier for translators to work. It
does not require expert knowledge about thinks like Subversion and
Bugzilla. One added benefit is that many people can work on the
localisation of MediaWiki for the same language making it very much more
a Wiki approach.
I have asked Nikerabbit, who has been hosting the BetaWiki wiki, if it
were possible to make changes to the MediaWiki software available in an
extension. He has done so, and Brion permitting it can be implemented
elsewhere.
The reason for the extended list of recipients of this mail is, that in
my opinion the best place to concentrate the "SpecialTranslate"
extension is the Incubator. The reason is that when a project is being
prepared for a full project status, the localisation is very much part
of this preparation. With the localisation being part of the incubation,
the work done will be preserved when it moves from incubation to
production. Also it provides instant gratification while it is still in
the incubator stage.
For the other projects, it is as good a place as any. Having it in
Incubator concentrates the localisation effort and for the benefits this
provides I would propose to do all the localisation using the
SpecialTranslate in Incubator.
Finally I want to thank Nikerabbit both for hosting BetaWiki and for
modifying the software so that we can have it as part of a WMF project.
Thanks,
GerardM
An automated run of parserTests.php showed the following failures:
This is MediaWiki version 1.9alpha (r18627).
Reading tests from "/home/brion/src/wiki/phase3/maintenance/parserTests.txt"...
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: message transform: <noinclude> in transcluded template (bug 4926)... FAILED!
Running test TODO: message transform: <onlyinclude> in transcluded template (bug 4926)... FAILED!
Running test Thumbnail image caption with a free URL... FAILED!
Running test BUG 1887: A ISBN with a thumbnail... FAILED!
Running test BUG 1887: A RFC with a thumbnail... FAILED!
Running test BUG 1887: A mailto link with a thumbnail... FAILED!
Running test BUG 1887: A <math> with a thumbnail- we don't render math in the parsertests by default,
so math is not stripped and turns up as escaped <math> tags.... FAILED!
Running test BUG 1887, part 2: A <math> with a thumbnail- math enabled... FAILED!
Running test Image caption containing another image... FAILED!
Running test Bug 3090: External links other than http: in image captions... 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 Fuzz testing: image with bogus manual thumbnail... 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: dt/dd/dl test... FAILED!
Running test TODO: Images with the "|" character in the comment... FAILED!
Running test TODO: Parents of subpages, two levels up, without trailing slash or name.... FAILED!
Running test TODO: Parents of subpages, two levels up, with lots of extra trailing slashes.... FAILED!
Running test TODO: Don't fall for the self-closing div... FAILED!
Running test TODO: Always escape literal '>' in output, not just after '<'... FAILED!
Reading tests from "/home/brion/src/wiki/phase3/extensions/Cite/citeParserTests.txt"...
Reading tests from "/home/brion/src/wiki/phase3/extensions/Poem/poemParserTests.txt"...
Passed 463 of 490 tests (94.49%)... FAILED!