New Front End Module

[Dev1]

I've followed the steps in the "tutorial" here: http://doc.otrs.org/developer/3.1/en/ht ... dp41886480

I've successfully built and installed the extension but it doesn't appear to do anything, I can't see any tabs or navbar - the only evidence that its actually installed is that it appears in the package manager. If I try to navigate using ?Action=AgentHelloWorld I receive an "Internal Server Error". I've cut and pasted the code directly from the the tutorial, built the opm etc. The only thing I'm not confident with is this throw away line: "After creating the links and executing the Sysconfig", how do I execute the Sysconfig? Please don't point me back to the article as I've gone over it many times and still can't see how I do it!

Has anyone successfully followed the tutorial and managed to get the module installed and working?

Thanks

Lewis

OTRS 3.1.12
Windows Server 2012

[jojo]

check the apache log, what is the exactly error?

[Dev1]

Whoops should have done that first! After checking the log it was showing that I'd missed a file. Fixed this, updated the version and upgraded my package, now I'm getting the following error in my log:

Notice: Install C:/PROGRA~2/OTRS/OTRS/Kernel/Modules/AgentHelloWorld.pm (644)!
Notice: Install C:/PROGRA~2/OTRS/OTRS/Kernel/Output/HTML/Standard/AgentHelloWorld.dtl (644)!
Notice: Install C:/PROGRA~2/OTRS/OTRS/Kernel/Config/Files/HelloWorld.xml (644)!
ERROR: OTRS-CGI-10 Perl: 5.12.3 OS: MSWin32 Time: Tue Jan 22 10:36:10 2013

Message: C-Parser:
XML declaration not well-formed at line 1, column 6, byte 6 at C:/Program Files (x86)/OTRS/StrawberryPerl/perl/vendor/lib/XML/Parser.pm line 187
!

Traceback (1788):
Module: Kernel::System::XML::XMLParse (v1.109) Line: 776
Module: Kernel::System::XML::XMLParse2XMLHash (v1.109) Line: 608
Module: Kernel::System::SysConfig::_Init (v1.34) Line: 1599
Module: Kernel::System::SysConfig::new (v1.34) Line: 126
Module: Kernel::System::Package::PackageUpgrade (v1.130.2.6) Line: 794
Module: Kernel::Modules::AdminPackageManager::_UpgradeHandling (v1.108) Line: 1567
Module: Kernel::Modules::AdminPackageManager::Run (v1.108) Line: 1044
Module: Kernel::System::Web::InterfaceAgent::Run (v1.64) Line: 868
Module: ModPerl::ROOT::ModPerl::Registry::C_3a_Program_20Files_20_28x86_29_OTRS_OTRS_bin_cgi_2dbin_index_2epl::handler (unknown version) Line: 49
Module: (eval) (v1.90) Line: 204
Module: ModPerl::RegistryCooker::run (v1.90) Line: 204
Module: ModPerl::RegistryCooker::default_handler (v1.90) Line: 170
Module: ModPerl::Registry::handler (v1.99) Line: 31

All the file contents are cut and paste from the link in the first post.

[Dev1]

Fixed the issue. The packaging step was pulling in files from the wrong place. The problem was\is that the otrs.PackageManager.pl searches the OTRS install path for my files to package, and so was basically repackaging the same files with a new opm.

So following the tutorial my environment is like this, with the files in the correct folders;
C:\Users\Administrator\Documents\OTRS_dev\HelloWorld
C:\Users\Administrator\Documents\OTRS_dev\HelloWorld\Kernel\
C:\Users\Administrator\Documents\OTRS_dev\HelloWorld\Kernel\Config
C:\Users\Administrator\Documents\OTRS_dev\HelloWorld\Kernel\Language
C:\Users\Administrator\Documents\OTRS_dev\HelloWorld\Kernel\Modules
etc..

I have a batch file that lives in the top level folder (C:\Users\Administrator\Documents\OTRS) that is used to repackage my files, it looks like this:

cd "C:\Users\Administrator\Documents\OTRS\HelloWorld"
perl "c:\program files (x86)\Otrs\Otrs\bin\otrs.PackageManager.pl" -a build -p helloworld.sopm
copy "C:\Users\Administrator\AppData\Local\Temp\*.opm" *.opm
del "C:\Users\Administrator\AppData\Local\Temp\*.opm"
pause

I was expecting the PackageManager to enumerate my development folders (listed above) but it doesn't, but rather enumerates the folders in C:\Program Files (x86)\OTRS\ to find my modified files. I've now added the following lines to my batch file in order to get it to build:

copy "C:\Users\Administrator\Documents\OTRS_dev\HelloWorld\Kernel\Modules\AgentHelloWorld.pm" "C:\Program Files (x86)\OTRS\OTRS\Kernel\Modules\AgentHelloWorld.pm"
copy "C:\Users\Administrator\Documents\OTRS_dev\HelloWorld\Kernel\Output\HTML\Standard\AgentHelloWorld.dtl" "C:\Program Files (x86)\OTRS\OTRS\Kernel\Output\HTML\Standard\AgentHelloWorld.dtl"
copy "C:\Users\Administrator\Documents\OTRS_dev\HelloWorld\Kernel\Config\Files\HelloWorld.xml" "C:\Program Files (x86)\OTRS\OTRS\Kernel\Config\Files\HelloWorld.xml"

This is clearly a hack but gets me going, after performing this step and installing my extension I can now see the new Frontend Module in my OTRS installation - I do however get another error when I select the new item but it's progress!

OTRS 3.1.12
Windows Server 2012

[reneeb]

Compare the path of your dev environment with the path in the batch file:

C:\Users\Administrator\Documents\OTRS\HelloWorld
vs
cd "C:\Users\Administrator\Documents\OTRS\HelloWorld"

You should build the opm from you dev environment

Add "-d ." at the end of perl "c:\program files (x86)\Otrs\Otrs\bin\otrs.PackageManager.pl" -a build -p helloworld.sopm

after the build of you opm file you should install it via PackageManager.