Hi Miguel,
Miguel Angel Bayona Pérez schrieb:
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
I can't see a problem (although I didn't verify your description).
I use a customer theme like this:
I only stored the DTLs which differ from Standard under
/Kernel/Output/HTML/my-theme.
If my-theme is used, OTRS looks for the DTL under my-theme, and if this
DTL is missing, the DTL under Standard is used (try it out!).
So, if you install an additional package which puts its DTL within the
Standard-theme, these DTLs should also be available for my-theme.
Let me know what you found out.
Bye, Alex
_______________________________________________
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
Support or consulting for your OTRS system?
=> http://www.otrs.com/
