How do you hide the "edit" link to people who are not logged in?
I know it can be done because I've done it before. Unfortunately I don't
remember what I did. I checked the LocalSettings.php file and didn't
find anything. I'm using version 1.8.2.
After reading quite a lot about WikiWikiWebs (mainly for a university paper), I'm convinced that our project team could greatly benefit from employing a wiki.
I've already convinced the project manager that we should at least give it a try (mainly by stating how it won't cost a dime). Also, I've set up a local test environment (gotta love XAMPP), mainly for getting to know the MediaWiki engine.
However, predictably, many of my colleagues are quite skeptical - and to be honest, so am I to some extent.
Now I hope to benefit from the experts' experience on this mailing list:
a) How can I motivate my colleagues to at least try it out - and hopefully realize that it might actually be a great help to them?
b) What's required in terms of basic structure? Certainly some help pages for explaining the wiki syntax (though I'll probably link to Wikipedia rather than create it from scratch), but I'm sure there are a couple of other things to increase acceptance and participation.
Due to the large variety of projects people here are working on, it would be very hard to create a comprehensive basic structure right from the start. So I'll have to rely on the users/colleagues to create a kind of self-organizing wiki.
Any input on this issue would be greatly appreciated!
(Hopefully you won't mind if I incorporate those suggestions into my paper as well.)
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer
How can I link several MediaWiki Instalattions search,
I intened to have about 20 MediaWiki Installation and i want people to be
able to search one or all of them, maybe also select only few to run search
Is this easy to do?
I'm trying to install mediawiki version 1.8.2. I don't have root access
to MySQL ( not my server ). I created a database using the web tools ( I
think it's C panel ). When I try to install mediawiki it only uses the
user name in the "root" section. When I put in the master user name and
password the the hosting company gave me I get the following error message.
Error selecting database digital_wikidb: 1044 Access denied for user
What's going on here and how do I fix this?
I have installed mediawiki on my own server and ran into the same
problem. It only worked if I used the root account for mysql. Using a
user of the database would not work.
Ok, I haven't found a good explanation online.
How does the Commons work with the various projects to share content?
What are the Mediawiki configurations in use on the main Wikipedia /
other project / Commons sides?
-george william herbert
Well, if they won't search for the answer via google, they aren't going to search for it in the wiki. The key is not putting up a page on how to modify a doc. The key is putting the doc itself in the wiki. I know this doesn't translate really to spreadsheets, but you get what I'm saying.
----- Original Message ----
From: Frederik Dohr <fdg001(a)gmx.net>
To: MediaWiki announcements and site admin list <mediawiki-l(a)Wikimedia.org>
Sent: Tuesday, November 28, 2006 1:44:12 PM
Subject: Re: [Mediawiki-l] corporate wiki: success factors?
> In order for the wiki to succeed you have to first and foremost have
> the stamp of approval by someone with authority. They don't need to be
> 100% sold on it, they just have to allow you to use it and to give
> others access to it. That should be an easy sell.
Done; I got approval and set it up a couple of weeks ago - but it's more
like being tolerated rather than being promoted or encouraged. Also,
it's currently running on my local workstation (using XamppLite), but
hopefully I'll get the access data for the dedicated server soon
(internal bureaucracy delayed this by about two or three weeks already -
some people were worried that adding a new database might corrupt the
data of another MySQL-based PHP-site running on that server... ).
> Second, you have to put relevant useful content on the wiki that people need access to. Pay attention to docs that people are always looking for, modifying, etc.
Actually, this gives me a great idea; I'm known to be an Excel pro (not
exactly true in absolute terms, but certainly in relation to most of my
colleagues), so people occasionally approach me for help with their
spreadsheets. Some of these issues require a little macro programming,
but often I can just point to existing functions (e.g. autofilter) - if
I'd gather some FAQs there and publish them on the wiki, that might be
the perfect "gateway drug"...
MediaWiki-l mailing list
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail beta.
Here are my thoughts for what its worth.
In order for the wiki to succeed you have to first and foremost have the stamp of approval by someone with authority. They don't need to be 100% sold on it, they just have to allow you to use it and to give others access to it. That should be an easy sell.
Second, you have to put relevant useful content on the wiki that people need access to. Pay attention to docs that people are always looking for, modifying, etc. For example, we currently have no way to track individual projects here, we're a small shop and most things just get done in a couple days, no big deal. So when I setup the wiki, the first thing I did was setup a project template and put everything I was working on at the time onto the wiki. I setup a project status page that had rolled up info on all the current projects. When my boss or his boss wanted an update, I told them to check the wiki. They were blown away by the thought of having a quick snapshot of what everyone was working on, documentation, links to folders on the network for source code, production directories etc.
Another example was a lot of our network documention. I'm a programmer by title, but have some authority over the network side of things, so this particular approach may not work for you! I took some of the more static docs to start, like server info docs, howto's, etc, and put them on the wiki. i then DELETED the docs from the network. Guess our net admin is going to learn to use the wiki :)
To sum up, make a case for the wiki to get approval to use it. And then use the heck out of it. You'll have some early adopters that will see its usefulness to the organization as a whole and use it, not everyone has the 'what's in it for me' mentality. Those that DO will simply be forced to use it once it becomes integrated into the standard practices of the org.
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail beta.
> I am setting up a wiki to use for project documentation. I would like to
> able to specify page patterns with standard structures, headings and links
> that could be automatically loaded into the editor. So, for instance, a
> pattern page (I am avoiding the term Template, which seems to be something
> else) for a UNIX-style manual section would have pre-written headers for
> name, synopsis, options, known bugs, etc., along with perhaps some
> boilerplate. I would like users to be able to select among a number of
> pattern pages (maybe a dozen at most) when they create a new page.
I do this on our IT wiki implementation. Its mainly for documentation and to help the make sure we have a common design for our articles I setup templates. Then I have an "Add a New Article" page the user can go to. There's a section for each of the predefined pages the user can add, with a description and such so that they can make sure they know what its for. In each section is an input box specific to that article type in which they type the page name and click the "Create Page" button. using the preload option (ie preload=Template:New_Project), the page is created in edit mode with all the headings, default text, categories, etc.
Hope this helps,
Want to start your own business?
Learn how on Yahoo! Small Business.
I'd be interested to hear anybody's thoughts on the best way to
construct a large FAQ in mediawiki. I can see some advantage in
having lots of short pages, perhaps one Q per page in terms of being
able to assign categories and create an automatic index that way. But
that makes it difficult to browse and scroll around when you're not
sure what you're looking for.
So I'm leaning towards having several long pages each containing related Q&As
The main index page would then link to these pages, but ideally would
also list just the titles from each of the Questions in the other
So I'd like to generate a kind of TOC for a set of pages, perhaps but
I can't see how to do that at present.
I've been wondering about a persistant problem in MediaWiki. Whenever
anyone edits a page in any of the two wikis I run, the "This page was
last modified" data in the footer of that page is always incorrect,
by always stating the time for the *next to last* edit, instead
of the last edit as the string says.
It's not a question about clearing the browser's cache. No matter what
browser you use, you always get to see the date for the *next to last*
modification of the page, not the last modification.
This is pretty frustrating and makes the "This page was last modified"
string in the footer pretty much useless.
Can you suggest a solution for this?
For an illustration, see http://avenarius.sk . That's a fresh MediaWiki