From Kernel/System/Ticket.pm:

    # do not execute acls it userid 1 is used

    return if $Param{UserID} && $Param{UserID} == 1;

..

    # check acl config

    my %Acls;

    if ( $Self->{ConfigObject}->Get('TicketAcl') ) {

        %Acls = %{ $Self->{ConfigObject}->Get('TicketAcl') };

    }

Later, you can see that if the Debug level is > 2, it will tell you what Acl is matched.

To do this, in Config.pm write 

$Self->{Debug} = 3;

It might give you too much information, but you should also be able to see how to add your own Log where you wish to debug.

On Tue, Jul 2, 2013 at 3:02 AM, Bogdan Iosif <bogdan.iosif@gmail.com> wrote:

Hi list,

Can I configure OTRS to:

1. Write in a log file when Config.pm is reloaded? (Is there any other deterministic way to tell that the file was reloaded?)

2. Write in a log file when ACL parsing fails?

-=-

The reason I'm asking is due to troubles with my ACLs. I can't determine by myself why they don't work as expected because I haven't found ANY way to see a message from OTRS when ACL parsing fails. I checked the log file (\var\log\otrs.log) and Apache's log files (\logs\error.log).

I feel like I'm missing something super obvious. It can't be that ACLs either magically work or they magically don't.

Thanks,

Bogdan

---------------------------------------------------------------------
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

---------------------------------------------------------------------
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