Just a note of warning for those of you using MySQL 4.1: changes in the
new charset options may result in mysqldump outputting bogus data into
backups which can't be restored without data loss.*
This may affect some Unicode text, and certainly can irretrievably
corrupt compressed old revision text (using $wgCompressRevisions
option). If you're using MySQL 4.1, you should probably examine and
test your backup dumps to make sure they can be restored and used
successfully.
Passing an option like --default-character-set=latin1 may stop
mysqldump from trying to 'convert' (and thus corrupt) your data. (If
your server is not set to the defaults, this may or may not be the
correct value for you.) In the future hopefully we'll be able to play
nicer with the new character set settings, but for now MediaWiki
follows prior practice for older versions of MySQL where there was (and
remains) no ability to correctly indicate the charset used in a
particular database, table, or field.
* Specifically, a default "latin-1" to UTF-8 conversion silently
corrupts all bytes with the values 0x81, 0x8d, 0x8f, 0x90, or 0x9d by
turning them into literal question marks. The question marks cannot be
returned to their original byte values when the data is re-imported.
-- brion vibber (brion @ pobox.com)
Hey folks,
I've installed Mediawiki a few times now with great success; kudos to the
folks that made the install so painless.
I'm faced with installing Mediawiki on a machine which has a slightly
strange network topology. Basically, there are two interfaces on the
machine: one answers to machine.net1.example.com and the other to
machine.net2.example.com. Computers on the net1 local subnet are blocked
from accessing the machine over the net2 interface; same goes for net2
machines trying to get to net1. Apache considers the machine.net1 address
to be canonical, so after Mediawiki installs a machine that tries to reach
the Mediawiki install from net2 has their URL redirected to the canonical
net1 address, and therefore is blocked.
What I want to know is there a reasonably simple way to get Mediawiki to
disregard the canonical address and just use
http://machine.net2.example.com/ when referred to as such? Is there a
sane and safe way to disable the redirect?
Thanks much for any information,
jf
HI,
I have installed Mediwiki 1.3.8 on Solaris. I am very new to MediWiki. I have created table called "environment" and also loaded the data in to the table which is in the Database called "wikidb". Now how can I view ir from my mediawiki browser. what are the steps do I need to take inorder to appear my table in mediawiki browser.
Thanks,
Vani
Hello,
I recently started tinkering with MediaWiki, and I have a special case
that I couldn't find a solution to on the MetaWiki:
http://meta.wikimedia.org/wiki/Preventing_Access
I want to make a "HOWTOs" section on my wiki, and I want all anonymous
users to be able to read just that section, but not other sections'
pages. One method I thought would work was to create a
"Category:HOWTOs" and add pages into there, and then specify that
category be world readable:
# Pages anonymous (not-logged-in) users may see
$wgWhitelistRead = array ("Main Page", "Special:Userlogin",
"Wikipedia:Help", "Category:HOWTOs");
However this doesn't allow pages in the HOWTOs category to be seen
anonymously. I tried using a wildcard operator ' * ', but that didn't
work either.
Thanks for any help.
I've beaten my head against the wall for a few days, and give
up, so I'm requesting help.
Here is the config screen:
Please include all of the lines below when reporting installation problems.
Checking environment...
* PHP 4.3.2: ok
* PHP server API is apache2filter; using ugly URLs (index.php?title=Page_Title)
* Have XML / Latin1-UTF-8 conversion support.
* PHP's memory_limit is 20M. If this is too low, installation may fail!
* Have zlib support; enabling output compression.
* Found GD graphics library built-in, image thumbnailing will be enabled if you enable uploads.
* Installation directory: /var/www/html/wiki
* Script URI path: /wiki
* Connected as root (automatic)
* Connected to database... 4.1.7-standard; enabling MySQL 4 enhancements
* Database wikidb exists
* There are already MediaWiki tables in this database. Checking if updates are needed...
...ipblocks is up to date.
...already have interwiki table
...indexes seem up to 20031107 standards
...have linkscc table.
...linkscc is up to date, or does not exist. Good.
...have hitcounter table.
Converting links table to ID-ID...
Sorry! The wiki is experiencing some technical difficulties, and cannot contact the database server.
[XX@XX wiki]# uname -a
Linux XX 2.4.21-15.ELsmp #1 SMP Thu Apr 22 00:18:24 EDT 2004 i686 i686 i386 GNU/Linux
Relevant packages:
MySQL-client-4.1.7-0
php-mysql-4.3.2-11.ent
MySQL-server-4.1.7-0
httpd-2.0.46-32.ent
php-4.3.2-11.ent
php-mysql-4.3.2-11.ent
I've googled the mailing list archives and attempted to fix any
problems I see there. As you can see the database is getting created
and I've made sure that the wikiuser id has db grant access:
[XX@XX wiki]# mysqlshow
+-----------+
| Databases |
+-----------+
| mysql |
| test |
| wikidb |
+-----------+
mysql> grant all privileges on db.* to wikiuser@'localhost';
mysql> flush privileges;
I also attempted to get around what might be a problem with
the authentication scheme mentioned in the mailling list archives:
mysql> update mysql.user set password = OLD_PASSWORD('XXXXXX')
-> where host = 'localhost' and user = 'wikiuser';
mysql 3286 0.0 0.2 32148 12248 pts/0 S 13:06 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/XX.pid --skip-locking --socket=/var/lib/mysql/mysql.sock --old-passwords
I've opened permission on the config directory, there is nothing
of value in the httpd server logs or the mysqld log file.
Any other ideas? I'm really hoping for something easy I'm
overlooking.
Thanks.
-Jot
--
Jot Powers <misc(a)bofh.com> http://www.bofh.com
Bumper Sticker: Time flies like an arrow. Fruit flies like a banana.
I didn't know if anybody else would be interested in this or possibly
adding it into the MediaWiki source tree but figured I'd toss this out
for people to use or not use as they may. It enhances the keyword and
description meta tags of the wiki by first allowing you to set the
number of link text keywords by setting $wgKeywordsX. You can set the
default keywords and description with $wgKeywords and $wgDescription. If
either the keywords or description aren't set otherwise then they'll get
filled in with the link text (as keywords did before). If you also use
the extension then users can edit the page's keywords and description
when editing the wiki using the keywords and description tags.
This can be useful for more fine grained control over how search engines
index your wiki pages.
Change to includes/OutputPage.php.
---
# This function takes the existing and broken links for the page
# and uses the first 10 of them for META keywords
function addMetaTags () {
global $wgLinkCache, $wgOut;
global $wgKeywordsX, $wgKeywords, $wgDescription;
$good = array_keys ( $wgLinkCache->mGoodLinks ) ;
$bad = array_keys ( $wgLinkCache->mBadLinks ) ;
if ( ! ( $wgKeywords && $wgDescription ) ) {
$a = array_merge ( $good , $bad ) ;
$wgKeywordsX ? $wgKeywordsX : 10;
$a = array_slice ( $a , 0 , $wgKeywordsX ) ; # keywords max
$a = implode ( "," , $a ) ;
$strip = array(
"/<.*?>/" => '',
"/[_]/" => ' '
);
$a = htmlspecialchars(preg_replace(array_keys($strip),
array_values($strip),$a ));
}
$wgKeywords = $wgKeywords ? $wgKeywords : $a;
$wgOut->addMeta ( "keywords" , $wgKeywords );
$wgDescription = $wgDescription ? $wgDescription : $a;
$wgOut->addMeta ( "description" , $wgDescription );
}
---
New file, extensions/SEO.php.
---
/*
MediaWiki extension to allow wiki users to change the page's keyword
and description meta tags. Introduces the description and keywords tags.
*/
$wgExtensionFunctions[] = "SEO_DescriptionExtension";
$wgExtensionFunctions[] = "SEO_KeywordsExtension";
function SEO_DescriptionExtension () {
global $wgParser;
$wgParser->setHook( 'description', '_SEO_Description' );
}
function _SEO_Description ( $input ) {
global $wgDescription;
$wgDescription = $input;
return '';
}
function SEO_KeywordsExtension () {
global $wgParser;
$wgParser->setHook( 'keywords', '_SEO_Keywords' );
}
function _SEO_Keywords ( $input ) {
global $wgKeywords;
$wgKeywords = $input;
return '';
}
---
--
Michael <mogmios(a)mlug.missouri.edu>
http://kavlon.org
The first of the two conferences went quite well.
I only ran into a couple of problems and these
could perhaps be solved for the next conference.
It was held at Wentworth-by-the-Sea in Newcastle
NH, right next to Rye and Hampton Beach... the
place was gorgeous! And the facilities were awesome,
the AV folks there were very helpful in getting the
equipment all connected and very accomodating.
However the costs were pricey, an internet live
connect went for $150. A live AV support person
was $500 for the day... I didn't need an AV person
but even so, they were helpful anyway... no charge
for getting the connectors and making sure I was
ok to start the presentation, they were very helpful
indeed and very friendly!
All in all I presented on Friday and Saturday and
the headcount totals were over 100 educators,
school admins and staff from Northern New England
area.
The presentation on Wikipedia was well received...
the major objection, or should I say concern, is the
question that "how can Wikipedia content be
accurate without 'experts' writing the articles?"
My response is that the articles could be checked
against other online ecyclopedia content and thus
one could be reassured of the quality of content.
Also that there are safeguards like 'peer editing'
and 'npov' which help make the articles both
accurate and non-biased, or as much as a npov
objective can guarantee.
If there are other good points to counteract this
objection I'd be interested in putting this into the
next presentation... although for this next one
at McAuliffe Center Tech Conference I'll have a
fraction of the time I had at the NHAWLT presentation.
One of the problems I ran into was that I lost 'mousage',
I lost the mouse pointer, when I projected the laptop screen.
I used two different projectors and also tried an attached
USB mouse instead of the glidepoint.
But the instance of MediaWiki running
on the Linspire laptop was flawless of itself... a really
good example of how powerful and yet easy to use and
learn to edit the wiki engine is...
OpenOffice was very handy as a presentation tool.
I used the suggested presentation from French and
edited it and thinned it down for the time I had to
work with... I also used the screen shots of the
different language Wikipedias (that was done
around February)... And I incorporated the Alexa
charts to compare with Britannica, Groliers, Ecyclopedia.com
and refer.com so as to give some idea of Wikipedia's
growth and expansion.
I also briefly explained some of the other sister projects
and highlighted why the wiki software lends itself so
well to collaborative projects...
The next conference is in December.
With thanks to all who helped get me get MediaWiki
running on Linspire and also those that gave me
good suggestions on what to say during the presentation!
Best regards,
Jay Bowks
[[w:en:User:ILVI]]
On Wed, 27 Oct 2004 18:42:54 +0200, Ashar Voultoiz <hashar(a)altern.org> wrote:
> ilooy wrote:
>
>
> > Hi fellow Wikipedians,
> >
> > I'll be doing a presentation on Wikipedia for
> > the McAuliffe Conference and the NHAWLT
> > Teachers' Conference in the coming weeks
> > and was wondering if anyone else has done
> > a presentation to a large group... what features
> > would be good to highlight... and what seems
> > to work well with a group that has not heard
> > much about the project yet.
> >
> > If you have some ideas as to what might
> > be good points to bring out please let me
> > know. I appreciate any insights you may
> > offer on this subject.
> >
> > with sincere regards,
> > Jay B.
> > [[w:en:User:ILVI]]
>
--
--
ilooy.gaon(a)gmail.com
Hi,
we get the following error message on
http://www.vdr-wiki.de/wiki/index.php/Sysinfo-plugin :
Warning: imagejpeg() [function.imagejpeg
<http://www.php.net/function.imagejpeg>]: Unable to open
'/www/htdocs/v101777/wiki/images/thumb/8/89/180px-Sysinfo-plugin.jpg'
for writing in /www/htdocs/v101777/wiki/includes/Image.php on line 232
How can we avoid that error?
Thank you,
Markus