MediaWiki-l December 2004

mediawiki-l@lists.wikimedia.org

94 participants
155 discussions

Multiple languages
by James Gardiner 08 Jul '08

08 Jul '08

Morning! I am building a web site for a family member who is in the process of completing a PhD and MediaWiki looks like the ideal CMS to use as they will be able to update their own web site (delegation is always important :-) Two questions: 1) There may be a need to have certain pages in multiple languages. Is the best way to do this for a small site is to add a language identifier to the page title eg: here is the CV in [[CV.en|English]] or in [[CV.nl|Dutch]]. Is there a way to do this and still have a more readable title eg "English CV" rathern than "CV.en"? 2) I see from the LocalSettings.php that it is possible to prevent access to certain pages for users who are not logged in. Do I need to list all the pages I want blocked or is it possible to do wildcards eg internal* TIA James

6 6

help! tragedy!
by Moonlight Embrace 08 Feb '05

08 Feb '05

My webhost has just transferred one server to another, and in the process decided to run PHP as cgi! I no longer have pretty urls. Is there anything I can do about this?

8 10

Re: [Mediawiki-l] dealing with wiki spam
by Erik Hermansen 31 Jan '05

31 Jan '05

At 06:16 PM 12/17/2004 -0500, Michael Charters wrote: >What other MediaWiki features are there to help reduce the spam problem? You could require a login for edits. Sorry, if that is too obvious. :) http://meta.wikimedia.org/wiki/Access_Restrictions -Erik

3 2

Full text search
by Moritz Karbach 18 Jan '05

18 Jan '05

Hi, I'd like to have a full text search in my MediaWiki. I have got a page called 'Linux', containing several occurrances of the word 'tar'. But the search function doesn't find anything! I have checked the FulltextStoplist.php file, but it doesn't contain the word 'tar'. If I do a manual search through the mysql tables 'cur' and 'searchindex' I receive several hits... Can anyone help me? - Moritz

6 7

Re: [Mediawiki-l] Restrict editing to registered users?
by =James Birkholz= 07 Jan '05

07 Jan '05

Are WikiPedia images blocked from being downloaded? I tried transferring one of mine by "Save image as" but when I try to upload it back up into my wiki, I get an error: "Upload warning The file is corrupt or has an incorrect extension. Please check the file and upload again." I get an "unknow file type" if I try to open the image in Photo Editor. James Birkholz admin, Posen-L mailing list and website http://www.Posen-L.com

9 21

Change wiki.png image?
by =James Birkholz= 02 Jan '05

02 Jan '05

What is the best way to put my own image in place of the "wiki.png" image? I presume that I can edit all the .css files for the skins, but is there a global setting? James Birkholz admin, Posen-L mailing list and website http://www.Posen-L.com

6 6

link expansion problem
by Graham Seaman 31 Dec '04

31 Dec '04

Hi, I'm having a problem with a new install, where for example a link made on Main_Page like so: [[testing]] gets expanded to "/Main_Page?title=testing&action=edit", rather than to what I expect, which is "/testing?action=edit". Has anyone come across this before? All the menu links seem to be fine. I'm running debian, with: Apache: 1.3.26 PHP: 4.1.2-7.0.1 (I hope this isn't the problem..) $wgScriptPath = ""; $wgScript = "$wgScriptPath"; $wgRedirectScript = "/redirect.php"; $wgArticlePath = "/$1"; Thanks for any suggestions! Graham

3 4

Removing Talk function
by Cong Chinh Nguyen 31 Dec '04

31 Dec '04

I really don't want to use the Talk pages, and will have a separate forum for the editors. Is there anyway to disable the Talk function? Or at least remove all the "Talk" links? Thank you

1 0

Restrict editing to registered users?
by =James Birkholz= 31 Dec '04

31 Dec '04

I'm looking at using the MediaWiki software on my genealogy website for a genealogy wiki. I've (just) got an installation running and will be reading the manuals, but have a burning question that I don't see addressed in the Table of Content's. This wiki won't have near the traffic of a WikiPedia, but will deal with topics (History) that are often controversial and I wish to have a little more ability to control "troublemakers" who only use edit wars. 1) Is it possible to configure MediaWiki to restrict article editing to registered users? Or does this go against the concept too much? 2) Is it possible to require a valid e-mail address to register? If not, I would look at modifying the code (I work in php a little). In such a case, would anyone object to such a modification? 3) Is there any reason that I couldn't copy some articles (snapshot) from WikiPedia into my "GenWiki" if I note the source with something like "Some of the above text originally published at WikiPedia (link)"? Or "This article was derived fully or in part from an article on Wikipedia.org - the free encyclopedia. "? James Birkholz admin, Posen-L mailing list and website http://www.Posen-L.com

2 1

Re: howto setup MW for a SourceForge project?
by Thomas L Roche 30 Dec '04

30 Dec '04

Tom Roche Thu, 30 Dec 2004 00:43:53 -0500 ----- >> [Project needs and inherent SF insecurities seem] easiest to >> resolve by also putting the database in my project's SF web space: >> as long as I back it up regularly, the damage that can result from >> the insecurity is limited. But I note >> mediawiki-1.3.9/INSTALL >> > Required software: >> > * Web server with PHP 4.1.2 or higher (4.3.x is preferred) >> SF provides this, but ... >> > * A MySQL server. 4.0.x is preferred, but 3.2.x should >> > work as well. >> ... does SF provide that? If not, how best to provide a backend >> suitable for running an MW on SF? Can I just install MySQL in my >> project's webspace? Brion Vibber Thu, 30 Dec 2004 12:32:51 +0000 (UTC) ----- >> Yes Indeed! http://sourceforge.net/docman/display_doc.php?docid=3052&group_id=1 > ^ Project Database Creation » | doc feedback | support > To have a MySQL database created for your project, please have a > Project Administrator for your project make use of the Database > Admin tool within the Project Admin pages for your project. >> and yes you can, as longa s you trust every sourceforge member who >> is on one of the thousands of hosted projects to poke at your >> database (including access to password hashes). True that--but given that we will have no confidential information in the wiki, and the DB itself will be on SF, I believe we can take the risk. Following is my implementation plan: I'd appreciate if youse could reality-check and correct any omissions (un)found. Each stage prereqs any preceding: 0 setup 1 wiki restricted 2 wiki public 3 site transformation? <stage=0> Setup: I will * distribute DB id/pw to other admins * install MW (request more space if needed) * install phpMyAdmin (or preferred tool, but SF recommends phpMyAdmin) * setup SF basicauth for MW and pMA frontends and distribute id/pw * install minimal content, verify minimally-correct operation Required deliverables: * normal MW functions correctly working with minimal content * at least one successful manual DB backup </stage=0> <stage=1> Wiki goes live but with access restricted to small "beta-user" group responsible for * providing initial structure and content * ensuring that backups (including versioning) are suitable (e.g. automatable) Required deliverables: * normal MW functions correctly working for all users * core content installed, usably structured * at least two periodic DB backups (e.g. daily cron job) * at least two periodic versionings (e.g. daily commits of wiki contents to a CVS module, running from crontab using wix (or other tool) for file access) * at least one "complete restore": delete all wiki content, restore from backup or repository </stage=1> <stage=2> Wiki goes live alongside current project home page: * basicauth removed from wiki front page * SF project page>Home Page continues to link to current project home page * Current project home page gains a "Wiki" link in the navbar, otherwise no change. "Voyage of discovery" (perhaps stress testing the backup/restore functionality :-) Required deliverables: * happy users * happy admins </stage=2> <stage=3> Transformation. Wiki front page becomes project home page? Generate docs from wiki for File Release? I suspect we'll have more ideas during stage 2. </stage=3> Am I missing anything?

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

MediaWiki-l December 2004