[otrs] BUG: packages and themes not working

[Miguel Angel Bayona Pérez]

Yes, the problem is when installing packages in an OTRS installation with custom themes.

As you know, when installing a package, several files are copied in the system. Some of them are copied in directory:

//Kernel/Output/HTML/Standard///

which corresponds to the "Standard" theme. When some one creates a custom theme, the system creates an extra folder:

////Kernel/Output/HTML/<My-Theme>/

and uses its contents instead the ones  of "Standard". The problem is that when installing a package, OTRS installs 
(as indicated in the corresponding *.opm////) files in the 

////Kernel/Output/HTML/Standard/////

folder and it does not install them under <My-Theme> and, therefore, the new installed packages do not work with custom themes.

I hope it is now clearer.

Regards,

     Miguel Angel

>/ /Hi Miguel,
>/ /
>/ /I can't follow you.

>/ /Miguel Angel Bayona Pérez schrieb:
>>/ Hi there,
/>>/
/>>/ after migrating to 2.2 and the creation of a new theme i´ve started to 
/>>/ receive strange or unrelated errors (some of them reported here by 
/>>/ me). At the beginning I thought it was due to inmaturity of ITSM 
/>>/ modules. After looking ate the code, it turns out that the problem is 
/>>/ WITH ALL MODULES and is due
/> What do you mean with module installation? Are you talking about 
> ITSM-packages?
>>/ that during the module installation they ONLY update the "Standard" 
>>// theme (i.e. Kernel/Output/HTML/Standard/*). If you are using only this 
/>>/ theme, then it is not a problem. However, if you have created your own 
/>>/ theme, it is not updated and the new module features do not work.
/>>/
/>>/ SOLUTION: modify the installation procedure of the modules to update 
/>>/ ALL the themes and  not only the "Standard"
/>>/
/>>/ WORKAROUND: it yoy use your own theme, befor installing a new module, 
/>>/ change to "Standard", install the module and manually copy the new 
/>>/ files in "Kernel/Output/HTML/Standard" to your 
/>>/ "Kernel/Output/HTML/<My_Theme>" directory, and then,  change again to 
/>>/ your theme.
/>I use a self-made theme and have no problems in v2.2.2 (without ITSM).
>>/
/>>/ Regards,
/>>/
>>//     Miguel Angel
/>
> Bye, Alex

-- 
---------------------------
Miguel Angel Bayona Pérez
OPT Sistemas
Avda. de los Prunos 11
28042 Madrid
T. +34 913 717 710
M. +34 639 197 571
mabayona at optsistemas.com
http://www.optsistemas.com
---------------------------