using $otrs/Custom

[schaffel]

Is there something that I have to consider when using the $otrshome/Custom directory?
I try to change some *.dtl files without adding a new theme. so I coppied them from $otrsho/Kernel/Output/HTML/Standard to $otrshome/Custom/Kernel/Output/HTML/Standard and changed them.
From the README file in the Custom directory I understood, that files inside that directory will be loaded instead of the default files. Is that correct?

To keep it short it didn't work for me. The OTRS still uses the default *dtl file.

Do I need to activate the feature of that Custom directory?

[StefanoBoccanera]

I can give my experience.
I used a theme for the frontend, and it works very well.
Probably the manual is not clear about it but in my opinion the 'custom' mechanism doesn't work with dtl and the 'theme' approach is an overlap method with 'custom' and of course is a mandatory solution.
You don't fear about 'theme', you can use it also for small modification to the dtl (no really different graphical theme).
About functional logic I used the 'custom' mechanism for both, kernel/module directory and kernel/system, and yes it's working very well.

regards

[schaffel]

Thank you for your answer.

I hoped that the *.dtl files are no special case.

What I feared was not to create an own theme but the efforts to disable the default and only allow the new theme.
I don't know exactly what I have to set or disable to make the new theme the default.

[jojo]

dtl files won't use custom. So they should be in Kernel/Output/HTML/yourfolder/xxx.dtl

yourfolder = Name of the theme