Hi Renée,

are you sure custom Skins (Output\HTML) should go under Custom? It never actually worked for me this way either, and sounds as if it would go head to head against what the dev doc says about Skins:

http://otrs.github.io/doc/manual/developer/3.3/en/html/skins.html

I have a modified custom Skin under Kernel\Output\HTML\<custom folder name> and it works very nicely. It did not work when putting the custom DTLs under Custom\Kernel\Output\HTML\Standard.

Of course I had to create the required XML config entries before the Skin was usable (as explained in the above doc).

Cheers,

Peter

On Wed, Jul 2, 2014 at 5:28 PM, Renee B <otrs.list@perl-services.de> wrote:

Hi Jo,

On 02.07.2014 17:12, Josef1 Penzkofer wrote:
> Hi Renée,
>
> and this works properly?

yes. This should even work in OTRS 3.2.x (maybe not for templates, I
can't remember when that was fixed).

> Yesterday I wrote an E-Mail to "otrs-de@otrs.org" because I made changes in
> file "CustomerTicketMessage.pm".
>
> Therefore I copied the file in directory "/Custom/Kernel/Modules".
>
> The changes does not work.

Did you restart the Apache? Did you check if the "original" file was
loaded? Did you add some debug statements?

> The changes works, after I made the changes into file
> "CustomerTicketMessage.pm"; directory: /Kernel/Modules.
>
> Strange: I copied some other files into directory "/Custom/Kernel/... and made
> changes. This changes works.
>
> So, whats going wrong?

I'll have a look at the source code tomorrow. Maybe there is a
difference how Customer related modules  are loaded compared to the
modules related to the Agent interface.

> Thanks in advance.
>
> Jo

- Renée

--
Perl / OTRS development: http://perl-services.de
OTRS AddOn repository: http://opar.perl-services.de

_______________________________________________
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev