I'd like to make Lotus Notes databases available in mediawiki. For those
unaware it is possible to link to Lotus Notes databases using similar link
to a standard one. So instead of http://google.com (and "<a
I'd like to be able to link like:
notes://url/LotusNotesDatabase.nsf. For more info on Lotus Notes databases
check this forum: http://www-10.lotus.com/ldd/nd6forum.nsf?OpenDatabase.
I'd also like to extend the basic MediaWiki "linking capabilities" with
notes:// links - i.e. users should be able to link to databases from wiki
either by handtyping new link or using new button from toolbar.
If anyone know where it would be good to start (I thought about rewritting
parser.php or writing new extension) I would be v.grateful
I've noticed that only the title of my pages appears in the keyword
metadat of my pages. Is there some place to enable the addkeywords
function with category links ?
I'm running :
# MediaWiki: 1.8.2
# PHP: 5.2.0 (cgi)
# MySQL: 4.0.27
* Special pages:
* Parser hooks:
o DynamicPageList2 (version 0.7.7),
o ParserFunctions by Tim Starling
o Semantic MediaWiki (version 0.5),
I've noticed that the same thing happens on meta.wikimedia.org (running
1.9 alpha): the title is displayed in the metatags keywords list.
Maybe an extension breaks this feature.
Thanks for any advice.
>>> Fernando Correia<fernandoacorreia(a)gmail.com> 24/11/2006 17:10 >>>
>On the company I work for, we are in the process of centralizing all
>technical documentation of our software framework on the wiki, for use by
>several departments of the company.
>The idea is catching on and other departments are exploring the idea of
>using the wiki to document their knowledge and also to publish documentation
After some months trying to propel the use of a wiki wiki environment within a couple of research teams, I have concluded that a top-down approach is mostly required. I mean, when the head of a team asks team-members to discuss a contribution she/he has previously entered in the wiki by using the wiki, you will be successful for sure: there is not alternative to use the collaborative environment!
Of course you have to be attentive to the bottle-necks could cut productivity with such an approach. What you could get is no answers at all! So, to get a previous agreement on this way of contribution by a number of persons is advisable.
Workshops showing wiki work basics by using the wiki environment will also encourage people to follow the thread. Even probably you must be ready to suffer criticism and scepticism for a long while!
For me, at the moment, two major concerns:
1. Most of the team-members arrive to the wiki from a WYSIWYG environment. In spite of this fact, most of them are now using Mediawiki without problem. I'm trying to decide if the use of a WYSIWYG environment with the wiki is a must or could be avoided.
2. How to move wiki entries from Mediawiki to rtf, xml or OpenDocument formats.
As far as I see by reading this list entries, Mediawiki people philosophy are far from these two concerns. So they are from access control. And I can get their point! But at least in the kind of environment I am trying to introduce wiki culture rtf/OpenDocument document production and access control are required. As after a number of trials with other wiki packages I have successfully implemented a number of Mediawiki wikis I keep struggling to learn enough about this environment as to satisfy the needs of the groups.
Your XEN ICT Team
I am trying to install Media Wiki 1.8.2 but I am getting an error. It seems
that it is setting up all the tables in my data base but the last line says:
Parse error: parse error, unexpected $, expecting T_STRING or T_VARIABLE or
'$' in /mnt/w0710/d22/s30/b0285502/www/includes/Revision.php on line 298
Right before that it says: Checking for additional recent changes
...seems to be ok
Initialising "MediaWiki" namespace for language code en...
Does anyone have any ideas on what this is and how to fix it?
I have MW installed (v1.7.2) and I'm currently using one db for an
author's novel. The wiki for that one novel is in a subdirectory of
the main site.
I've been advised that it's best to just use one install and multiple
db's to have a wiki for each novel.
My question is, How to organize the one install. What should be at
the top level, and what should be in each subdirectory for each novel?
I would like to have a member's registration apply to all the novels,
and a search search all the databases.
I guess because I just have one wiki installation, registration would
be global and my real question is what needs changing? Somebody said
I need to do the configuring in LocalSettings.php, but I'm not sure
how to go about setting different db's for each novel.
Any helps is greatly appreciated and please let me know if I haven't
made myself clear here.
I am asking this question a second time in hopes that some GENIUS can help
me. I completely reinstalled MediaWiki 1.8.2 and it worked for all of 5 minutes
before I started getting:
500 Server Error
A misconfiguration on the server caused a hiccup.Check the server logs, fix
the problem, then try again.URL:
Looking at the server log, I see the error:
"Premature end of script headers: /home/xxxxx/public_html/wiki/index.php"
Thanks to François, I looked at:
....but neither was able to solve my problem. The host company has tried to
help, but they are not experts with MediaWiki, so this think it's the
software. However, given that thousands of people all over the world use the
MediaWiki, I think it must be something else.
Can anyone suggest ANY other thing I should look at or try?
> Hello Tim,
> It is a lot easier on your server to have a separate database and then
> hack LocalSettings.php so that it uses different databases for each
> subdirectory. Just have Apache configured so that it will redirect
> /novel2/Page to /w/index.php?title=Page as well as /novel1/Page to
Thanks Kasimir. I'm not that comfortable/knowledgeable about
configuring Apache. My host is Dreamhost and I do feel comfortable
editing the config file, but any details you could provide about
doing what you suggest would be greatly appreciated.
On 11/25/06, Tim Ware <tim(a)hyperarts.com> wrote:
> I want to move my wiki, now at the top level of the htdocs, down one
> level into a subdirectory. Any pitfalls here that I should be
> This wiki explores one particular novel of an author's, and I want
> to have another directory for another of his novels. Should I do a
> separate install of MW for the additional novel, or just a separate
> Ideally, I'd like to have a search where one could search either
> novel or both.
> I hope I'm being clear here. Thanks!
> MediaWiki-l mailing list
MediaWiki-l mailing list
I want to move my wiki, now at the top level of the htdocs, down one
level into a subdirectory. Any pitfalls here that I should be aware of?
This wiki explores one particular novel of an author's, and I want
to have another directory for another of his novels. Should I do a
separate install of MW for the additional novel, or just a separate
Ideally, I'd like to have a search where one could search either
novel or both.
I hope I'm being clear here. Thanks!
Firstly, I apologize if this has been answered before, but I am having some
problems getting my Media Wiki up and running. The install all went through
perfectly and everything seemed to be working fine until I started changing
the Admin users theme. All went wrong there. I have since reverted the theme
(by changing sql manually), but its still giving the same error. After that,
I tried registering a new user, and the new user produces the same, even
after just registering.
It seems that if i delete all my cookies for the wiki domain, the problem
goes away until i login again, then it gives the 500 server error all the
time. It have also noticed it happens if i try edit a page and im not
I am running PHP version 5.2.0, with apache 2.0.59. Mysql 5.0, and mediawiki
I get this in my httpd-error log: [Sat Nov 25 15:02:46 2006] [notice] child
pid 62542 exit signal Segmentation fault (11)
It only shows that when I get a 500 error. All my other sites work fine,
they all use sessions, cookies and various other things which all work fine.
Any ideas as to what could be wrong?