DokuWiki Installer


This page assists in the first time installation and configuration of Dokuwiki. More info on this installer is available on it's own documentation page.

DokuWiki uses ordinary files for the storage of wiki pages and other information associated with those pages (e.g. images, search indexes, old revisions, etc). In order to operate successfully DokuWiki must have write access to the directories that hold those files. This installer is not capable of setting up directory permissions. That normally needs to be done directly on a command shell or if you are using hosting, through FTP or your hosting control panel (e.g. cPanel).

This installer will setup your DokuWiki configuration for ACL, which in turn allows administrator login and access to DokuWiki's admin menu for installing plugins, managing users, managing access to wiki pages and alteration of configuration settings. It isn't required for DokuWiki to operate, however it will make Dokuwiki easier to administer.

Experienced users or users with special setup requirements should use these links for details concerning installation instructions and configuration settings.

For security reasons this script will only work with a new and unmodified Dokuwiki installation. You should either re-extract the files from the downloaded package or consult the complete Dokuwiki installation instructions

driven by DokuWiki powered by PHP
UI grievances [Mantis Bug Tracker Wiki]

User Tools

Site Tools


UI grievances

This page collects various UI problems reported by users, to be taken as input for a MantisBT GUI redesign.


  1. can't relayout without touching every file
  2. tablebased & hardcoded styles
  3. rarely id or class attributes. no chance to css it


  1. I can't setup my own view of issues. I *think* that's my biggest gripe.


  1. test it out for a day or two and you'll know why :). Adding new entries to mantis takes way too much time.
  2. ah ok, not that mantis is a bad product, I used it for over 2 years. It's just the interface is too slow and needs a new look.


  1. #mantisbt is a good bug tracker, but he has an old layout, long development cycles and a complicated administration at file level.


  1. Well, mantisbt is good enough, unless you need to ldap auth, sso, or use the soap api. Oh, you just can't re-style.


  1. The design is very “oldschool” and I think it's actually ugly, so no good feeling while working with it, you know?


  1. Mantis customization only via config files, e.g. custom workflows
  2. little or clunky support for agile development.
  3. Jira has better overview of coming versions, better API, dated UI, file upload is better, Jira Connect.
mantisbt/ui_grievances.txt · Last modified: 2013/04/23 17:42 by atrol