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/
" 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@optsistemas.com http://www.optsistemas.com ---------------------------
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
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
participants (2)
-
Alexander Scholler -
Miguel Angel Bayona Pérez