-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
January 24, 2007
This is a bug-fix update that fixes some installation and upgrade issues
with the original 1.9.0 release.
* (bug 3000) Fall back to SCRIPT_NAME plus QUERY_STRING when REQUEST_URI
is not available, as on IIS with PHP-CGI
* Security fix for DjVu images. (Only affects servers where .djvu file
uploads are enabled and $wgDjvuToXML is set.)
* (bug 8638) Fix update from 1.4 and earlier
* (bug 8641) Fix order of updates to ipblocks table for updates from <=1.7
* (bug 8673) Minor fix for web service API content-type header
* Fix API revision list on PHP 5.2.1; bad reference assignment
* Fixed up the AjaxSearch
* Exclude settings files when generating documentation. That could
expose the database user and password to remote users.
* ar: fix the 'create a new page' on search page when no exact match found
* Correct tooltip accesskey hint for Opera on the Macintosh (uses
Shift-Esc-, not Ctrl-).
* (bug 8719) Firefox release notes lie! Fix tooltips for Firefox 2 on
x11; accesskeys default settings appear to be same as Windows.
Full release notes:
http://svn.wikimedia.org/svnroot/mediawiki/tags/REL1_9_1/phase3/RELEASE-NOT…
Download:
http://download.wikimedia.org/mediawiki/1.9/mediawiki-1.9.1.tar.gzhttp://download.wikimedia.org/mediawiki/1.9/mediawiki-1.9.1.patch
MD5 checksum:
89f77d8f39fbefa4325e0fe4d06746c7 mediawiki-1.9.1.tar.gz
e9e3785068f9edc6169c4215bc65eff0 mediawiki-1.9.1.patch
SHA-1 checksum:
11418c10ac59c044ece1cc0dd20a32c74b96ec86 mediawiki-1.9.1.tar.gz
6eaf11390c1aaea87ff48d798f7fe564a341f249 mediawiki-1.9.1.patch
PGP signatures:
http://download.wikimedia.org/mediawiki/1.9/mediawiki-1.9.1.tar.gz.sighttp://download.wikimedia.org/mediawiki/1.9/mediawiki-1.9.1.patch.sig
Before asking for help, try the FAQ:
http://www.mediawiki.org/wiki/Manual:FAQ
Low-traffic release announcements mailing list:
(Please subscribe to receive announcements of security updates.)
http://lists.wikimedia.org/mailman/listinfo/mediawiki-announce
Wiki admin help mailing list:
http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Bug report system:
http://bugzilla.wikimedia.org/
Play "stump the developers" live on IRC:
#mediawiki on irc.freenode.net
- -- brion vibber (brion @ pobox.com / brion @ wikimedia.org)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFtyKJwRnhpk1wk44RAmIQAJsH/xB/lV+/gFHAbhEVWsXv1yoMLgCfWChB
r3LSI7FwfucNJ4qOliFJ8QA=
=rKzE
-----END PGP SIGNATURE-----
An automated run of parserTests.php showed the following failures:
This is MediaWiki version 1.10alpha (r19620).
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!
I keep getting the warning message about "Lost session data" when I go
to save changes at EN. This was a problem a few months ago, then was
fixed, but seems to be back. However there's a twist:
1) I click save (with an edit summary)
2) Preview comes up with message "Sorry! We could not process your
edit due to a loss of session data. Please try again. If it still
doesn't work, try logging out and logging back in." - edt summary box
still has my summary in it
3) I click save
4) Reminder: You have not provided an edit summary. If you click Save
again, your edit will be saved without one.
5) Save again - works.
On one or two instances, the lost session data error message has
appeared twice in a row.
Steve
On 23/01/07, leon(a)svn.wikimedia.org <leon(a)svn.wikimedia.org> wrote:
> * Added an option to make Linker::userToolLinks() show the contribs link
> red when the user has no edits. Linker::userToolLinksRedContribs() is an
> alias to that which should be used to make it more self documentating.
Oh, gross. Boolean parameters are horrible and meaningless less than a
month down the line when plastered all over calling code in this
fashion.
Rob Church
Why wont this work?
<gallery>
Image:{{{1|default.jpg}}}
</gallery>
Very weird. I'm on 1.8.2. Any ideas?
Rune.
_________________________________________________________________
Ta' på udsalg året rundt på MSN Shopping: http://shopping.msn.dk - her
finder du altid de bedste priser
Hi all,
Do you know all mayors from towns elevated higher than 1000m, all
sitcoms set in New York, or all philosophers that were influenced by
Friedrich Nietzsche?
Wikipedia contains information required for answering such questions,
but has the problem that its constricted search capabilities only allow
very limited access to its valuable knowledge-base. The Semantic Web
still lacks a critical mass of RDF data online and up-to-date terms and
ontologies are missing for many application domains.
The dbpedia.org project approaches both problems by extracting
structured information from Wikipedia and by making this information
available on the Web. dbpedia.org allows you to ask sophisticated
queries against Wikipedia (like the ones mentioned above) and to link
other datasets on the Web to dbpedia data.
dbpedia.org features at the moment:
* two large extracted datasets for different purposes
* a SPARQL endpoint and a data browser
* a visual query builder
More information about the project can be found at:
http://dbpedia.org
Since it is a first effort to make these available to a larger audience,
we appreciate any feedback, comments and ideas for improvements.
On behalf of the dbpedia.org collaborators
Sören Auer, Chris Bizer, Richard Cyganiak, Georgi Kobilarov, and Jens
Lehmann
Start a new thread,
Neil Harris wrote:
> Actually, digital identity management is more important than ever, and
> this time it looks like it's going to be done right. SUL is an important
> part of helping make that happen for Wikipedia and all of its attendant
> projects.
>
I agree, wearing two hats: the operations and security communities....
Good engineering practices often require stepwise refinement.
Single User Login may have been originally envisioned for convenience,
but the ease of use and project-wide consistency can also encourage
better security practices.
I agree that changes to the login procedure can wait until SUL is
deployed, as long as enhancements are well planned beforehand.
Speaking to elements of the recent thread, I'd prefer SSL instead of
home-grown challenge-response algorithms. As I'm the author of several
well-known challenge-response protocols, and an experienced network
operator, I can speak to the difficulty of proper implementation and
operation! Use the existing tools, where the problems are understood
and mitigated on a world-wide basis.
I also agree with Ivan (and others) that there is no technical problem
with MD5 as a salted hashing algorithm in this instance. But I do prefer
some flexibility toward future use of other algorithms for diversity.
I suggest that the software default to MD5 (as now), but the presence of
the "sha1:" prefix indicate the alternative. It seems reasonable to
design a migration path for the future, and that migration code should
be well tested before migration occurs.
I don't agree that sha256 be used until that is a standard part of the
software package. Experience has shown the folly of relying on
insufficiently deployed and tested security implementations.
In an ideal world, what features would the ideal Wiki Software have, and
what would it be like?
If we can answer this question, developmental direction is made clear. It is
easy to develop MediaWiki with view to improving it, streamlining it,
ironing out bugs - but much more difficult to look beyond it; for the future
of Wikimedia projects and general wiki success, new software must emerge
that caters for the new functions required by modern wiki users.
What functions would set MediaWiki well above all other wiki engines for
years to come?
What features would make it the most efficient wiki engine?
**What would the software be like if it generated maximal wiki success?**
To discuss this (what I find an interesting) question, I've set up a page at
http://meta.wikimedia.org/wiki/MediaWiki_Ideal
Obviously the answers to these questions won't necessarily be possible to
implement; but it would be interesting to know the answers nonetheless.
Look forward to some bright ideas :)
Hi,
Apologies if this question has been answered before or that it is on the main Wikimedia FAQ and I've missed it, but could someone let me know how I can edit the Special Wiki Page called "Wanted Pages". I want to add a bit of explanatory text which explains the purpose of the Wanted Pages special page.
Thanks very much in advance
Chris Kutler
Please don't print this e-mail unless you really need to.
---------------------------------------------------------------------------------
National Archives Disclaimer
This email message (and attachments) may contain information that is confidential to The National Archives. If you are not the intended recipient you cannot use, distribute or copy the message or attachments. In such a case, please notify the sender by return email immediately and erase all copies of the message and attachments. Opinions, conclusions and other information in this message and attachments that do not relate to the official business of The National Archives are neither given nor endorsed by it.
------------------------------------------------------------------------------------
An automated run of parserTests.php showed the following failures:
This is MediaWiki version 1.10alpha (r19600).
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!