There is a list of inactive wikis which should be locked at
http://meta.wikimedia.org/wiki/Inactive_wikis which are currently spam
traps, with many more to be added. I was wondering if this was still a
Steward privilege, or if we need to ask developers to lock these?
Amgine
Anthony DiPierro wrote:
> I found out what preload is. See
> http://en.wikipedia.org/w/index.php?title=Noarticlehere&action=edit&preload…
> So, in pseudocode (I don't know mediawiki), all that'd need to be done
> is change:
> return $text;
> to:
> if ($text!='') {
> return $text;
> } else if (namespace is article namespace) {
> return $newarticleboilerplate;
> } else {
> return '';
> }
Fabulous! Preloading a blank article form should be not terribly
traumatic ... How hard would it be to make the preload an option that a
regular editor can switch off when it gets annoying? (Though I for one
would probably keep mine on.)
[cc to wikitech-l]
- d.
when updating from mediawiki 1.44 to 1.53 i got errors whithin table "image"
the fields: img_width, img_height, img_bits, mg_media_type,
img_major_mime and img_minor_mime dit not get computed.
as a result on special-page "Gallery of new files" and on the imagepage
itself the images dont get displayed. whithin an article everthing is ok.
Heinz
-----BEGIN PGP SIGNED MESSAGE-----
Moin,
what is nec. to get the version information on that page for extensions:
http://en.wikipedia.org/wiki/Special:Version
On my (internal, 1.5.0) wiki, the extensions have their versions listed,
on a specific public one with 1.5.x they are missing - e.g. only the
"extension functions" are mentioned, but not the credits.
Is there a setting somewhere in LocalSettings.php that must be toggled to
enable them?
Best wishes,
Tels
- --
Signed on Sun Dec 11 10:52:39 2005 with key 0x93B84C15.
Visit my photo gallery at http://bloodgate.com/photos/
PGP key on http://bloodgate.com/tels.asc or per email.
"Any sufficiently rigged demo is indistinguishable from an advanced
technology." -- Don Quixote, slashdot guy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iQEVAwUBQ5v3t3cLPEOTuEwVAQGA+wf9ECuwAQEIAL4XWyi2D5PP+ByEJKYPU3ki
phPrmR+LaC5txz0iaK82lWIPB5OG8Zp7Dqk60sbzbNUKOAhtpfQncVQ9O7WxfgPF
ifZQCtzODa3ljLHQqKIzszW9efAbGb5fkhLbcdZ4ZJKhewiqZnIc6Qt4Zpcz1drN
1XYu0xb/bctc/MrIUPCa351o15IoCdcDP7JaV8ZNXrN0llf7cnPLGg9f3yyqkpEi
AiG4ID39Bk8VZZqQ9Vy1PM0klyCJ9UeP3k6zYFYCs3MZcv5NFc8P1gDv0n0l5vT4
cFTOTtaUoSRYudS2RV+t+7V+OMENjzE8FmpFBg4/Stul5ePebHb6Bg==
=DQOV
-----END PGP SIGNATURE-----
Just a relatively small hypothetical change I'd like to solicit feedback
on: Currently the page title (the part of the page rendered in <h1>) is
simply a single string, sometimes concatenated from multiple components.
I'd like to split it into an associative array, e.g.
array(
'action'=>'Editing',
'namespace'=>'Talk',
'mainpart'=>'French revolution',
'section'=>true
)
Except for 'mainpart', all keys would be optional. The main reason I'd
like to do this is so we can style namespaces separately from the title
(and perhaps even associate them with icons). But I think it would come
in handy for skinning in general.
Any objections to this change, or did I overlook any gotchas?
Erik
Why are there so few hooks in MediaWiki? Is this part of an effort to be
lean or have you not gotten around to it?
Aron
--
ssh aron(a)rubinium.org cat /dev/brain | grep ^work:
Aron Rubin Member, Engineering Staff
Lockheed Martin E-Mail: arubin(a)atl.lmco.com
Advanced Technology Laboratories Phone: 856.792.9865
3 Executive Campus Fax: 856.792.9930
Cherry Hill, NJ USA 08002 Web: http://www.atl.lmco.com
How can i let anonymus users chose their language eg. by clicking
buttons for "english" or "german".
I know this works for registrated users within preferences.
Any ideas?
Thanks, Heinz
Hallo,
Unser Projekt soll ein Wiki, dass in den Sprachen Deutsch,
Italienisch, Französich und English erhältlich werden. Dazu kommt ein
Wiki, dass nur für Administratoren da ist, sprich kein bearbeiten
für den user.
Bis jetzt habe ich nur die Mediawiki Software auf einer Deutschen und
dieser geschützes Wiki installieren können.
Ich habe zwei Ordner mit Mediawiki und zwei Datenbanken erstellt.
Der Skin sollte bei allen Sprachen gleich aussehen.
Wie ist es systematisch am besten, die weiteren wikis zu installieren?
Möchte nochmals mein Ziel erklären:
Der User sieht auf der Hauptseite links im Menu die verschiedenen
Sprachen, wenn er z.b. auf Italienisch klickt, erscheint der Artikel
auf Italienisch(inklusiv der Navigation). Und das mit allen Sprachen.
Wie ist das im Hintergrund am besten zu installlieren? Die Skins,
Extensions und ganz wichtig die Bilder sollten für alle verfügbar
sein (keine doppelten dateien). Wie mache ich dann dass mit der
Bilder Datenbank?
Vielen Dank im voraus
andy
Anthony DiPierro wrote:
> Right. It's not perfect. Just better. At least if someone is lazy
> and doesn't attribute something and then someone else catches them, it
> can be fixed.
> If we added a "references" field to the edit page, even if it was
> optional, the number of attributions would probably increase even
> more. The field would be unformatted, so someone could of course type
> "I just knew it" or "copied from some website" or even "poop" for
> their reference, but it'd be one more thing to look into if someone
> put their reference as "Wikipedia".
I put forward an idea a while ago which people weren't too keen on, but
I think it's time for it to be presented again: when a new article is
created, prefill it with text. e.g.
A '''pagetitle''' is ... (say what the article is about, with a bit of
introductory detail)
==More detail==
(If there's more to say about it, put in sections with == == on the name
of each section)
==See also==
==References==
* (List the sources you used in writing this article)
*
*
==External links==
* (List the few most relevant external web pages on the subject (home
pages, etc) that you know of)
While this would just be wikitext, and any experienced Wikipedia regular
could of course format an article how they liked, new editors would be
presented clearly with what we expect from a new article.
With this in place, I think we could even allow anons to create articles
again on en:. They certainly wouldn't just put "so what do you want me
to type?"
I'm not sure if Mediawiki has new article prefill as yet, but it can't
be that hard. The prefill wikitext could even be a Mediawiki: space message.
(Example of a new article I created today: [[XCB]]. I have something
like the above template in my head when I write an article.)
> Now, adding a references section would preferably add a column to a
> database table. Whether or not that would require scheduled downtime,
> I don't know.
Sounds like much more work than the above. The above would set out that
we do expect references and so on. Ultimately, I think guiding new
editors in how to do the right thing would work better than trying to
force a given article format in the database.
- d.
[cc: to wikitech-l]
Hello,
just for information. Upgrading might fail for duplicate content on some
fields who become a primary key.
Unfortunately, the 1.5 install isn't as verbose as 1.4 install:
***1.5 error message***
Making img_name the primary key... Query "ALTER TABLE image ADD PRIMARY
KEY img_name (img_name)" failed with error code "".
***1.4 error message***
Making img_name the primary key... Query "ALTER TABLE image ADD PRIMARY
KEY img_name (img_name)" failed with error code "Duplicate entry
'README' for key 1".
I suggest for users who have a duplicate content making a crash of 1.5
install, to revert their database and try the install with a 1.4. Then,
correct the database by suppressing one of the duplicate content, and
redo the 1.5 install.
I hope this is already in bugzilla (if not, maybe someone used to
expressing the bug could make it) and the install process in 1.6 are as
verbose as in 1.4.
François