Page 1 of 1
DokuWiki integration for a single project
Posted: 16 Aug 2016, 17:28
by Chewits
Hi!
Is it possible to integrate DokuWiki with MantistBT so that links in the main menu and on issue pages are available for the particular project(s)?
I tried to set these variables via [ Manage Configuration ] > [ Configuration Report ] page:
Code: Select all
wiki_enable: ON;
wiki_engine: dokuwiki;
But it does not work - "Wiki" link does not appear at all. If I set these variables via config_inc.php, everything works fine.
If it is not possible, maybe all $g_wiki_ variables should be enumerated in $g_global_settings?
Alexander
Re: DokuWiki integration for a single project
Posted: 17 Aug 2016, 07:38
by atrol
Chewits wrote:
Code: Select all
wiki_enable: ON;
wiki_engine: dokuwiki;
You have to set wiki_enable: 1 in database
ON is a numeric constant in our PHP code which is defined as 1
If you enter ON to the database configuration it is treated as a string, that's why it did not work for you.
Re: DokuWiki integration for a single project
Posted: 18 Aug 2016, 10:12
by Chewits
Hi atrol,
I've attached screenshots of how my config looks when I set it in database. There are no 'Wiki' links in this case.
But as soon as I set it globally in config_inc.php it works fine:
Code: Select all
$g_wiki_enable = ON;
$g_wiki_engine = 'dokuwiki';
I tried it with mantis 1.2.18.
Re: DokuWiki integration for a single project
Posted: 18 Aug 2016, 11:49
by atrol
You can't enable Wiki integration for specific projects.
You have to choose "All Projects" for the setting in database.
Re: DokuWiki integration for a single project
Posted: 19 Aug 2016, 18:01
by Chewits
Ok, thank you.
I think these variables should go to $g_global_settings in config_defaults_inc.php. If yes, I can create a pull request for that.
Re: DokuWiki integration for a single project
Posted: 22 Aug 2016, 17:28
by atrol
Chewits wrote:
I think these variables should go to $g_global_settings in config_defaults_inc.php.
After that you would need access to file system to enable/disable Wiki.
As much as possible (and reasonable in terms of security) options should be configurable in web UI.
The real problem is, that we don't have set any information which options should not be set per project and which options should not be set per user.
So we can't prevent useless settings on generic configuration page.