Hi Alexander, what you say looks ok and reasonable application behaviour (if it is not in my-theme, the system looks for it in Standard). However since the installation of the ITSM packages (in 2.2.1 and 2.2.2), I was getting errors when using the ITSM and I could not p.e. create services. The problems went away when I copied manually the files that where in Standard and missing in my-theme. That´s why my explanation: if I must copy the files from Standard to my-theme AND this makes a difference, this means that OTRS is not looking in Starndard. If you have checked that this is not the case, this could mean that the problem is perhaps in my installation. My installation is: Ubuntu 7.04, Apache/2.2.3 (Ubuntu) PHP/5.2.1 proxy_html/2.5 mod_perl/2.0.3 Perl/v5.8.8 However, I´m using OTRS intensivelly in my team (5 people, 400 users) and the rest of the functionality (beyond some repetitive log messages "No FormatTimeString() translation found for '-' string!" that seems to be fixed in future 2.2.3 ) seems to work properly. Regards, Miguel Angel
Hi again,
Alexander Scholler schrieb:
/ 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. /Perhaps now I see. Could it be that the ITSM-packages does not only _add_ DTLs, but also _overwrites_ DTLs from Standard-theme. Then the reason for your problem is clear. My above description is helpful for you to get into less problems. For those DTLs which were overwritten by the package and differ from Standard within your theme, you have to take the new DTL, add you modifications and put this into my-theme. / />/ Let me know what you found out. />/ />/ Bye, Alex /Bye, Alex