[rt-users] Get Queue CustomField value

2013-10-29 Thread andkulb
Hello, I have a queue named AAA. Then there are a custum field for queues - SubUnit with values: a, b, c. Queue AAA has a value 'a' of SubUnit custom field. How can I extract that value? I want to use that value on scrip. -- View this message in context:

[rt-users] Update all tickets of queue

2013-10-29 Thread andkulb
Hello, Is it posible with the help of scrip to do such thing: My Queue has a custom field and when you create a ticket in that queue, the ticket custom field is set by the value of queue custom field value. How can I change all queue tickets custom field value on Queue custom field value

Re: [rt-users] Update all tickets of queue

2013-10-29 Thread Kenneth Crocker
Have you tried bulk update? Kenn Sent from my Windows Phone From: andkulb Sent: 10/29/2013 6:21 AM To: rt-users@lists.bestpractical.com Subject: [rt-users] Update all tickets of queue Hello, Is it posible with the help of scrip to do such thing: My Queue has a custom field and when you create

[rt-users] canonicalizing URI fsck.com?

2013-10-29 Thread Len Jaffe
FOr some of my users, I see meesages of this form in my rt.log: [Tue Oct 29 19:25:25 2013] [debug]: Canonicalizing URI '21' to 'fsck.com-rt://mydomain.com/ticket/21' (/u01/app/PROD/rt4-efts/sbin/../lib/RT/URI.pm:108) What's up with fsck.com? Did I misconfigure something back in the beginning?

Re: [rt-users] Restrictions and limitations on use of ReferrerWhitelist, RestrictReferrer, RestrictReferrer (cross-site request forgery warning message)

2013-10-29 Thread Duncan Napier
Hi .. . Date: Mon, 28 Oct 2013 12:20:42 -0400 From: Kevin Falcone falc...@bestpractical.com To: rt-users@lists.bestpractical.com Subject: Re: [rt-users] Restrictions and limitations on use of ReferrerWhitelist, RestrictReferrer, RestrictReferrer (cross-site request forgery

[rt-users] Upgraded 3.8.8 - 4.2.0, IE issues

2013-10-29 Thread Tom Lahti
I just upgraded from 3.8.8 to 4.2.0, and we're having some difficulty with Internet Explorer. It seems it is unable to submit forms except for the Jumbo form. There's no errors, it just redisplays the page. This is manifesting in a number of forms including the actions comment and reply, when

Re: [rt-users] Upgraded 3.8.8 - 4.2.0, IE issues

2013-10-29 Thread Wright, Cory (CDC/OID/NCIRD) (CTR)
Tom -- I have also experienced this issue along with the previously communicated broken email issues, both of which are blocking a 4.2.0 upgrade in our environment. No resolution on either, yet. - Cory -Original Message- From: rt-users-boun...@lists.bestpractical.com

Re: [rt-users] Upgraded 3.8.8 - 4.2.0, IE issues

2013-10-29 Thread Tyler Sweet
I was sent a patch for this at one point, and was told the fix is coming in 4.2.1. IIRC, the problem is in /opt/rt4/share/static/js/forms.js (or where ever you have RT installed at). I can't remember which line needs to change, but here's what mine looks like: jQuery(function() {

Re: [rt-users] Upgraded 3.8.8 - 4.2.0, IE issues

2013-10-29 Thread Tyler Sweet
Ah, sorry for the double-post. I found the message here: http://lists.bestpractical.com/pipermail/rt-users/2013-October/081725.html On 10/29/2013 at 3:58 PM, in message 526fdb3b022c0002b...@iris.cbe.com, Tyler Sweet tbsw...@cbecompanies.com wrote: I was sent a patch for this at one

Re: [rt-users] Upgraded 3.8.8 - 4.2.0, IE issues

2013-10-29 Thread Tom Lahti
On 10/29/2013 1:58 PM, Tyler Sweet wrote: I was sent a patch for this at one point, and was told the fix is coming in 4.2.1. IIRC, the problem is in /opt/rt4/share/static/js/forms.js (or where ever you have RT installed at). I can't remember which line needs to change, but here's what

Re: [rt-users] Upgrading 4.0.8 - 4.2.0 breaking outgoing email

2013-10-29 Thread Wright, Cory (CDC/OID/NCIRD) (CTR)
After some further troubleshooting I have determined that email from the upgraded 4.2.0 instance is in fact working (testing with dashboard subs), but that no scrips execute. The bulk of errors in my debug log are: [6973] [Tue Oct 29 21:24:15 2013] [warning]: DBD::mysql::st execute failed: