#771 closed enhancement (wontfix)
DokuWiki Engine
Reported by: | Straider | Owned by: | Jonas Borgström |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | wiki system | Version: | 0.7.1 |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
Is there an easy way to closely integrate the DokuWiki engine with the Trac platform?
Not that the Trac Wiki engine isn't good enough, but because the DokuWiki engine has some very adequate features, such as Syntax Highlight, Section Editing, Windows Shares, Automatic Table of Contents, and others.
Thanks.
Attachments (1)
Change History (7)
comment:1 by , 20 years ago
Resolution: | → fixed |
---|---|
Severity: | normal → enhancement |
Status: | new → closed |
comment:2 by , 20 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Sorry, apparently Trac reset the resolution type to fixed when I previewed it.
comment:4 by , 17 years ago
Is there any way then to replace the Wiki section of Trac with a seperate Dockuwiki installation while still creating links and seamless references between bugs, tasks, changesets?
comment:5 by , 17 years ago
Not that I know of, but there's a wiki syntax replacement patch somewhere which implements most of the DokuWiki syntax within Trac, see …
Well, I just realized that this patch was in a mail exchange that happened outside of Trac-users.
I'm sure Matthieu Jonglez is OK with sharing his code, so here's his original mail:
Hi there, I investigated that over a year ago when we migrated from Dokuwiki + CVS to Trac + SVN. I first looked into doing that as a plugin but gave up on Christian's own advice and did a patch instead. Please find attached a zip containing: - the html output of the syntax example page (DokuwikiFormatting.htm) - the wiki text equivalent (as you can see it's dokuwiki syntax) (DokuwikiFormatting.txt) - a couple of screen shots illustrating the look and feel of the edit pages after the patch is applied - just in case you are trying to migrate for the same reason I did, tracdown.tgz a modified version of tracdown that supports multiple projects/product (supports recursive folders) You'll have to excuse the install process of the formatter patch: the makefile is kinda hardcoded but will probably only need minor editing for your install. Note that the trac goodies plugin is required for the emoticon. I am sure that the formatting patch must break a few of the plugins available out there, but I've been running it for over a year now with the following config (extract from my install script) (cd formatter && make) (cd goodies && python setup.py install) (cd ctxtnavaddplugin/0.10 && python setup.py install) (cd autowikifyplugin/trunk && python setup.py install) (cd newsflashmacro/0.9 && python setup.py install) (cd tracdown && python setup.py install) easy_install TracWebAdmin-0.1.1dev_r2765-py2.4.egg easy_install TracGantt-0.3.2a-py2.4.egg (cd TracTags && python setup.py install) (cd tracblogplugin/0.10 && python setup.py install) A final note: I can't remember which version of DokuWiki we were using, but we migrated over a year ago now... I haven't kept track of the syntax changes (if any) that took place so I can't guarantee it'll manage a 100% coverage of you wiki data. Regards, / Matthieu
And his contributions can be found in the attachment:trac.zip.
by , 17 years ago
Replace Trac's WikiFormatting with DokuWiki syntax, for Trac 0.10.4 (contributed by Matthieu Jonglez)
Since DokuWiki is written in PHP the integration would be problematic. For more powerful markup you can use WikiRestructuredText. The TracFaq is a good example of the table of contents generation. The way DokuWiki generates a small TOC at the corner of the page does seem nice though. However, individual features you'd like to see added to Trac should probably be filed under separate tickets.