MediaWiki-l August 2005

mediawiki-l@lists.wikimedia.org

137 participants
174 discussions

MediaWiki Installation question
by S. Morgan Friedman 02 Aug '05

02 Aug '05

Hi Everyone - I just installed the Mediawiki on my (Debian) server. The installation & configuration went perfectly, without a hitch. But, upon completion, when I went to the main page, I saw this error: Security Alert! The PHP CGI cannot be accessed directly. This PHP CGI binary was compiled with force-cgi-redirect enabled. This means that a page will only be served up if the REDIRECT_STATUS CGI variable is set, e.g. via an Apache Action directive. For more information as to why this behaviour exists, see the manual page for CGI security. For more information about changing this behaviour or re-enabling this webserver, consult the installation file that came with this distribution, or visit the manual page. I know little about PHP (but lots about some other languages!) and I'm not quite sure how do go about fixing this. A Google search wasn't useful and I wasn't able to find a search function on the mailing list archive so I can see if someone has asked this before. What do you recommend I do? Thank you so much for your help!!!! -morgan

3 2

Upgrading from 1.5b3 to 1.5b4
by Nicolas STRANSKY 02 Aug '05

02 Aug '05

Hi, I'm upgrading from Mediawiki 1.5b3 to 1.5b4. Is it possible to just replace the site files or is there a database change that makes it necessary to execute the installation procedure again ? Thanks for your help -- Nicolas STRANSKY Équipe Oncologie Moléculaire Institut Curie - UMR 144 - CNRS Tel : +33 1 42 34 63 40 26, rue d'Ulm - 75248 Paris Cedex 5 - FRANCE Fax : +33 1 42 34 63 49

6 9

Wiki email gateway
by Zain Memon 02 Aug '05

02 Aug '05

Is there some extension or such that would let me set up an email address that I can send an email to, and it will populate a wiki page with that email's content?

2 1

Install categorylinks SQL error
by John R. Owens 02 Aug '05

02 Aug '05

Using MediaWiki 1.4.7, MySQL 4.1.13, Apache 2.0.54, PHP 4.4.0, on a FreeBSD 5.4-STABLE box, the first time I installed went fairly smoothly. Then I realized that the installation had wiped out the cur table I'd already inserted, and the way the new MySQL is, that meant it was sitting around empty yet using up 8GB of space I had better uses for. So eventually, not being a real MySQL expert, I just rm -rf the MySQL db directory, recreate it and repop it with everything but the wiki databases, and go back to wiki/config/index.php. This time the installation didn't work; I get these messages, just fine up until the end: # PHP 4.4.0: ok # PHP server API is apache2handler; ok, using pretty URLs (index.php/Page_Title) # Have XML / Latin1-UTF-8 conversion support. # PHP's memory_limit is 8M. If this is too low, installation may fail! Attempting to raise limit to 20M... ok. # Have zlib support; enabling output compression. # Turck MMCache not installed, can't use object caching functions # Found ImageMagick: /usr/local/bin/convert; image thumbnailing will be enabled if you enable uploads. # Found GD graphics library built-in. # Installation directory: /usr/local/www/mediawiki # Script URI path: # Connected as root (automatic) # Connected to database... 4.1.13-log; enabling MySQL 4 enhancements # Created database wikidb # Creating tables...Query "CREATE TABLE categorylinks ( cl_from int(8) unsigned NOT NULL default '0', cl_to varchar(255) binary NOT NULL default '', cl_sortkey varchar(255) binary NOT NULL default '', cl_timestamp timestamp NOT NULL, UNIQUE KEY cl_from(cl_from,cl_to), KEY cl_sortkey(cl_to,cl_sortkey(128)), KEY cl_timestamp(cl_to,cl_timestamp) )" failed with error code "Specified key was too long; max key length is 1000 bytes". The only thing that comes to mind that I did differently when redoing the MySQL database was that I told it to use UTF8 as the default character set & collation; I suppose that might possibly affect the number of bytes in the key? Or is there some other reason behind this? Oh, and if I reload the page, I get much the same, except there are messages saying tables already exist before the real error comes around. Also, while I'm at it, from what I understand, PHP eAccelerator is supposed to be the successor to Turck MMCache, but it doesn't seem to be detected and considered equivalent. Is this typical, or did I perhaps not install eAccelerator right, too? -- John R. Owens ProofReading Markup Language: http://prml.sourceforge.net/

3 3

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

MediaWiki-l August 2005