I'm a fairly new MediaWiki user. I just converted one of my wikis
over from TWiki. I'm running 1.3.8. I've run into something which I
haven't been able to figure out myself via the docs and googling.
I'd like to customize the Upload file special page. to give some more
help and advice to my users. Is there a way to do this, preferably
without PHP coding?
Even if I can't change the page, if I click on the image use policy
link I get a "No such special page" in response. Can anyone point to
were I can go to figure out how to fix this?
Hello,
We've got a mediawiki setup that we're using to create some
documentation. At some point in the future we will be ready to
release it, and continue developing in the background. Is there a way
to turn on a "No-Edit" lock on a page by page basis so that we could
freeze the released documentation, and continue editing on other
pages?
Thanks.
Regards,
Mark Norton
Hello,
I created an experimental debian package for mediawiki 1.4beta3 .
Please note this is the really first version of the package and it can
be unsecure and add bugs as well. You should probably not use it unless
you want to help testing.
It can be downloaded from my home computer:
http://dyn.twenkill.net/mediawiki_1.4beta3-1_i386.deb
I believe it can be installed on debian-stable, not sure though :o)
Be sure to read the /usr/share/doc/mediawiki/README.Debian file once you
installed the package, some work have to be done manually.
cheers,
--
Ashar Voultoiz - WP++++
http://en.wikipedia.org/wiki/User:Hashar
Servers in trouble ? noc (at) wikimedia (dot) org
"This signature is a virus. Copy me in yours to spread it."
Dear all,
I am happy to tell you that ENotif+EAuthent 2.00 has been merged into
the developing path of MediaWiki. This is sent only a short information
to keep you updated about the status
You can direct your questions directly to me.
Tom
hi,
While looking through recent posts to the mailing list and the mailing list
archives I was surprised to find that MediaWiki spam has not been discussed
very often.
We run a small MediaWiki site, and we have a large spam problem--we need to
regularly check the 'Recent Changes' page, remove spam, and then block users by
IP.
Given that our small MediaWiki has a large spam problem, I wonder what other
MediaWiki administrators are doing to deal with WikiSpam?
I noticed a feature on the wikimedia.org site earlier today that I think would
help our wiki out quite a bit:
http://meta.wikimedia.org/wiki/Spam_blacklist
I've tried creating this page on our MediaWiki, but it didn't work--i.e., after
copying/pasting that Spam_blacklist to the same location on our site, I was
still able to create a link to one of the pages on that 'URL blacklist'.
Is this a feature that is going to be included in the new 1.4 release, or is it
already in the 1.3.9 release? Is there a setting I need to enable in the
MediaWiki configuration files?
What other MediaWiki features are there to help reduce the spam problem?
thanks for the help,
-Mike
I entered this into bugzilla, but I'm posting it here in the hope that
someone can suggest a workaround.
Thanks,
David
Currently, list items are terminated by a newline. I'd like that rule to be
modified so that list items are terminated when the next line begins with some
sort of list specifier, or when the next line is empty (or perhaps only
whitespace). Lines that begin without list specifiers should be treated as
separate paragraphs.
The current rule makes it very troublesome to create list items with multiple
paragraphs, and as far as I can tell, there is no way to embed preformatted
text in a list item. For example:
# This is the first list item, first paragraph
This is the first list item, second paragraph
Here is some preformatted text with the first list item
Here is the rest of the preformatted text
# This is the second list item (numbered as 2)
With the current rule, the above is rendered as a single item list, then a
plain text paragraph, then a preformatted text paragraph, then a second single
item list whose number starts with 1. This makes it difficult to create
sophisticated lists. Under my proposed change, the above would be rendered
instead as a single list, where the first item contains two plain text
paragraphs and one preformatted text paragraph.
This change is mostly compatible with current Wiki pages, since most authors
would normally place an empty line after their list before starting non-list
text. One could justify the use of a single newline to start a new paragraph
instead of an empty line because one is in a list context. (i.e. the whole list
is a single paragraph.)
By the way, as a workaround I'm manually numbering my paragraphs:
1. This is the first list item, first paragraph
This is the first list item, second paragraph
Here is some preformatted text with the first list item
Here is the rest of the preformatted text
2. This is the second list item (numbered as 2)
Please let me know if you have a better workaround.
_____________________________________________________________________
Dr. David Coppit Assistant Professor
coppit(a)cs.wm.edu Department of Computer Science
http://www.cs.wm.edu/~coppit/ The College of William and Mary
One of the bot in the bot suite with the interwiki bot has the capability to show the category tree under a specific category.
The page http://meta.wikimedia.org/wiki/Interwiki_bot/Getting_started gives you direction to get the bot (in Python). The page doesn't mention it, but one of the script that you get is category.py which has a tree generation mode. The page generated will be displayed nicely, but will of course be static and need periodic refreshes.
-Vina
-----Original Message-----
From: Brion Vibber <brion(a)pobox.com>
To: MediaWiki announcements and site admin list <mediawiki-l(a)Wikimedia.org>
Date: Wed, 15 Dec 2004 16:43:52 -0800
Subject: Re: [Mediawiki-l] Category listing with hierarchal view?
On Dec 15, 2004, at 4:24 PM, Lisa Jill wrote:
> I have recently set up MediaWiki to use as an information repository.
> I am interested in using the Categories page as a table of contents.
>
> However, to do this effectively, I would like to do two things.
>
> 1) Have Special:Categories show a hierarchal view of categories, witih
> top level categories and sub-categories indented underneath.
That would be a really handy thing to have. We don't have this yet
mainly because extracting a tree from the link graph is not very
efficient, particularly on a large site like Wikipedia.
It would probably though be fairly easy to generate a tree by walking
through the links table; you probably would want to cache the tree data
and regenerate it periodically. (And make sure you don't get caught by
loops...)
Each entry in the categorylinks table links a page (by cur_id index
number) to a category (by name). Pages in the NS_CATEGORY namespace
(cur_namespace=14) are themselves categories, and their category
memberships denote child->parent relationships. So basically you'll
want to pull all the category memberships:
SELECT cur_title,cl_to
FROM cur,categorylinks
WHERE cur_namespace=14 AND cur_id=cl_from
and work out a tree of subcategory memberships from that. There is no
default root node, and there is no a priori restriction against loops,
so it might not be very clean.
There is an experimental 'category browser' mode which does some
limited sub-category display, but I'm not too familiar with it.
> 2) I would like to make a page that lists all entries organized by
> category, and paginated. So much like special:categories but with
> actual article listings in it.
Special:Categories just grabs the category names from the category
membership list in categorylinks, and throws away the page titles.
You'd want to do basically the same query, but without the DISTINCT and
pulling the titles out of a join to cur.
The QueryPage class might be too limited to support this paged output
cleanly, I'm not sure.
-- brion vibber (brion @ pobox.com)
Hi,
I'm going to write a couple functions for a bunch of new tags. All tags will
call the same function:
$wgParser->setHook( "tag1", "func" );
$wgParser->setHook( "tag2", "func" );
$wgParser->setHook( "tag3", "func" );
...
What do you say about passing the tag to the callback function?
So, instead of,
function func ( $input )
it could be,
function func ( $input, $tag )
so, a switch within the function can tell which tag caused the call. I
looked at the source code, Parser.php, it looks like a simple modification:
In the Parser.php, line 365 (ver 1.3.9) this:
$ext_content[$tag][$marker] = $callback( $content );
Can be changed to this:
$ext_content[$tag][$marker] = $callback( $content, $tag );
I already did this change on my code, I was wondering this could be
officially added to MediaWiki.
Just a suggestion to see if this would make life for some easier :)
Muzaffer
hello list
i am new to wikis but i am already convinced. But I've got one problem,
i wnat to makea wiki with articles in english in german.
Same as the real Wikipedia. I want to have an article and on the left-hand
navigation it should pop up 'other languages'. If I look at the article in
German, everything (also the navigation) should be in german. Same with
english. I've already googled for it, checked out the mailling list and used
the help at metawiki. Nothing worked out. Thought I can do it via namespaces
but I don't know how to do this. I already did:
$wgUseDatabaseMessage=true
tried links like:
:en:english_page
en:english_page
nothing worked!
Can anyone give me some advise or point me to a good howto
Thomas
--
Thomas Wedehase
Nuernberg, Germany
www.thomaswedehase.com