Difference between revisions of "How to make dokuwiki a good mediawiki"

From Linuxintro
imported>ThorstenStaerk
imported>ThorstenStaerk
Line 13: Line 13:
 
* use mediawiki and patch/extend it until is can do ACL's. Accept that for a backup, a script is needed.
 
* use mediawiki and patch/extend it until is can do ACL's. Accept that for a backup, a script is needed.
 
* use dokuwiki and patches/plugins/skins until it looks like mediawiki and uses mediawiki's markup
 
* use dokuwiki and patches/plugins/skins until it looks like mediawiki and uses mediawiki's markup
 +
 +
Reading [http://www.mediawiki.org/wiki/Security_issues_with_authorization_extensions this] discourages going the first path with authorization extensions. So the only way to secure mediawiki would be to set up several mediawiki instances, an internal one, a public one and so on. This provokes so many problems that I decided not to go this way. The problems are:
 +
* you will have to do "recent changes" on both mediawiki instances in order to see the complete picture
 +
* you will have to search on both mediawiki instances
 +
* with two mediawiki instances, it is still not possible to have one page public to group A, and another one visible to group B.
 +
 +
What stays is to modify dokuwiki to get mediawiki's look-and-feel and its syntax.
 +
  
 
I want the ACL features of dokuwiki and the look-and-feel of mediawiki.
 
I want the ACL features of dokuwiki and the look-and-feel of mediawiki.

Revision as of 17:47, 10 July 2011

Comparing dokuwiki and mediawiki I come to the result that

mediawiki has the advantages

  • look and feel
  • known markup language
  • edit buttons are above the section to be edited

while dokuwiki has the advantages

  • ACL's allow me to keep pages invisible
  • backup is easy because it is plain files

So to get to my perfect wiki there are two basic ways:

  • use mediawiki and patch/extend it until is can do ACL's. Accept that for a backup, a script is needed.
  • use dokuwiki and patches/plugins/skins until it looks like mediawiki and uses mediawiki's markup

Reading this discourages going the first path with authorization extensions. So the only way to secure mediawiki would be to set up several mediawiki instances, an internal one, a public one and so on. This provokes so many problems that I decided not to go this way. The problems are:

  • you will have to do "recent changes" on both mediawiki instances in order to see the complete picture
  • you will have to search on both mediawiki instances
  • with two mediawiki instances, it is still not possible to have one page public to group A, and another one visible to group B.

What stays is to modify dokuwiki to get mediawiki's look-and-feel and its syntax.


I want the ACL features of dokuwiki and the look-and-feel of mediawiki.

html_secedit replaces ## by some text

See also


This article is a stub and needs improvement. You can help here :)