Hello Mr. Kenneddy,

In first time, i suggest you just to use one ACL. Maybe you could declare an
ACL when you avoid that all group users (except admin) can execute the
action. I would do that.

Sorry by the late answer.

Greetings,
Eduardo Raffoul



2008/2/8, Charles Kennedy <[EMAIL PROTECTED]>:
>
> Hi Eduardo,
>
> A part of my problem could be solved with ACL, but I the below ACL is
> not working for me.
>
>    $Self->{TicketAcl}->{'ACL-RemoveTicketMove'} = {
>         # match properties
>         Properties => {
>           # See, this is empty. Everybody matches.
>         },
>         # return possible options
>         Possible => {
>             Action => {
>                 AgentTicketMove => 0,
>             },
>         },
>     };
>     $Self->{TicketAcl}->{'ACL-AddTicketMove'} = {
>         # match properties
>         Properties => {
>             User => {
>                 Group_rw => [
>                     'admin',
>                 ],
>             },
>         },
>         # return possible options
>         Possible => {
>             Action => {
>                AgentTicketMove => 1,
>             },
>         },
>     }
>
> My intention on this was permit only the admin users move the ticket.
> What's wrong?
>
>
> Regards,
> Charles K. Schulz
> [EMAIL PROTECTED]
>
>
> 2008/2/8, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
> > Date: Thu, 7 Feb 2008 14:09:37 -0430
> > From: "Eduardo Raffoul" <[EMAIL PROTECTED]>
> > Subject: Re: [dev] Check user group or if user is admin
> > To: "Development community of OTRS.org" <[email protected]>
> > Message-ID:
> >         <[EMAIL PROTECTED]>
> > Content-Type: text/plain; charset="iso-8859-1"
> >
> > Hi Charles,
> > Hi Charles,
> >
> > Depending on what type of option you want to filter, theres 2 ways to do
> it.
> > If this option is related to properties of tickets, queues, or something
> > like that, an ACL would work fine. If what you want to filter is an
> entire
> > module, or some functionality of that module, you can put filter options
> in
> > the related /Config/Files/*.xml file. In Framework.xml you can see this
> >
> >     <ConfigItem Name="Frontend::Module###Admin" Required="0" Valid="1">
> > ... description stuffs...
> >         <Group>Framework</Group>
> >         <SubGroup>Frontend::Admin::ModuleRegistration</SubGroup>
> >         <Setting>
> >             <FrontendModuleReg>
> >                 <Group>admin</Group>
> > ... some other things....
> >             </FrontendModuleReg>
> >         </Setting>
> >     </ConfigItem>
> >
> > The key here is the <Group> tag, that is how the system knows that only
> and
> > admin user can access to the function or module. Take a look at the rest
> of
> > the file, or any other one, and maybe you'll find what you're looking
> for.
> >
> > Many greetings,
> > Eduardo Raffoul
> >
> > 2008/2/7, Charles Kennedy <[EMAIL PROTECTED]>:
> > >
> > > Hi,
> > >
> > > I have a option that will be visible only if the user is admin. So, I
> > > put a block in the dtl file and now I need to pass the data on the
> > > frontend module.
> > >
> > > How can I check if the user is of admin group?
> > >
> > >
> > > Thanks & Regards,
> > >
> > > Charles K. Schulz
> > > [EMAIL PROTECTED]
> _______________________________________________
> 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
>
_______________________________________________
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

Reply via email to