Hi,
I remember that there was a "email password" button on the account
creation page. I was able to register a user (with all details) and
then have the wiki email the account details and password to the user
email address. I have looked around the configuration instructions on
mediawiki.org and on the web, but can't find anything. Any ideas what
I might be missing?
We are using version 1.11.
Thanks,
Andi
<snip cool stuff about very slick new search functions>
So... still no category intersections? I'm merrily deveoping my CLucene
daemon, whether that ever ends up being of any use to Wikimedia or not...
(what are we using now, a GCJ'ed Lucene?) but I'm still a huge fan of
category intersections - and I think lots of other folks are too... all it
takes is another lucene index with an appropriate analyzer :-)
Here's an argument for both a) category intersections and b) an inclusive
policy with regards to articles/content:
The other day I was looking for video games to play with my kids, age 6 and
8. So I was looking for rmultiplayer games on a PC platform and after
visiting a few review websites, googling around, and ending up at a
Wikipedia article, I had an idea: I can do category intersections to look
for the games.
And what do you know?
http://aerik.com/cl_search.php?q=%2BMultiplayer_online_games+%2BWindows_gam…
With an inclusive article policy and more categories (tagging), it becomes
much more powerful... not just for video games, but for anything...
Best Regards,
Aerik
On Tue, Apr 8, 2008 at 11:50 AM, <aaron(a)svn.wikimedia.org> wrote:
> Log Message:
> -----------
> * Let MySQL choose among more indexes for title/user conditions
> # Don't use the wrong logging index
> - if( $this->title || $this->pattern ) {
> - $index = array( 'USE INDEX' => array( 'logging' => 'page_time' ) );
> - } else if( $this->user ) {
> - $index = array( 'USE INDEX' => array( 'logging' => 'user_time' ) );
> + if( $this->title || $this->pattern || $this->user ) {
> + $index = array( 'USE INDEX' => array( 'logging' => array('page_time','user_time') ) );
> } else if( $this->type ) {
> $index = array( 'USE INDEX' => array( 'logging' => 'type_time' ) );
> } else {
You're still making the assumption that the only indexes are
page_time, user_time, type_time, times. There's no justification for
that; third-party sysadmins may add custom indexes. Wikimedia has
some, in fact, for watchlists at least. IMO, you should only use USE
INDEX or FORCE INDEX at all when you *know* there's a specific problem
with how some versions of MySQL choose indexes. Otherwise it's
pointless at best, and possibly harmful.
I don't see any reason to force an index in any case here except when
there's a condition on log_type of the form log_type != 'x' or
log_type NOT IN ('x', 'y', ...), and no other conditions on log_type.
In that case, IGNORE INDEX type_time would probably be helpful.
I've noticed that the English Wikipedia is spitting out this error
message in place of the <references/> tag when there are no <ref> tags
anywhere in the article.
This is a new development, I believe? In the past I've sometimes thrown
a <references/> tag (or more specifically the {{reflist}} template) into
an existing references section even if there weren't currently any
inline references in the article, since I just as often put <ref> tags
into articles while neglecting to add a <references/> and wanted to make
things easier on future editors who might make the same oversight. I'm
not sure why this counts as an error now. Is it intentional?
On 4/8/08, Tim Starling <tstarling(a)wikimedia.org> wrote:
> Anon Sricharoenchai wrote:
> > == Negotiation for consent ==
> > Would it be possible to let the conflicting users to resolve the
> > conflict by themselves, not by the decision of the automatic system
> > using edit-count?
> > The renaming of username will be made on their consent.
> >
>
>
> I think the most important thing is that we don't put any unnecessary
> conditions on the deployment of SUL. I would like to see it fully deployed
> before I grow old and die.
>
Why should it be fully deployed?
Is it possible to leave the old unresolved conflicting account forever?
P.S. For the case that one can't resolve the conflict, if he REALLY
want a unify username, they have only 2 options,
1. rename his existing account
2. create a new account
I added this code to MediaWiki:Common.js
> var button = {
> "imageFile": "
> https://compbio.iupui.edu/support/wiki/images/e/e3/Button_GNU.png",
> //image to be shown on the button (may be a full URL too), 22x22 pixels
> "speedTip": "Use this to mark free software that's ALSO open source",
> //text shown in a tooltip when hovering the mouse over the button
> "tagOpen": "{{", //the text to use to mark the beginning of the
> block
> "tagClose": "GNU}}", //the text to use to mark the end of the block
> (if any)
> "sampleText": "" //the sample text to place inside the block
> };
> mwCustomEditButtons.push(button);
>
The goal is to put a *{{GNU}}* tag into the wiki whenever a button is
pressed. If I put the {{GNU}} within "tagOpen" the template is interpreted
before insertion into the page which is NOT what I want. The button should
insert the template name "{{GNU}}" and not the text the template
references. So I split the template in half but the cursor is in the middle
of the template. e.g.:
{{|GNU}}
>
What I would like to do is put the cursor at the end of the template. For
example:
{{GNU}} |
>
That way someone can insert the template and keep typing without messing up
the template. Any ideas on how to do this?
Thanks,
Jonathan Nowacki
--
IU Medical School
410 West 10th Street, Suite 5000 Indianapolis, IN 46202-5122
United States of America
On Tue, Apr 8, 2008 at 5:18 AM, <aaron(a)svn.wikimedia.org> wrote:
> Log Message:
> -----------
> Tweak - title index better than user in these cases most likely
> # Don't use the wrong logging index
> - if( $this->user ) {
> + if( $this->title || $this->pattern ) {
> + $index = array( 'USE INDEX' => array( 'logging' => 'page_time' ) );
> + } else if( $this->user ) {
> $index = array( 'USE INDEX' => array( 'logging' => 'user_time' ) );
> - } else if( $this->title || $this->pattern ) {
> - $index = array( 'USE INDEX' => array( 'logging' => 'page_time' ) );
In many cases that won't be the case, and the optimizer should be able to tell:
mysql> EXPLAIN SELECT
log_type,log_action,log_user,log_namespace,log_title,log_params,log_comment,0
AS log_id,log_timestamp,user_name FROM `logging`,`user` WHERE
(log_type NOT IN('suppress')) AND log_user = '1' AND log_namespace =
'0' AND log_title = 'Main_Page' AND (user_id = log_user) ORDER BY
log_timestamp DESC LIMIT 51;
+----+-------------+---------+--------+-------------------------------+-----------+---------+-------------------------+------+-------------+
| id | select_type | table | type | possible_keys
| key | key_len | ref | rows | Extra |
+----+-------------+---------+--------+-------------------------------+-----------+---------+-------------------------+------+-------------+
| 1 | SIMPLE | logging | ref | type_time,user_time,page_time
| page_time | 261 | const,const | 66 | Using where |
| 1 | SIMPLE | user | eq_ref | PRIMARY
| PRIMARY | 4 | enwiki.logging.log_user | 1 | |
+----+-------------+---------+--------+-------------------------------+-----------+---------+-------------------------+------+-------------+
2 rows in set (0.05 sec)
mysql> EXPLAIN SELECT
log_type,log_action,log_user,log_namespace,log_title,log_params,log_comment,0
AS log_id,log_timestamp,user_name FROM `logging`,`user` WHERE
(log_type NOT IN('suppress')) AND log_user = '1732' AND log_namespace
= '0' AND log_title = 'Main_Page' AND (user_id = log_user) ORDER BY
log_timestamp DESC LIMIT 51;
+----+-------------+---------+--------+-------------------------------+-----------+---------+-------------------------+------+-------------+
| id | select_type | table | type | possible_keys
| key | key_len | ref | rows | Extra |
+----+-------------+---------+--------+-------------------------------+-----------+---------+-------------------------+------+-------------+
| 1 | SIMPLE | logging | ref | type_time,user_time,page_time
| user_time | 4 | const | 1 | Using where |
| 1 | SIMPLE | user | eq_ref | PRIMARY
| PRIMARY | 4 | enwiki.logging.log_user | 1 | |
+----+-------------+---------+--------+-------------------------------+-----------+---------+-------------------------+------+-------------+
2 rows in set (0.17 sec)
Granted that that's on MySQL 5 (toolserver), not 4, but you don't need
to *always* force the index. Just make sure it's ignoring conditions
like log_type NOT IN ('suppress') by forcing times in those cases so
it avoids a filesort, and it should make a good choice. Or do you
know of further scenarios where it doesn't?
How does the caching of pages for the WMF projects work?
== Setting ==
On 1th April the [[MediaWiki:Tagline]] page, controlling the "From
Wikipedia, the free encyclopedia" text line, was changed several
times.
From; 08:06, 1 April 2008
until; 08:07, 1 April 2008
so at max 1 minute, probably shorter, the text was;
"From Britannica, the encyclopedia that is slightly more accurate than
Wikipedia according to a paper in the eminent journal ''Nature''... "
After that is was changed again a couple of times in to different
messages during that day;
From Wikipedia, the free Pokémon encyclopedia
From Whippetpedia, the free encyclopedia for dogs
From Wikipedia, the free encyclopedia administer by people with a
stick up their lavender passageway
From Wikipedia, the free encyclopedia that triples in population every
six months
One of the edit summary's was;
"Relax; these are completely harmless, and just for a day. "Yes, we're
aware of Wikipedia's criticisms, and we're still confident enough in
our project that we can joke about it"
== On topic ==
When I requested the page;
http://en.wikipedia.org/wiki/Blue_Gender
around midnight 2008-04-07 I noticed that the tagline on that page was;
"From Britannica, the encyclopaedia that is slightly more accurate
than Wikipedia according to a paper in the eminent journal
''Nature''... "
When I logged in it was gone, back the normal one. Also when I logged
out again it was also again the normal tag line.
== My question ==
How does the caching works?
I suspect that I have seen that changed tag line on that page because
that specific page was cached just in that very short time frame the
tag line was changed to that text. And because the page was not
edited that cached version was not renewed.
What I like to know is how long can cached version being used to show
a page when it is requested? When does it expire?
And because there are many squids; can it be that depending the squid
who serves you can get different results?
I would like to know that for use in wikizine.
--
Contact: walter AT wikizine DOT org
Wikizine.org - news for and about the Wikimedia community
> The big problem I can see with Semantic MediaWiki is that it involves
> horrible new wikitext syntax
Semantic MediaWiki lets you annotate links and values anywhere in wiki
text with the property they denote. With SMW you put the property name
before "::". That's it. Minimally horrible, compared to e.g. template
syntax ;-).
So
Berlin is the capital of [[Germany]] with a population of 3,391,407.
becomes
Berlin is the capital of [[Is capital of::Germany]] with a population
of [[Population::3,391,407]].
> ... although if that can be hidden inside
> the template code, all the better.
Yes, use of a templates may not have to change at all. Someone only has
to modify the template to output SMW syntax and property names in wiki text.
> Mostly what [infobox templates] need is
> standardisation
If all you're trying to do is capture information from infoboxes,
DBpedia shows how much is possible already, and standardization can only
help. But at some point you'll want to tell machines what the template
field names represent. (DBpedia does an amazing job of inferring the
type of a template field, but still gets some wrong.) The extensions
that extend the SMW extension are evidence that its formalism for
representing properties and datatypes within MediaWiki and thence in RDF
is useful. I hope any effort to "bring semantics to infobox templates"
would build on that.
Respectfully yours,
--
=S Page
