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 :-)
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*
The advice in the subject line is correct. Users should never be
deleted from the table for another reason; you leave a lot of messy
references to them lurking about which really does confuse the hell
out of the software.
MediaWiki does not support the deletion of users, and likely never will.
> From: Billy Covington <wrcovington(a)gmail.com>
> I am attempting to create a template in which all anyone needs to do
> to put a Google Map on a page is use a template with 3 variables
> (longitude, latitude, and description) using Evan Miller's Google Maps
> extension (http://meta.wikimedia.org/wiki/User:Emiller/
> The only problem is, Mediawiki won't read the variables if they're
> inside the <googlemap></googlemap> extension tags.
You will have to modify the extension to feed the included text
through the wiki parser.
> I am definitely no expert or even novice at php...
This would seem to be beyond your scope, then. It sounds like an
interesting project, but I have no extra time to help you right now!
Perhaps someone else with an interest will want to craft a solution.
:::: We may no longer have a free press, but it is reasonably priced.
-- John Cory
:::: Jan Steinman <http://www.Bytesmiths.com>
I downloaded and installed Mediawiki 1.5.5 a few days ago, and have been
having a look. I have pretty good experience in PHP, but it's my first look
One of the biggest things I have noticed is:
a) echo, doesn't
b) if I try and create my own "test_wiki.php" file calling wiki
functions/methods, I get I think errors but all that is displayed on the
screen is a complete blank
I suppose these things are basically the same thing. Is "echo" disabled?
Is there some other global setting I haven't seen which is stopping output
to the screen? Is there some magic constant that I have to set to get debug
output (I have found $wgDebugLogFile, $wgDebugRedirects, $wgDebugRawPage,
$wgDebugComments, $wgReadOnly, $wgLogQueries, $wgDebugDumpSql but they don't
seem to help much).
Thanks for any help.
I changed my logo by setting $wgLogo in LocalSettings.php. I believe
that's the right way.
It only shows up on some pages. It seems like it likes to show up on
editing pages, login pages--pages with forms. It doesn't show up on
content pages (when you're only reading them), the main page, etc.
When it doesn't show up, I don't see a broken image box or anything,
it's just not there.
It doesn't seem to matter what skin I use, and I've been sure to clear
cache and restart httpd, etc. It's actually happening the same way in
two different installations. In both cases the logos are nice and
small; one of them is a png with transparency and the other is a
non-transparent png. Any ideas?
Side note: I'm new to MediaWiki, but I'm having a really hard time
googling for help. If I include "MediaWiki" in the search string, the
results seem to return every third wiki out there, rather than help
about MediaWiki. Any tips there?
I run a wiki and like to upload bigger files (no matter what file type or
extension). When I try to upload e.g. pdf- or zip-files with a size of 4 MB
with the image upload function I got an error message "the uploaded file is
Is there a special parameter, which I have to configure? I did not find that
in the docu...
Here my only settings, which are out of the standard:
$wgFileExtensions = array( 'png', 'gif', 'jpg', 'jpeg', 'pdf' );
$wgStrictFileExtensions = false;
$wgUploadSizeWarning = 5000 * 1024;
$wgEnableUploads = true;
$wgUseImageResize = true;
$wgUseImageMagick = true;
$wgImageMagickConvertCommand = "/usr/bin/convert";
#$wgHashedUploadDirectory = false;
My version: 1.5.6 on apache 1.3.33, php4.3.10-16, MySQL 4.0.24, ImageMagick
version 6.0.6, PHP imagick version 0.9.11, debian 3.1.
10 GB Mailbox, 100 FreeSMS/Monat http://www.gmx.net/de/go/topmail
+++ GMX - die erste Adresse f�r Mail, Message, More +++
at the beginning, my english is not very well.
I've two different wikis (a German & an Italian WIki), they are connected
via interwiki links.
These Wikis have a CommonSettings.php.
How I can use images for the German and Italian Wiki at the same time?
At the moment the CommonSettings.php looks like:
## To enable image ads, make sure the 'images' directory
## is writable, then uncomment this:
$wgEnableUploads = true;
$wgUseImageResize = true;
$wgUseImageMagick = true;
$wgImageMagickConvertCommand = "/usr/local/bin/convert";
# If you operate multiple wikis, you can define a shared upload
# path here. Uploads to this wiki will NOT be put there - they
# will be put into $wgUploadDirectory.
# If $wgUseSharedUploads is set, the wiki will look in the
# shared repository if no file of the given name is found in
# the local repository (for [[Image:..]], [[Media:..]] links).
# Thumbnails will also be looked for and generated in this
$wgSharedUploadPath = 'http://www.xxx.ch/common/wiki/images';
# Path on the file system where shared uploads can be found
$wgSharedUploadDirectory = '/home/xxx/public_html/common/wiki/images';
# Set this to false especially if you have a set of files that need to be
# accessible by all wikis, and you do not want to use the hash (path/a/aa/)
# directory layout.
$wgHashedSharedUploadDirectory = true;
$wgSharedUploadDBname = 'The German(default) Wiki';
$wgUploadPath = "http://www.xxx.ch/common/wiki/images";
$wgUploadDirectory = "/home/xxx/public_html/common/wiki/images";
I'm working on a site at washingtonbibleforums.com using the
Cologneblue skin. I noticed that the background color is different on
the main page than on others. I tracked this down to the body tag. In
the body tag of the main page, the source shows FFFFFF as the
background color. In other pages, this is set to FFFFce. I can't find
anywhere in the code to get rid of that so I can set this with CSS.
Does anyone else know where to find it in the source?
Someone knows about any program (crawler) which I could install in my PC/win XP
in order to get a look of whatsoever Google's crawlers are getting from my
Thanks a lot, mauro.
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 267.15.6/257 - Release Date: 2/10/2006
So tonight I set off writing a short little extension for mediawiki, and got
in a fight with the parser.
My extensions characteristics, in short, are that: it takes arguments from
my defined tags and the content between the tags, and inserts them into a
strings (the content between the tags). Of course the parser is more then
happy to turn these into:
... implies the parser would have to be mucked with to prevent conversion of
But!!!!... a section or two above, it's stated that when you forcibly render
text with the parser, you can turn off the <p> tags with a simple 'false':
I'd think it'd be a short step to allow the extension to set a variable, or
call a method, essentially giving the parser the same 'false', as when it is
called directly: $wgOut->parse('text', false);
That sure would make life easier.
E.g. $wgParser->setHook( "MyExtension", "renderMyExtension", 'false'); ...
or maybe $wgParser->setPtag('false');
Hopefully somebody can tell me if I've missed some easy answer, or this
functionality is already there (no, I haven't read through Parser.php yet).
Or a second best: that there would be interest into adding this into nearby
I'm aware there is probably a 'long way' around this problem, i.e.: set a
hook for ParserAfterTidy, then find my tags+content, strip my tags and their
args, re-insert my args+content, and finally dump all of the page again...