> It would be useful if you gave the exact name of the message.
That brings up another problem, how is the user to figure that out?!
Here we see in an uselang=en dump, which doesn't have the bug, that
the page we are looking has all the trappings of the real
Current_events page, and unless one looks closely, one thinks it is
the Current_events page.
$ w3m -dump 'http://localhost/mediawiki/index.php?title=Current_events&oldid=99999999999…'
Current events
From 台掃
Jump to: navigation, search
The database did not find the text of a page that it should have found, named
"Current events,oldid=2147483647".
This is usually caused by following an outdated diff or history link to a page
that has been deleted.
If this is not the case, you may have found a bug in the software. Please
report this to an administrator, making note of the URL.
Retrieved from "http://localhost/mediawiki/index.php?title=Current_events"
And not even in the HTML source can one find the message name you
want. Any additional bugs I mention please report, if worthy.
OK, looking through Allmessages I dug it up:
$ w3m -dump http://localhost/mediawiki/index.php?title=媒體維基:Missingarticle\&action=raw
數據庫找不到文字"$1"。
<p>通常這是由於修訂歷史頁上過時的鏈接到已經被刪除的頁面所導致的。
<p>如果情況不是這樣，您可能找到了軟件內的一個臭蟲。
請記錄下URL地址，並向管理員報告。
The problem must be they forgot to close the <p>'s, so the 2nd one
ends up rendered. Ah ha! So do validate all your HTML before making
releases. You could probably cat(1) together all the items on
Allmessages, and send it all to the validate(1) program.
By the way, in
http://localhost/mediawiki/index.php?title=特殊:Allmessages&uselang=en
one can click on a link offered,
http://localhost/mediawiki/index.php?title=媒體維基:Missingarticle/en&action=ed…
but that won't get us anywhere, nor will
http://localhost/mediawiki/index.php?title=媒體維基:Missingarticle/en&action=raw
Indeed, the /en is not working.
Dear Travis,
The MetaProject on open proxies is quite active, albeit somewhat
backlogged at the moment. We're in the process of developing a
database to manage the open proxies that are blocked, which will solve
several of the problems with the current system.
Recently blocked open proxies are listed at
[http://meta.wikimedia.org/wiki/WM:OP/B]; older blocks became too
numerous to list manually, so they're categorized at
[http://meta.wikimedia.org/wiki/Category:Open_proxies_blocked_on_all_partici…]
until the database is ready. (We'll need to have a bot check to make
sure nobody added non-open-proxies to that category before importing
into the forthcoming database.)
Brion has nothing to do with the MetaProject to my knowledge.
Yours sincerely,
Jesse Martin
(Meta admin 'Pathoschild')
> From: "Travis Derouin" <travis(a)wikihow.com>
> I came across this page:
>
> http://meta.wikimedia.org/wiki/Meta:WikiProject_on_open_proxies
>
> Is this project still active? If so, is there any easy way to import updated
> versions of this list in an automated fashion? What's the obscure blacklist
> that was mentioned in this link, can you tell us more about it Brion?
>
> Travis
>
Hi all,
I developed these while I was in France and kept thinking I would
get around to polishing them off and delivering them to a mass
audience. However, I got distracted, so I'm hoping someone here might
find them interesting, develop them or at least polish them off and
make them widely available or something.
Anyway, they're linked from
http://en.wikipedia.org/wiki/User:Stevage/greasemonkey
EnhanceHistory is the cool one - it lets you see a visual history of
an article, by showing the actual text that was added (green) or
deleted (red) in each revision, with a tiny bit of context. However,
it has always had problems with the diffing algorithm. I tried 3
different publicly available javascript diffing algorithms, and each
had a different problem: extreme slowness, inaccuracy, or occasional
hangs (the one I'm currently using). Fortunately, replacing the diff
algorithm is very easy, if you know a better one, there's a simple
function call that needs to be replaced.
FilterWatchlist lets you temporarily hide certain categories of
entries from your watchlist. It's mostly been made redundant by
changes to monobook.js, but it might serve as a base for more
interesting customisations...or something.
For the confused, Greasemonkey is a client-side javascript running
extension to FireFox...it would be a nice idea to convert greasemonkey
scripts to browser-independent additions to monobook.css/js...
For any questions/comments, feel free to contact me here or on WP.
Thanks,
Steve
Hey ,all
I had put my skin code in function execute() of subbclass
inherited from QuickTemplate,i'm confused when generating html page, how
these
code within execute func be rendered? anyone give ideas
about call flow?
thanks
wind
_________________________________________________________________
率先尝试 Windows Live Mail。
http://ideas.live.com/programpage.aspx?versionId=5d21c51a-b161-4314-9b0e-49…
An automated run of parserTests.php showed the following failures:
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: Template with thumb image (with link in description)... 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: 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"...
Passed 451 of 471 tests (95.75%)... FAILED!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
There appear to be some major problems upstream from our European
proxies in Amsterdam; about 15 minutes downtime there so far. Mark's
switching DNS for Europe to the Florida servers in case the problem
continues.
Note that our Bugzilla installation is also hosted on the European
servers, so it'll remain offline as well until Amsterdam's back up.
- -- 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
iD8DBQFFdLO9wRnhpk1wk44RAtKRAKCqhuxQke0lZdMiQeHx1JkuHVdWYgCdFEy/
E06ZoHmKU38S02iUly0Lr10=
=6a3g
-----END PGP SIGNATURE-----
I see that in the last few weeks, [[:en:Template:lowercase]] has been
updated to actually display the title in lowercase with a JavaScript
hack. Any word on whether this is the long term solution to the
problem, or whether the proposed magic word[1] will be implemented?
Sorry, I don't know the relevant bug number.
Steve
[1] I think we discussed this maybe a year ago, the idea of letting
articles specify a "display" title. A first-letter-lowercase flag was
the least controversial idea...
I've been looking into the open proxy blocking functionality today and have
found some interesting things. Is this what Wikipedia is using to block open
proxies?
One issue that I found is that since proxy_check.php didn't send some client
and other relevant headers to the proxy, several proxies replied with "301
Moved Permanently" responses and wouldn't load the SpecialBlockme.php page
(which is a really cool idea by the way). I'm not sure why this was - but
adding in some fake firefox header information seemed to fix it.
Some proxies seemed to connect to a 2nd proxy before connecting to the final
server. For example if I set my proxy to 62.75.167.11:8080 ,
my IP ends up being listed as 62.75.136.84 when I edit a page, and this IP
is not accepting connections on 8080. This unfortunately circumvents the
benefits of proxy_checker.php.
SpecialBlockme doesn't have an expiry by default, it might be a good idea to
have a more realistic length of blocking especially for something that's
automated, like a global variable $wgProxyDefaultBlockLength which could be
set to something like "3 months". Also, SpecialBlockme doesn't record log
entries for blockingopen proxies, which admins might find useful, so I added
this to our setup by adding these lines:
$log = new LogPage( 'block' );
$log->addEntry( 'block', Title::makeTitle( NS_USER, $ip ), $reason,
$wgProxyDefaultBlockLength) );
I came across this page:
http://meta.wikimedia.org/wiki/Meta:WikiProject_on_open_proxies
Is this project still active? If so, is there any easy way to import updated
versions of this list in an automated fashion? What's the obscure blacklist
that was mentioned in this link, can you tell us more about it Brion?
Travis
Wikipedia has a problem
Sorry! This site is experiencing technical difficulties.
Try waiting a few minutes and reloading.
(Can't contact the database server: All servers busy)
----
Haven't seen this one before - doesn't have any link to fundraising or
anything either.
Steve
Hey,
I've been playing around with this setting and can't seem to get it to
work. Although I've set it in LocalSettings and made sure the open proxies
I've tested with are through ports set in wgProxyPorts, I can still edit
pages without a problem.
Any ideas?
Travis