DokuWiki Discussion

The discussion namespace can be used to discuss features of DokuWiki. However this usually becomes a mess, so using the mailinglist instead is highly recommended! Discussions here should finally be reworked into the “real” documentation for example in the manual or on the tips page.

Please do not add to this page directly - instead create new subpages in the list below or add to an existing subpage!

• Help - questions and technical support
• Distributed and Offline Wiki Clients - How to solve synchronisation problems with metadata and indexes?
• Storing wiki pages
• Relative Namespace upperlevel link Is it possible to do relative namespace upperlevel links?
• Dokuwiki and Emacs How manage Dokuwiki's pages from Emacs?
• Google Highlighting How to turn it off? (As a Config-Variable maybe…)
• main index - It gets very long, another solution than namespaces, to just split the long index list ?
• Recent Changes - Something with 1970/1/1 on top of the list.
• PluginAPI Ideas - discussion about a new plugin api and package management
• renaming doku.php some remote hosting services accept only “index.php” as start page…
• apache2 - Apache 2 configuration through .htaccess files that directly relate or have impact on DokuWiki's functionalities. (Here is another attempt for Windows address rewriting: apachewindows)
• RSS
• Firefox extension
• downloads
• images
• ACL and multiuser environments
• Usability
• Philosophy
• XMLRPC
• AtomAPI
• (Anti-)spam
• rendering
• wikimap
• statistics
• DokuWikiIntegration - GUI Editor and Wiki Parser Integration in other web applications.
• IntegrationWithApiDocTool
• exporting
• security
• managing data
• Print face and PDF format
• locking-unlocking
• PHP restrictions using ini_set
• ManageProfile – Updated to support 2005-07-13 release
• Floating/movable Table of Contents
• Performance or why is this thing so damn slow?
• WindowsShareLink detect all windows share links…
• NoNewline get rid of those '\\'
• CustomPHP – simple plugin capability using custom php inline includes (inline Sparklines example)
• FileManagement - make managing attached files easier
• tags - using the filesystem for del.icio.us style tagging of wiki pages
• Wiki CMS — Using DokuWiki to define a new breed of wiki-based CMS.
• WYSIWYG - Enormously increased usability for non-techie people with a WYSIWYG editor.
• doLinks - Is it possible to make links to &do commands like &do=login?
• 中文用户讨论 - For Chinese User（为中文用户）
• Install on Tomcat - Is it possible to install Dokuwiki on Tomcat?
• Better Notification - Wondering who did the update?
• Dynamic username – Is it possible to insert the currently logged in user into a link? SOLVED
• MediafileSelection User Accessability - Every user can access ALL files?
• Alternate NameSpace Template File - for yet none existing Sub NameSpace
• sidebar_plugin - Discussion about have sidebar as plugin and not as part of template
• installation_on_public_webserver - Discussion on the installation on a “normal” webserver and security problem or permission
• microformats - Usage of Microformats in DokuWiki and it's plugins
• minorChangesForAll
• dontSaveWithoutSummary
• Google AdSense - integrating Google AdSense adverts with DokuWiki
• php.ini - suggested php.ini values for use with DokuWiki
• currentDWStyle
• diff — Diff between two (arbitrary) revisions
• wiki_trails - Wiki trails proposal

• how to realize a contextual comment system with yui-ext – need help!

• display a list of users - How can i do this?
• pdf handling - Strategies for handling PDFs

The following pages contain discussion which are now obsolete but still present some knowledge worth to keep. Please refrain from editing these pages.

• Logo Contest – How the DokuWiki logo was created. A piece of history.
• EffDee Defacements – A security bug in an older version of DokuWiki was used for a mass defacement
• Bugtracking – This page reflects what was considered when choosing a bugtracker for DokuWiki. Contains a nice list of available bugtracking software
• Mailinglist – some software that was considered before deciding for a hosted solution