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
Approval of Signup Accounts Requirements [Mantis Bug Tracker Wiki]

User Tools

Site Tools


mantisbt:approval_of_signup_accounts_requirements

Approval of Signup Accounts Requirements

Introduction

This is a place holder for detailed requirements for feature implemented in the following issue: http://www.mantisbt.org/bugs/view.php?id=4112

Database Schema Changes

  • Schema Changes
  • Upgrade steps

Do we need a change in schema? Can't we set the access level to NOBODY and block NOBODY users from logging in? Then when user is approved we change the access level to default signup access level (e.g. reporter). This way we don't need schema changes or upgrade steps.

Configuration Changes

New Email Messages

  • What are the new messages?
  • Include sample messages?
  • Moderation email should include Approve / Delete / Reject. Delete should silently delete the request, reject should allow entering a comment. In the first version we can start with just Delete.

Future Ideas

  • Upon approving a signup request, allow the user to choose a user that can be used as a template for this newly approved user. The newly approved user then gets exactly the same access level and access to private projects that the template user has.

Feedback

Please place any feedback here.

mantisbt/approval_of_signup_accounts_requirements.txt · Last modified: 2008/10/29 04:25 (external edit)