An automated run of parserTests.php showed the following failures:
This is MediaWiki version 1.10alpha (r19675).
Reading tests from "maintenance/parserTests.txt"...
Reading tests from "extensions/Cite/citeParserTests.txt"...
Reading tests from "extensions/Poem/poemParserTests.txt"...
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!
Forwarded for Piotrus:
Help needed with posting to wikitech-l
I have a serious case of gremlins - tried several ways of posting to
that list for a week and nothing works. Sigh. I see you are one of the
contributors to that mailing list: could I ask you to repost my
letter? It can be copy&pasted easily from
User:Piotrus/Sandbox#letter.-- Piotr Konieczny aka Prokonsul Piotrus |
talk 18:29, 26 January 2007 (UTC)
Hello guys,
The General User Survey project (survey of Wikipedia users, see
http://meta.wikimedia.org/wiki/General_User_Survey) is in dire need of
somebody who would help us with the coding part - the questions for
the survey have been mostly ready for months, but we cannot implement
the survey with our (lack of) technical skills.
It was suggested (at
http://en.wikipedia.org/wiki/User_talk:Jimbo_Wales#Researching_Wikipedia)
that our close-to-2-years (!) delay in getting General User Survey
project up and running is due to researchers discussing the issue
among themselves on a forum nobody else reads (i.e. Wiki-research-l) -
so I am bringing the issue here.
Finishing the GUS project would give us not only a better theoretical
understanding of ourselves (demographics, motivations, etc.) but also
generate reliable practical information on how Wikimedia software and
procedures are valued by the users.
Thank you for your help,
PS. I've tried sending this message to the list few days ago but I am
pretty sure it got eaten by some net bug along the way, so I am trying
it again. I apologize if it anybody receives it the second time.
PS2. Just recently another interesting research project did cross a
milestone: see http://en.wikipedia.org/wiki/Wikipedia:WikiXRay
-- Piotr Konieczny aka Prokonsul Piotrus
For a MediaWiki modification I'm working on I added a hook to the
SkinTemplate.php file and specifically the outputPage function. As the
name implies I inserted it before the execute() function is called. The
code now looks like this:
$tpl->set( 'sidebar', $this->buildSidebar() );
$tpl->set( 'nav_urls', $this->buildNavUrls() );
// Hook that allows last minute additions to the
// template, before it is executed.
wfRunHooks( 'BeforeTemplateExecution', array( &$tpl ) );
// execute template
wfProfileIn( "$fname-execute" );
$res = $tpl->execute();
wfProfileOut( "$fname-execute" );
This allows me to add a function to the hook in LocalSettings.php the
normal way:
$wgHooks['BeforeTemplateExecution'][] = 'fnExtendTemplate';
The function looks like this:
function fnExtendTemplate( &$tpl ) {
$tpl->set( 'mainmenu', buildMainMenu() );
return true;
}
And the buildMainMenu function, which is also added to the
LocalSettings.php file:
function buildMainMenu() {
return "Hello World!";
}
With these functions I can simply add the following line to the Skin file:
<?php print($this->data['mainmenu']); ?>
I made this because I have a mainmenu and a submenu on the site I'm
working on, located on different places in the HTML part of the site.
The buildMainMenu and the buildSubMenu function both call a function
that gets the content of the menu structure (similar to
MediaWiki:Sidebar) and parses it. buildMainMenu and buildSubMenu then
render their part of the menu, depending on the page title.
This hook is useful to me, because it lets me add elements to the
template in a quick, clean and simple way. Is this also useful to the
developers community?
Boris
On 26/01/07, brion(a)svn.wikimedia.org <brion(a)svn.wikimedia.org> wrote:
> another dutch masquerading as english
In one of mine, too.
A possible reason it's not immediately obvious with a "brief test" is
because a "brief test" probably consists of accessing the extension
page or whatever with uselang=XX applied. However, if someone
overwrites the English messages, which act as a fallback, then
uselang=XX will fall back to the "English", which of course, will
contain whatever they just added, and it'll all appear to work.
I suggest that people extend their testing to *at the very minimum*:
* Do a lint (php -l blah.i18n.php)
* Check the thing still works as expected in English and ideally
another of the pre-existing languages
* Check the newly-added language works properly
Cheers,
Rob Church
An automated run of parserTests.php showed the following failures:
This is MediaWiki version 1.10alpha (r19662).
Reading tests from "maintenance/parserTests.txt"...
Reading tests from "extensions/Cite/citeParserTests.txt"...
Reading tests from "extensions/Poem/poemParserTests.txt"...
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!
The Gainsville (Florida) Sun [1] is remote loading English Wikipedia
content. [2] The Sun is serving up these pages using "pbcs.dll", which I
see installed at a lot of U.S. newspaper websites. However, prodding
around other websites that use this DLL only yields error messages, so I
suppose this "wiki template" is just an extension that the Sun happened
to be using.
[1] http://en.wikipedia.org/wiki/The_Gainesville_Sun
[2]
http://www.gainesville.com/apps/pbcs.dll/section?template=wiki&text=Special…
--
Minh Nguyen <mxn(a)zoomtown.com>
[[en:User:Mxn]] [[vi:User:Mxn]] [[m:User:Mxn]]
AIM: trycom2000; Jabber: mxn(a)myjabber.net; Blog: http://mxn.f2o.org/
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello!
You are receiving this email because your project has been select to
take part in a new effort by the PHP QA Team to make sure that your
project still works with PHP versions to-be-released. With this we
hope to make sure that you are either aware of things that might
break, or to make sure we don't introduce any strange regressions.
With this effort we hope to build a better relation between the PHP
Team and the major projects.
If you do not want to receive these heads-up emails, please reply to
me personally and I will remove you from the list; but, we hope that
you want to actively help us making PHP a better and more stable tool.
The final release candidate of PHP 5.2.1 was released today, it can
be downloaded from http://downloads.php.net/ilia/. We don't
anticipate any regressions, however if you spot any or come across
new bugs, please notify PHP's QA team at "php-qa(a)lists.php.net".
Given that this is the last RC, testing to identify any missed
regression is critical, if you have not tested any previous RCs,
please take the time to test this one to ensure 5.2.1 is as stable
and bug free as possible.
In case you think that other projects should also receive this kinds
of emails, please let me know privately, and I will add them to the
list of projects to contact.
Best Regards,
Ilia Alshanetsky
5.2 Release Master
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Darwin)
iD8DBQFFuUzWLKekh381/CERAhi7AJ9QPMq5J7qYdzpYiRlssXnewwg0qACeIkKr
UuM0jD6XPUoHzL1fJREs3NU=
=lXwn
-----END PGP SIGNATURE-----
My problem is these sitemaps are only for Google. If one wants a
sitemap for a visitor to browse, one has to make one by hand. The code
doesn't mention what to do if one wants a traditional sitemap.
Looking through Cite.i18n.php of the cite extension I stumbled over
these messages:
'cite_references_link_many' => '<li id="$1">↑ $2 $3</li>',
'cite_references_link_many_format' => '[[#$1|<sup>$2</sup>]]',
# An item from this set is passed as $3 in the message above
'cite_references_link_many_format_backlink_labels' => 'a b c d e f g h i
j k l m n o p q r s t u v w x y z',
Examples:
http://commons.wikimedia.org/wiki/User:Raymond_de/ref shows the "old"
style (with 2.0 2.1 2.2...)
http://de.wikipedia.org/wiki/Benutzer:Raymond/ref2 shows the "new" style
(with a b c...)
Do we really still need/support $2 in
'cite_references_link_many_format'? Can't it be replaced by $3 by default?
'cite_references_link_many_format' => '[[#$1|<sup>$3</sup>]]'?
I am unsure about the usage. Or are both variants common?
Raymond.
Brianna (pfctdayelise) wrote:
>
> I presume leaving 'Expiry' blank makes it infinite, like previously?
> Maybe it would be good to change the text to 'Expiry (optional)' or
> 'Expiry (leave blank for indefinite protection)' to make the behaviour
> clearer.
>
> cheers
> Brianna
> user:pfctdayelise
>
Well, I need to rewrite that part to be more like blocking anyway, simply
because it's not localisable, it's a bad user interface, and because of the
reason you mentioned.
More evidence as to the investigation about Brion's stolen crack stash :-)
Andrew Garrett
(Werdna)