Wikitech-l March 2007

wikitech-l@lists.wikimedia.org

115 participants
173 discussions

Start a nNew thread

Christoph Hüsler steht nicht zur Verfügung.
by christoph.huesler＠css.ch 12 Mar '07

12 Mar '07

Ich bin abwesend und ab 30.03.2007 wieder erreichbar. Bei Fragen wenden Sie sich bitte an D. Brugger.

1 1

RSS feeds for watchlists
by Titoxd＠Wikimedia 12 Mar '07

12 Mar '07

Some pseudocode (someone who knows what they are doing should probably fix it :P): <?php //On clicking "generate a new token" in [[Special:Watchlist/feed]]: function setWatchlistToken( &$user ) { $token = $this->generateToken(''); $hash = md5( $token ); $dbw = wfGetDB( DB_MASTER ); $dbw->update( 'user', array( 'user_watchlist_token' => $hash), array( 'user_id' => $user->mId ), __METHOD__ ); return $token; } //Used by "get your current token" or by the reader itself function getWatchlistToken ( &$user) { $dbr = wfGetDB( DB_SLAVE ); return $dbr->selectField( 'user', 'user_watchlist_token', array( 'user_id' => $user->mId ), __METHOD__ ); } // Hash generator: md5 hashes are 32-dimensionally distributed; // mt_rand is 676-dimensionally distributed, as explained on IRC function generateToken( $ignore_salt_for_compatability = " ) { return base64_encode(mt_rand()); } function checkWatchlistToken (&$user, &$token) { $realToken = $this->getWatchlistToken($user); if ($token == $realToken) { return true; } else { return false; } } ?> Titoxd.

2 1

MediaWiki automated test run failure 2007-03-12
by brion＠pobox.com 12 Mar '07

12 Mar '07

An automated run of parserTests.php showed the following failures: This is MediaWiki version 1.10alpha (r20362). 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) [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 493 of 511 tests (96.48%)... 18 tests failed!

1 0

Re: [Wikitech-l] AJAX and .aspx as technologies for MediaWiki?
by Sheldon Rampton 12 Mar '07

12 Mar '07

Simetrical <Simetrical+wikilist(a)gmail.com> wrote: > Absolutely, many individual parts need reworking, and some major parts > (such as Parser) could use a total rewrite. But individual parts need > reworking, not the whole thing. My personal opinion is that the code should be rewritten so that articles are still largely *edited* in wikitext but get *stored* as XML. This would present several advantages: (1) The XML would be close to the HTML version that most people see when they view articles in their web browser, so less parsing would need to be done when presenting articles for viewing. (The XML storage format would have to provide equivalents of the current {{template}} tags, and those would still need to be parsed anew when the article is displayed, but overall the parsing load should be reduced.) (2) Adopting XML as a standard storage format would make it easier to port content between MediaWiki and other word-processor formats and content management systems. (3) Wikitext could be retained as an input format for people who wish to use it when creating or editing articles, but if articles are actually *stored* as XML, it would be easier to offer other input formats such as WYSIWYG. Going to XML would also require (and, perhaps, facilitate) more precise characterization of wikitext so that it becomes possible to establish a one-to-one correspondence between every possible wikitext markup and its XML equivalent. Of course, this should be done while preserving as many as possible of the existing wikitext conventions that are currently in use within the MediaWiki community. -------------------------------- | Sheldon Rampton | Research director, Center for Media & Democracy (www.prwatch.org) | Author of books including: | Friends In Deed: The Story of US-Nicaragua Sister Cities | Toxic Sludge Is Good For You | Mad Cow USA | Trust Us, We're Experts | Weapons of Mass Deception | Banana Republicans | The Best War Ever -------------------------------- | Subscribe to our free weekly list serve by visiting: | http://www.prwatch.org/cmd/subscribe_sotd.html | | Donate now to support independent, public interest reporting: | https://secure.groundspring.org/dn/index.php?id=1118 --------------------------------

12 25

cannot upload any images to commons,
by shi zhao 12 Mar '07

12 Mar '07

Today me cannot upload any images to commons, why? firefox display: reset. I use proxy: 66.230.200.195 -- Chinese wikipedia: http://zh.wikipedia.org/ My blog: http://talk.blogbus.com CNBlog: http://blog.cnblog.org/weblog.html Social Brain: http://www.socialbrain.org/default.asp cnbloggercon: http://www.cnbloggercon.org/ [[zh:User:Shizhao]]

1 0

Re: [Wikitech-l] Checkered background (from [MediaWiki-CVS] SVN: [20065] trunk/phase3)
by Erik Moeller 12 Mar '07

12 Mar '07

This change seems to be targeted at editors, rather than users of the wiki. For a user, the behavior of seeing a checkered background on a full size view serves no purpose and, indeed, obscures the content of the image. What is the justification for putting this in the default skin? On 2/26/07, leon(a)svn.wikimedia.org <leon(a)svn.wikimedia.org> wrote: > Revision: 20065 > Author: leon > Date: 2007-02-26 12:30:58 -0800 (Mon, 26 Feb 2007) > > Log Message: > ----------- > Added a checkered background for images on thei description pages. Useful to see transparancy. It's only monobook for now; I'm not in the mood to do the other skins right now, will add them soon. Commiting to not forget the rest, I guess this is better than nothing ;-) -- Peace & Love, Erik DISCLAIMER: This message does not represent an official position of the Wikimedia Foundation or its Board of Trustees. "An old, rigid civilization is reluctantly dying. Something new, open, free and exciting is waking up." -- Ming the Mechanic

8 10

MediaWiki automated test run failure 2007-03-11
by brion＠pobox.com 11 Mar '07

11 Mar '07

An automated run of parserTests.php showed the following failures: This is MediaWiki version 1.10alpha (r20334). Reading tests from "maintenance/parserTests.txt"... A database query syntax error has occurred. The last attempted database query was: " SELECT page_id FROM `parsertest_page` WHERE page_namespace = '0' AND page_title = 'Main_Page' FOR UPDATE LIMIT 1 " from within function "LinkCache::addLinkObj". MySQL returned error "1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'LIMIT 1' at line 1 (localhost)"

1 0

Running MediaWiki under PHP v5 binary?
by Ian Tresman 11 Mar '07

11 Mar '07

The latest version of MediaWiki v. 1.9.3 requires PHP v5 and mySQL v5. However, my server runs PHP Version 4.3.11 and mySQL v3.23.58, and they won't upgrade since it affects other customers. But my Web hosting company says I could run PHP v5 and MySQL v4 as binaries, but would MediaWiki work in this way? Regards, Ian Tresman

5 6

MediaWiki automated test run failure 2007-03-10
by brion＠pobox.com 10 Mar '07

10 Mar '07

An automated run of parserTests.php showed the following failures: This is MediaWiki version 1.10alpha (r20308). 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) [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 493 of 511 tests (96.48%)... 18 tests failed!

1 0

one-click image republishing/Commons promotion
by Brianna Laugher 10 Mar '07

10 Mar '07

Hello, I recently exchanged email with a chap, Mark Thomson, from http://yotophoto.com/ , an image search engine that indexes various copyleft(ish) sources including Wikimedia projects. He mentioned this plan of theirs: -------- 4) Yotophoto would like to enable one click republishing of images found so people can repost to their own blogs etc. To do this we will provide a copy and paste HTML code they can use. This code will link back to the image source (ie. Commons) as well as to the image license. Sites like Commons will get tons of back-links and exposure in this way I think. I like to think of this as the "Flickerization of Wikipedia" (and Commons). -------- As someone trying to raise the profile of Commons, I would be delighted to see this. However at the moment I haven't heard much about something like this except for "don't hotlink". I mentioned to Mark that this might be acceptable if they used the 150px or 250px thumbnails, but told him I would pass it on here for further comment. Thoughts? Would this be technically serverspeaking acceptable, probably acceptable, probably not acceptable or definitely not acceptable? :) cheers, Brianna user:pfctdayelise

1 0

← Newer
1
...
9
10
11
12
13
14
15
...
18
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Wikitech-l March 2007