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
Most active bugs summary [Mantis Bug Tracker Wiki]

User Tools

Site Tools


Most active bugs summary


The summary page could benefit from a list of the most active bugs, since active bugs are likely related to topics the users and/or the developers are interested in.

Several metrics were proposed as a measure of activity:

  1. the number of views of the given bug (currently, this data is not available in mantis)
  2. the number of monitors
  3. the number of bugnotes
  4. the number of attachments


The current implementation leverages the bug_history_table content to score the bugs and build the top ten list; this looks like the easiest way to take into account all of the above metrics (of course excluding bug views)

  • Each history entry weights as 1 point
  • only open bugs (e.g, with state below the resolved threshold) are listed

Of course we could refine the scoring function to give “better” results; for example:

  • weights more monitor events
  • weight more has_duplicate events
  • give negative weight certain events (unmonitor)

and/or provide a custom function hook to personalize the scoring function

mantisbt/summary_by_activity.txt · Last modified: 2011/11/16 07:42 by atrol