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 Template infinite loop... 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 412 of 429 tests (96.04%) FAILED!
I'm looking for a CAPTCHA-Extension for MediaWiki 1.71 and found
several hints Extensions etc.
Which Extension would you recomend for MediaWiki 1.71 ?
How is CAPTCHA be done on meta.wikimedia.org (login) ?
THX, HeinzJ
Hello,
I'm designing a wiki where pages follow a standard layout. Certain
templates are used to insert <h1> and simultaneously an floating
information box with some links (that depend on the content of the
<h1>). So, pages include the template then the text corresponding to the
content and everything is very simple.
However the [edit] links are now quite useless (and very confusing to
users) because they will edit the template instead of the page content.
I don't suppose that there is a workaround for this except to hide those
links. I changed the code as follows, and main.css appropriately.
in editSectionLinkForOther in Linker.php:
return "<div class=\"editsection editsectionother\" ...
Maybe you'd be interested to include this in the main trunk to as to
simplify such a setting. Also, the default skin might display such
'other' links somewhat differently.
Best
Alexandre
"Timwi" wrote:
> There is no reason why we couldn't do this. All we need to do is have
> those two images access an actual wiki image, just like the logo in the
> top-left corner is actually [[Image:Wiki.png]] (correct me if I'm
> wrong). Granting access to change those images to sysops only is way
> enough to ensure that any necessary restrictions are met (e.g. the
> MediaWiki one must mention MediaWiki and must not change the MediaWiki
> logo).
>
> Timwi
It'd be changed by the devs, so really no problem. The different
translations should be available at a gallery on mediawiki.org.
Question: should they be loacally uploaded or on commons?
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 Template infinite loop... 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 412 of 429 tests (96.04%) FAILED!
Hi All,
I am wondering how difficult it would be to use wiki with Sybase ASE. Has
anyone attempted this with any amount of success? I'm willing to work on
this with others who may be interested. I've downloaded mediawiki 1.6.8 (due
to PHP4) and just starting to look around.
Thanks,
Mark
I added this to monobook.php for creating additional sidebar-blocks:
http://www.mediawiki.org/wiki/Manual:Navigation_bar#Customizing_monobook.php
+ <div class="portlet" id="p-navn">
+ <h5><?php $this->msg('navigation') ?></h5>
+ <div class="pBody">
+ <?php $this->msgWiki( 'AnotherMenu' ) ?>
+ </div>
+ </div>
Are there any CONs against this?
Imho the solution above is able to use more complicated
sidebar-construction than MediaWiki:Sidebar doas
HeinzJ
Felipe Sanches wrote:
> After all these 42 messages, is there anybody working on this feature at all?
No. Only Nick Jenkins was actually interested in doing anything, in the role
of UI designer, and even he didn't go as far as the original post called
for. Given my failure to convince anyone to work on one of my ideas, I've
been taking a different approach over the past week or so: supporting
existing development efforts on the client side.
There is a lot of pure client-side development going on, based on
modifications to site or user javascript. I'm attempting to improve those
client-side features by adding customised server-side interfaces for them,
essentially turning them into hybrid client/server features. Then, if the
client-side developer will allow me to, I can move the client side component
into the extensions module as well, thereby creating a hybrid extension
which will work on all MediaWiki wikis with minimal installation effort.
The extensions which I am working on are:
* ProofreadPage. This is an extension to support transcription of scanned
images on Wikisource. The client-side developer is ThomasV. It is mostly
complete, and currently enabled on fr.wikisource.org.
* PicturePopups. This is an AJAX-based extension to display image licensing
information in a popup over the image. The client-side developer is zocky.
Work is ongoing.
* JOrbisPlayer. Greg Maxwell is the client-side developer, he has created a
demo on the toolserver at http://tinyurl.com/fsbu7 . We are in the
specification development stage.
These have all come about because the client-side developers have approached
me on IRC, asking some question about server interfaces or performance. In
the future, I may approach the developers of popular client-side features
myself, with a proposition to bring their feature to a wider audience. Lupin
in particular is on my list, although he may not know it yet.
So although we may not be getting dynamic editor lists on edit pages any
time soon, all is not lost in the realm of collaborative development. There
are lots of exciting opportunities.
-- Tim Starling
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 Template infinite loop... 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 412 of 429 tests (96.04%) FAILED!