Hi
Thanks to all who responded. I finally did the following:
backed up Config.pm and Kernel/Config/Defaults.pm (I also did a
mysqldump of otrs database, just in case)
and then in /opt/:
~# tar xvf otrs-3.0.8.tar
~# mv otrs-3.0.8 otrs
~# cd otrs
restored both Config.pm and Defaults.pm from their b
Hello,
If a customer clicks a ticket and gets a "No Permission to use this frontend
module!", probably it's true. That can happen either because he's got no
permission under the queue where the tickets is (tough in this case he
wouldn't even see the ticket) or because there's an ro group associat
I'm no expert in OTRS, but maybe it's a Linux permissions issue?
Your OTRS files and dirs need to allow access to both user OTRS and group
APACHE - at least that's how my installation is and it's working fine...
//M
On Fri, Oct 21, 2011 at 9:30 PM, Arturo Castro wrote:
> Hi
> this is my first
Hi
this is my first post. I've searched previous posts and googled for
this issue, but I can't get a solution yet.
the issue is that when a customer clicks over a ticket, instead of it,
an error message is displayed:
*
Hi all,
after upgrading to 2.2.6 with ITSM 1.1.0 Beta 3 I can't link objects in the
agent interface anymore. Every call to AgentLinkObject2 results a
permission denied error with the message "No Permission to use this
frontend module!". Reading the code and googling did not help very much in
terms
