Great stuff, thanks! Figured it was something like that, but my xml file
wasn't correct/complete. Couple more questions if you don't mind:
1. Now I'd like to fill the bottom window with [Foo Managment] when
clicked, is there a template Kernel/Modules/AdminFoo.pm for that?
2. Noticed that this kind of installation stuff is done automatically
when loading from the package manager. Is this interface definition for
OPM-files explained anywhere?
mvg, Kiffin
On Mon, 2009-12-21 at 17:02 +0100, Michiel Beijen wrote:
Hi Kiffin,
I'd recommend you to just take a look at existing configuration options.
In your case, you could create a file called Foo.xml with your
configuration options. This is a nice way to separate them from the
'canned' configuration options.
This file would provide an entry for the AdminFoo module. Just place it
in Kernel/Config/Files, go to Admin > SysConfig in the interface (this
will trigger the file rebuild) and the link will appear in the Admin
section, in this case on the bottom of the third row.
<?xml version="1.0" encoding="iso-8859-1" ?>
<otrs_config version="1.0" init="Application">
<ConfigItem Name="Frontend::Module###AdminFoo" Required="0" Valid="1">
<Description Lang="en">Frontend module registration for the
AdminFoo configuration object in the admin area.</Description>
<Description Lang="de">(German translation, if you feel like it,
otherwise leave the node out.)</Description>
<Group>Foo</Group>
<SubGroup>Frontend::Admin::ModuleRegistration</SubGroup>
<Setting>
<FrontendModuleReg>
<Group>admin</Group>
<Description>Admin</Description>
<Title>Foo</Title>
<NavBarName>Admin</NavBarName>
<NavBarModule>
<Module>Kernel::Output::HTML::NavBarModuleAdmin</Module>
<Name>Foo</Name>
<Block>Block3</Block>
<Prio>4000</Prio>
</NavBarModule>
</FrontendModuleReg>
</Setting>
</ConfigItem>
</otrs_config>
Hope this helps,