Re: [otrs] otrs 3.1.11 - otrs.Pendingjobs.pl

8:34 AM *To:* User questions and discussions about OTRS. *Subject:* Re: [otrs] otrs 3.1.11 - otrs.Pendingjobs.pl On 07/23/2013 09:11 AM, Steven Carr wrote: mailto:supp...@netwolves.com>,s...@netwolves.com <mailto:s...@netwolves.com>,rand...@netwolves.com <mailto:rand...@netwolves

Re: [otrs] otrs 3.1.11 - otrs.Pendingjobs.pl

Sent: Tuesday, July 23, 2013 8:34 AM To: User questions and discussions about OTRS. Subject: Re: [otrs] otrs 3.1.11 - otrs.Pendingjobs.pl On 07/23/2013 09:11 AM, Steven Carr wrote: mailto:supp...@netwolves.com>,s...@netwolves.com<mailto:s...@netwolves.com>,rand...@netwolves.com<

Re: [otrs] otrs 3.1.11 - otrs.Pendingjobs.pl

On 07/23/2013 09:11 AM, Steven Carr wrote: mailto:supp...@netwolves.com>,s...@netwolves.com ,rand...@netwolves.com > is an invalid email address. The match fail is because the content between <> doesn't conform to the rfc standard for a

Re: [otrs] otrs 3.1.11 - otrs.Pendingjobs.pl

is an invalid email address. The match fail is because the content between <> doesn't conform to the rfc standard for an email address (multiple @ signs for starters). You can't put multiple comma separated email addresses in a field designed for a single email address. Steve ---

Re: [otrs] otrs 3.1.11 issue

Thanks Gerald, I thought about that, but was hoping the routing that parses the email addresses for Net Ticket notifacations could be corrected so the people that enter the email addresses don't have to worry about a space "slipping" in. Obviously the routine used during add a note does not hav

Re: [otrs] otrs 3.1.11 issue

something like update customer_user set email=replace(email, " ", ""); might possibly be of use. (Backup first.) On Fri, Mar 22, 2013 at 2:58 PM, Steve Clark wrote: > Hi List, > > We upgraded from 2.4.x to 3.1.11. It has come to our attention by a > customer that only > one person was getting

Re: [otrs] otrs 3.1.11

> Edit Kernel/System/Ticket.pm and change line 3944, update the message > returned, change from 'Need StateID or State!' to "Need StateID or State! > Ticket: $Param{TicketID}". He does have a point, though. An good error message should give as much context as possible (answering the basic journal

Re: [otrs] otrs 3.1.11

Thanks. On 02/01/2013 07:34 AM, Steven Carr wrote: Edit Kernel/System/Ticket.pm and change line 3944, update the message returned, change from 'Need StateID or State!' to "Need StateID or State! Ticket: $Param{TicketID}". Steve On 1 February 2013 12:02, Steve Clark wrote: Hello List, Anyo

Re: [otrs] otrs 3.1.11

Edit Kernel/System/Ticket.pm and change line 3944, update the message returned, change from 'Need StateID or State!' to "Need StateID or State! Ticket: $Param{TicketID}". Steve On 1 February 2013 12:02, Steve Clark wrote: > Hello List, > > Anyone know how to identify the ticket number that is

Re: [otrs] otrs 3.1.11

There's also the possibility to either save again from Sysconfig after removal (Ticket.xml will help repopulate) or rebuildconfig from scripts. You may also want to be sure that OTRS has permissions within the web user (www-data or otrs) to write to the ZZZ files. On Thu, Jan 31, 2013 at 12:05 PM

Re: [otrs] otrs 3.1.11

Hello Yes it is OK. That's the way you return them to the default value. If you want to find out how to write them back, you can take a look at them at ZZZA *A*uto.pm and copy them back yo ZZZAuto.pm Leonardo Certuche www.itconsultores.com.co Medellín, Colombia On 31 January 2013 11:54, Steve C

Re: [otrs] otrs 3.1.11

Hello, I found that if I remove them from Config/Files/ZZZAuto.pm file they show up in sysconfig with their default values. Is it OK remove them from the ZZZAuto.pm file? On 01/31/2013 11:36 AM, Gerald Young wrote: Config/Files/Ticket.xml: Config/Files/Ticket.xml: Config/Files/ZZZAAuto.

Re: [otrs] otrs 3.1.11

Config/Files/Ticket.xml: Config/Files/Ticket.xml: Config/Files/ZZZAAuto.pm:$Self->{'Ticket::Frontend::CustomerTicketZoom'}->{'StateDefault'} = 'open'; Config/Files/ZZZAAuto.pm:$Self->{'Ticket::Frontend::CustomerTicketMessage'}->{'StateDefault'} = 'new'; Ticket.xml: Defines t

Re: [otrs] otrs 3.1.11

I only see them change On 01/31/2013 10:32 AM, Renee B wrote: Please ensure that those data aren't configured in Kernel/Config.pm Have you changed the XML file (Kernel/Config/Ticket.xml)? On 31.01.2013 16:26, Steve Clark wrote: Hello List, These two values have been altered from the default a

Re: [otrs] otrs 3.1.11

Please ensure that those data aren't configured in Kernel/Config.pm Have you changed the XML file (Kernel/Config/Ticket.xml)? On 31.01.2013 16:26, Steve Clark wrote: > Hello List, > > These two values have been altered from the default and I can't seem to > get them set back to the original value.