
Thanks for the tip. I've already studied that chapter, but to be honest found it a bit minimal and cryptic. You're right, the best thing to do would be to just dive into the code and figure it out from there. I'll see if I can document another example when I get some spare time. mvg, Kiffin On Tue, 2009-12-22 at 13:17 +0100, Michiel Beijen wrote:
1. No there is not; obviously you can use an existing module such as AdminType or so and work from that. If you like to create a template AdminFoo, maybe to go in the hello-world example, that would be great!
2. We would recommend all people who do OTRS customizations to use OPM packages for that. It just makes it really easy to separate modifications from the system, and it makes Dev > Test > Production moves easy. I guess you'd want to look at creating an .sopm file for your package, which is described here: [http://doc.otrs.org/developer/2.4/en/html/c1284.html]
You can then build OTRS packages by using bin/opm.pl -a build -p /path/to/Package-1.0.0.sopm
Hope this helps, --
Michiel Beijen R&D
OTRS AG Norsk-Data-Str 1. 61352 Bad Homburg Germany
T: +31 (0) 6457 42418 F: +49 (0) 9421 56818-18 I: http://www.otrs.com/
Business location: Bad Homburg, Country Court: Bad Homburg, HRB 10751, VAT ID: DE256610065 Chairman: Burchard Steinbild, Managing Board: André Mindermann
CU@ CeBIT 2010 in Hannover (Germany) and get to know more about OTRS at booth no. C37, in hall 2 from March 2-6, 2010! http://bit.ly/4qLvqm
Kiffin Gish wrote:
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" ?>
<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> Hope this helps,
--------------------------------------------------------------------- OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW! http://www.otrs.com/en/support/enterprise-subscription/
--
Kiffin Gish