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
Cloning Requirements [Mantis Bug Tracker Wiki]

User Tools

Site Tools


Cloning Requirements

  • Author: daryn
  • Status: Draft | Work in Progress


Development groups have different requirements for how they clone issues and what needs to be cloned. It is possible for different requirements to exist between different groups even in the same company. Currently the Cloning feature of Mantis is limited in it's implementation to basically an easy way to copy some issue data. I would like to expand the cloning of issues to provide greater control for administrators and greater functionality for users.

Current Approach

Currently cloning in Mantis is just re-reporting an existing bug as a new record. However, a limited set of data is copied to the new bug.

…expand to detail what happens in the current approach…

Proposed Approach

  • Give administrators the ability to configure what sections of data get cloned.
  • Give administrators a configuration option to allow users to choose which sections to be cloned.
  • Add access level threshold so administrators can limit which users can choose sections to be cloned.
  • Add ability to change the project and category for a cloned bug

If we have a set of options A, admin can select subset B of A, user can select subset C of A, where C may or may not be restricted to a subset of B …

Implementation Notes

  • Some notes

Database Changes

  • Required database changes to mantis_XXX_table


  • $g_var indicates something

Implementation Log

Other Changes


  • Please provide feedback
mantisbt/cloning_requirements.txt · Last modified: 2008/10/29 04:25 (external edit)