Just a quick update on this as I found some time to do some in-depth
digging.
It _was_ an issue with themes, but almost impossible to track down.
Back in the dim and distant past (otrs 2.4.x) we did indeed have our
own themes. But after upgrading to 3.0.x the default theme was much
better so we j
Preferences would be in a different location from security.
On Thu, Sep 6, 2012 at 12:01 PM, Mark Dissington <
mark.dissing...@netmania-it.com> wrote:
> Not that I can see. I've check agent <-> role and agent <-> group
> config. One agent has identical settings to my agent account, mine
> account
Not that I can see. I've check agent <-> role and agent <-> group
config. One agent has identical settings to my agent account, mine
account works OK, his has the problem.
I may strip all the group and role config down so everybody has rights
to everything and see if that sorts it. Any suggestions
I've checked our apache config and we already have utf-8 set as below:
AddDefaultCharset UTF-8
Anywhere else it could be configured? Strange that it works for some
agents but not others though, so wouldn't have thought it would be a
system-wide issue but maybe agent configuration perhaps?
M.
>>
Going with Alvaro's response, would non-working agents have preferences
different from working agent?
On Thu, Sep 6, 2012 at 10:47 AM, Alvaro Cordero wrote:
> Hello,
>
> I've seen this happening when you are using a default enconding that does
> not support some special caracters, for example in
Hello,
I've seen this happening when you are using a default enconding that does
not support some special caracters, for example in our case latin caracters
like "ñ", and the accent caracter, to fix that we changed the default
char-set to 'utf-8' and problem fixed.
You can check for that kind of
Hi Gerald,
It's not that nothing is displayed as you are typing, the customers list
appears and is filtered as for all agents as you are typing in the box, so the
customer DB is being queried and showing the same data for all agents. But if a
non-working agent selects any customer from the list
They won't populate if the customer is invalid.
On Thu, Sep 6, 2012 at 3:50 AM, Mark Dissington <
mark.dissing...@netmania-it.com> wrote:
> Hi Robert,
>
> Yes, I thought that was a possibility as well, but all the users are using
> the Standard theme.
>
> Mark.
>
> >>> On 05/09/2012 at 18:23, Rob
Hi Robert,
Yes, I thought that was a possibility as well, but all the users are using the
Standard theme.
Mark.
>>> On 05/09/2012 at 18:23, Robert Poreba wrote:
> Mark
>
> Are all users using the same Theme?
On 5 Sep 2012, at 12:58, "Mark Dissington"
wrote:
> Something very strange going
Mark
Are all users using the same Theme?
--
Kind Regards,
Robert
On 5 Sep 2012, at 12:58, "Mark Dissington"
wrote:
> Something very strange going on here with otrs 3.1.7 (now upgraded to 3.1.10)
> to try to resolve the issue.
>
> For both New Phone Tickets and New Email Tickets the custome
Something very strange going on here with otrs 3.1.7 (now upgraded to 3.1.10)
to try to resolve the issue.
For both New Phone Tickets and New Email Tickets the customer field won't
populate with the data from the Javascript customer search for SOME users. For
example my accoutn works fine - cre
11 matches
Mail list logo
