Are there any plans on implementing a PDF export, etc, feature for the wiki (are there wikis that support this?) I don't let non-developers any access to my tracker, but the ability to export such a design wiki page to PDF would be nice to send to clients, etc. (After developers have collaborated on the feature/bug/etc)

The Wiki needs a link to return to the bug description page. It is a good idea.

will the wiki be implemented in the next version of mantis?

I like this idea a lot, but it needs to be able to hook into the predominant wiki engine, MediaWiki.

This is a mod to DokuWiki to allow template selection. Tempaltes are stored as normal wiki page within "Templates" namespace.
http://wiki.splitbrain.org/plugin:template_chooser

Following is a link to the page which includes a list of DokuWiki plug-ins:
http://wiki.splitbrain.org/wiki%3Aplugins

I see the working [Wiki] link next to the [Send a reminder] link.
I also see the label that indicates this site is Mantis 1.0.3.

How is this done? Is there a customization feature that I missed in 1.0 to do this? Is this site running some patches to 1.0.3? Are they listed somewhere?

Thanks.

jreb, the Wiki feature is a patch and is not part of Mantis 1.0.3. The Wiki integration is not planned to be implemented in 1.0.x releases. However, it may be part of the Mantis 1.1 release.

See the attached Wiki for both the vision for this feature as well as detailed steps on how to setup a similar integration. Note that the patch is "experimental" and won't be supported.

I would like feedback from anyone who uses this patch. Also ideas for the vision will be most welcome.

I've attached a PDF snapshot of the Wiki associated with this issue. This was done using CutePDF Writer ( http://www.cutepdf.com ) which is a free printer driver that generates PDF file from any Windows application. This approach will work well if the PDF is to be generated from a single Wiki page. For Wikis that can generate a single PDF from multiple pages (if any), then it will make sense to use the Wiki implementation. If there is a working implementation in the Wiki, it will also be cross-platform (although I'm sure there are tools that are similar to CutePDF for Linux).

From wiki: mantisbt:7075:integration_with_dokuwiki#configuration1

URL under which the wiki engine is hosted. Must be on the same server.

$g_wiki_engine_url = $t_protocol . '://' . $t_host . '/%wiki_engine%/';

This will not allow one to use different subdomains for the bug tracker and wiki.

For example, we use dokuwiki as our main webpage www.ourdomain.com, and mantisbt is located at bugs.ourdomain.com. Of course I've seen instances where it is bugs.domain.com and wiki.domain.com as well.

The $g_wiki_engine_url defined is just the default value, it can be overritten the same way $g_path can be overwritten in config_inc.php. This will all work as long as both Mantis and the Wiki are installed on the same server.

Will this integration allow a user to login via the wiki, and as a result also be logged in to mantis? Or is the authentication one way only? Only mantis to wiki? It'd be nice if it were both ways. (from the quick testing I did on the setup here, it is only mantis to wiki, and not the reverse). Obviously, regardless of which interface is used to login, it should use the mantisbt authentication.

Also, allow the wiki namespace could be configured per project via the mantis project admin web interface. Our wiki already has individual project namespaces, and I'd like to use the format of "<project>:issues:<bugid>" instead of the flat "mantis:<bugid>".

That also leads to being able to make the wiki feature enabled/disabled per project. So, have a global config file option to enable the wiki support with all of the relevant backend config, but by default no projects have wiki support enabled unless done through the web interface.

And one more thing in wiki_dokuwiki_get_url_for_page_id() you hardcode the use of 'doku.php?id='. And while that should basically always be valid (unles some wierd custom install), some installations use mod_rewrite (http://wiki.splitbrain.org/wiki:tips:modrewrite) to clean up the url that is used. It'd be nice to be able to use a 'clean' url for the wiki when linked from mantis. So, perhaps this could be made part of the configuration. $g_wiki_engine_url_link = 'doku.php?id=' or just set to empty if using mod_rewrite.

I really like this idea!

One issue for integration not mentioned yet are files attached to notes vs. files attached to wiki pages (or uploaded to the wiki in general) - I think files linked to mantis issues should refer to the same files that belong to the wiki page (or the other way round).

Without having used your integration (much) yet, I could imagine that there need to be clear rules of what is written in the wiki and what in mantis, e.g. where should I add comments - directly to the page or as a note to the issue. (In both cases you need a good notification of changes.) At least I was just confused about this myself right now: should I add the new requirement (attached files) directly in the wiki page or post it here? (I guess the notification about changes in the wiki is not yet integrated: users watching an issue should also receive notification about related wiki pages. Maybe you could specify the level of the distance from the main issue page.)

Well, I think in fact that the description of the issue could actually /be/ the corresponding wiki page - what do you think? Currently, the wiki page attached to this issue only contains links to other pages -- these links should be better placed directly in the description! I think it should be avoided that you need the description again on the wiki page. (As a side effect, you would also be able to access the history of the description.)

Is there any progress on a actual design that will integrate into a release of mantis. I get the impression that Victor intended this as a proof of concept, but it seems fairly clean to me even with the points that Peter brought up. Any idea where this fits into the road map?

It would be nice at the very least to attach a relationship for this to a future release so at the very least there can be a goal for it.

Using Mantis 0.19.1.

I followed the steps in the PDF attachment but have a few problems:
(BTW: a few lines in the PHP code in the PDF output are a bit too long are therefore incomplete)

I do have a Wiki-link next to the Docs-link but it links to wiki.php which does not exists!? (example: http://hol01sro/mantist/wiki.php?type=project&id=12)

And I don't have a Wiki-link next to the "Send a reminder"-link!?

I've update the associated Wiki page to include an update version of the code as well as missing pieces like wiki.php, updates to bug_view_page.php, bug_view_advanced_page.php, etc.

I've also committed the current implementation to CVS. Hence, this stuff will be part of Mantis 1.1.

Now that it is there, I'll be working on implementing improvements that I've included in the vision or that are recommended here.

Note that I didn't update the attached PDF. The master is always the Wiki. The PDF is just an example that the Wiki contents can be exported/printed to PDF.

The first version of the integration was released as part of Mantis 1.1.0a1.