[rt-users] convert Mason HTML into PDF

2011-04-14 Thread Wolfram Huettermann

Hi RT-users,

I have a Mason HTML file like foo.html?id=777 (URL parameter id is 
necessary!) and want to convert it to a pdf-file by clicking on a 
Submit-Button. This button can have the name Print. The code in the 
init-scope is supposed to look like that:


%INIT
#  Code  that unnecessary for the problem.
if ($ARGS{Primt})
{
  use PrintModule;
  # print this  file to bar.pdf
}

/%INIT

Thanks in advance,


Wolfram


Re: [rt-users] RT-Authen-ExternalAuth-0.08 which packages i need for

2011-04-14 Thread john s.

Hello Luis

First of all many thanks for you help 

I have set my ldap configuration in this way which you have described,
but there are still coming some error messages in relation to the apache2
log file:

cutout apache.log:
Couldn't load RT config file RT_SiteConfig.pm:\n\nsyntax error at
/opt/rt3/etc/RT_SiteConfig.pm line 146, near 'EmailAddress'\nCompilation
failed in require at /opt/rt3/bin/../lib/RT/Config.pm line 562.\nCompilation
failed in require at (eval 2) line 1.\n


Similar errors comes if try to activate the following command lines:

'tls'=  0,
ssl_version'  =  3,
'net_ldap_args' = [version =  3   ],
'group'  =  'User',
'group'  =  'GROUP_NAME',
'attr_match_list'   = ['Name',
  #   'EmailAddress',   ],
# 'attr_map'   
=  {   'Name' = 'sAMAccountName',

  
#'EmailAddress' = 'mail',
  # 'Organization' = #
'Organization' = 'physicalDeliveryOfficeName',

  
# 'RealName' = 'cn',


# 'ExternalAuthId' = 'sAMAccountName',

  
# 'Gecos' = 'sAMAccountName',

  
# 'WorkPhone' = 'telephoneNumber',

  
# 'Address1' = 'streetAddress',

  
# 'City' = 'l',

  
# 'State' = 'st',

  
# 'Zip' = 'postalCode',

  
# 'Country' = 'co'

   
}
}


);







So i had to comment out some  command lines   in order to determine whats
going wrong and the the apache server will runing fine  :

Her is my new config:


#RT Authenth#

Set($ExternalAuthPriority,  [ ' My_LDAP' ]);
Set($ExternalInfoPriority,  ['My_LDAP']);
Set($ExternalServiceUsesSSLorTLS,   0 );
Set($AutoCreateNonExternalUsers,0);


Set($ExternalSettings, {'My_LDAP' = {   ## GENERIC SECTION
# The type of service 
(db/ldap/cookie) 
  'type' = 'ldap',
# The server hosting
the service
'server' = 
'192.168.23.40',
## SERVICE-SPECIFIC
SECTION
# If you can bind to
your LDAP server anonymously you should 
# remove the user
and pass config lines, otherwise specify them here:
# 
# The username RT
should use to connect to the LDAP server 
'user' = 'USER',
# The password RT
should use to connect to the LDAP server
'pass' = 
'password',
#
# The LDAP search
base
'base' =  'ou= 
Unit,dc=s***,dc=local',
#
# ALL FILTERS MUST
BE VALID LDAP FILTERS ENCASED IN PARENTHESES!
# YOU **MUST**
SPECIFY A filter AND A d_filter!!
#
# The filter to use
to match RT-Users
'filter'  = 
'(ObjectClass=*)',
# A catch-all
example filter: '(objectClass=*)'
#
# The filter that
will only match disabled users
'd_filter' = 
'(userAccountControl=514)'
   

[rt-users] RT 3.8.9 + PostgreSQL 8.4.7 - missing/bad indexes

2011-04-14 Thread Václav Ovsík
Hi,
because of horrible performance of spreadsheet export of tickets I found
some badly created or missing indexes. I didn't investigate if other
RDBMS schemas has the same problem.
To discover problems I rewrote Results.tsv into command-line shape and
run it with DBI_TRACE=2 finally. 

For every row of Tickets the following additional problematic queries are
executed:



SELECT  * FROM Groups WHERE Instance = ? AND LOWER(Domain) = LOWER(?) AND 
LOWER(Type) = LOWER(?)

e.g. one my bind params: 106431 'RT::Ticket-Role' 'Requestor'

rt=# EXPLAIN ANALYZE SELECT * FROM Groups WHERE Instance = 106431 AND 
LOWER(Domain) = LOWER('RT::Ticket-Role') AND LOWER(Type) = LOWER('Requestor');
 QUERY PLAN 
 
-
 Seq Scan on groups  (cost=0.00..12925.34 rows=1 width=66) (actual 
time=64.672..64.904 rows=1 loops=1)
   Filter: ((instance = 106431) AND (lower((domain)::text) = 
'rt::ticket-role'::text) AND (lower((type)::text) = 'requestor'::text))
 Total runtime: 64.936 ms
(3 rows)

Existing indexes:
CREATE UNIQUE INDEX Groups1 ON Groups (Domain,Instance,Type,id, Name);
CREATE INDEX Groups2 On Groups (Type, Instance, Domain);

Both indexes above are case sensitive. Either problematic query should be
case sensitive (without lower()) or a new index with lower() on fields should
be created:

CREATE INDEX Groups_zito1 ON Groups (lower(Type), Instance, lower(Domain));

rt=# EXPLAIN ANALYZE SELECT * FROM Groups WHERE Instance = 106431 AND 
LOWER(Domain) = LOWER('RT::Ticket-Role') AND LOWER(Type) = LOWER('Requestor');
   QUERY PLAN   
 
-
 Index Scan using groups_zito1 on groups  (cost=0.01..8.38 rows=1 width=66) 
(actual time=0.084..0.084 rows=1 loops=1)
   Index Cond: ((lower((type)::text) = 'requestor'::text) AND (instance = 
106431) AND (lower((domain)::text) = 'rt::ticket-role'::text))
 Total runtime: 0.108 ms
(3 rows)




SELECT main.* FROM ObjectCustomFieldValues main  WHERE (main.Disabled = '0') 
AND (main.ObjectType = 'RT::Ticket') AND (main.ObjectId = '106431')

rt=# EXPLAIN ANALYZE SELECT main.* FROM ObjectCustomFieldValues main  WHERE 
(main.Disabled = '0') AND (main.ObjectType = 'RT::Ticket') AND (main.ObjectId = 
'106431');
   QUERY PLAN   


 Seq Scan on objectcustomfieldvalues main  (cost=0.00..12298.75 rows=3 
width=457) (actual time=142.497..142.887 rows=3 loops=1)
   Filter: ((disabled = 0) AND ((objecttype)::text = 'RT::Ticket'::text) AND 
(objectid = 106431))
 Total runtime: 142.924 ms
(3 rows)

Existing indexes:
CREATE INDEX ObjectCustomFieldValues1 ON ObjectCustomFieldValues 
(CustomField,ObjectType,ObjectId,Content);
CREATE INDEX ObjectCustomFieldValues2 ON ObjectCustomFieldValues 
(CustomField,ObjectType,ObjectId);

The above query selects based on fields ObjectType and ObjectId,
unfortunately ObjectCustomFieldValues2 contains additional field
CustomField. To speedup the search index with good selectivity
with only field ObjectId can suffice.

CREATE INDEX ObjectCustomFieldValues_zito1 ON ObjectCustomFieldValues 
(ObjectId);

rt=# EXPLAIN ANALYZE SELECT main.* FROM ObjectCustomFieldValues main  WHERE 
(main.Disabled = '0') AND (main.ObjectType = 'RT::Ticket') AND (main.ObjectId = 
'106431');
  QUERY 
PLAN  
--
 Index Scan using objectcustomfieldvalues_zito1 on objectcustomfieldvalues main 
 (cost=0.00..8.58 rows=3 width=457) (actual time=0.059..0.063 rows=3 loops=1)
   Index Cond: (objectid = 106431)
   Filter: ((disabled = 0) AND ((objecttype)::text = 'RT::Ticket'::text))
 Total runtime: 0.090 ms
(4 rows)

or index with two corresponding fields:
CREATE INDEX ObjectCustomFieldValues_zito2 ON ObjectCustomFieldValues 
(ObjectType, ObjectId);
My planner uses always objectcustomfieldvalues_zito1, because I have
only one ObjectType value:

rt=# select distinct objecttype from objectcustomfieldvalues;
 objecttype 

 RT::Ticket
(1 

Re: [rt-users] RT under Windows

2011-04-14 Thread Robert Grasso
Our mail server is Postfix on Linux CentOS, so I cannot comment here - besides, 
almost all our users desktops are under Windows - I
have RT authentications performed with AD through RT-Authen-ExternalAuth (RT 
extension), this is the main adaptation to the Windows
side I can advertise. Until you install the whole RT software (along with the 
database) onto a single server, it is a pretty
independent software (remote access through a normal Web browser, no specific 
client)

You may be concerned by the database backup. As we are a small company, I just 
have a full+incremental OS image performed each night
by Acronis backup (which briefly stops MySql before the backup), with a short 
history, dumped onto an external hard disk. So the
database backup is a part of the whole OS backup - I agree, this is not a 
wonderful solution, but well ...

The Acronis choice has been made as part of our disaster recovery plan : I am 
the only Linux sysadmin here; in case of emergency, my
Windows sysadmin must be able to restore our RT server; and the Acronis 
software has a pretty windowish GUI - this is not a free ad
! I would have preferred Mondoarchive !!! but Mondoarchive is poorly compliant 
with my Windows sysadmin (no pretty and
Windows-as-usual GUI), especially if we consider possible stressfull emergency 
situations, when one must work quickly and without
errors ...

---
Robert GRASSO – System engineer

CEDRAT S.A.
15 Chemin de Malacher - Inovallée - 38246 MEYLAN cedex - FRANCE 
Phone: +33 (0)4 76 90 50 45 - Fax: +33 (0)4 56 38 08 30
mailto:robert.gra...@cedrat.com - http://www.cedrat.com  

 -Message d'origine-
 De : rt-users-boun...@lists.bestpractical.com 
 [mailto:rt-users-boun...@lists.bestpractical.com] De la part 
 de Yan Seiner
 Envoyé : 13 avril 2011 21:41
 À : rt-users@lists.bestpractical.com
 Objet : Re: [rt-users] RT under Windows
 
 
 On Wed, April 13, 2011 12:29 pm, Thomas Sibley wrote:
  On 04/13/2011 02:56 PM, Yan Seiner wrote:
  I've talking to our IT folks about running RT for work 
 order tracking.
  They're not opposed to a linux box per se, but currently 
 they're 100% MS
  Windows.  At least one of their folks has linux experience.
 
  Can anyone offer any insight into integrating an RT 
 installation into an
  MS shop?
 
  Windows is not a supported platform for RT.
 
  If you're looking to do auth against AD, you can do that 
 with mod_kerb
  and the $WebExternalAuth configuration, or by using the
  RT-Authen-ExternalAuth plugin for RT.
 
 Sorry, I mis-titled that.  I'm asking for advice on 
 integrating RT on a
 linux platform into an otherwise 100% microsoft shop.  
 Authentication is
 just one small part of it; email integration, and any other 
 issues I can
 relay to the IT folks would help.
 
 -- 
 If you have eight hours to chop down a tree
 spend six sharpening your axe.
 --Abraham Lincoln
 



[rt-users] Changing ticket owner

2011-04-14 Thread Houcem HACHICHA
Hi. I read from RT's wiki that some rights are needed for an RT user to
change the owner of a ticket (ownTicket, modifyTicket, etc). However, unless
I grant the SuperUser right, RT doesn't let my users change a ticket's
owner.
I have tried to grant all rights but SuperUser to a user and still nothing.

Any idea how to solve this?
Thanks in advance

-- 
*Regads,
Houcem*


[rt-users] [Rt-announce] Security vulnerabilities in RT

2011-04-14 Thread Alex Vandiver
In the process of preparing the release of RT 4.0.0, we performed an
extensive security audit of RT's source code.  During this audit,
several vulnerabilities were found which affect earlier releases of RT.
We are releasing versions 3.6.11, 3.8.10, and 4.0.0rc8 to resolve these
vulnerabilities, as well as patches which apply atop 3.6.10 and all
versions of RT 3.8.

RT versions 3.8.0 and above with the external custom field feature
enabled and configured are vulnerable to a remote code execution
vulnerability.  An authenticated user (either privileged or
unprivileged) can use this vulnerability to execute arbitrary code with
the permissions of the webserver; they may also be tricked into doing so
via cross-site request forgery (CSRF).  The external custom field option
is disabled by default; if you have not explicitly enabled
CustomFieldValuesSources in your RT configuration, your RT instance is
not vulnerable.  We have been assigned CVE-2011-1685 for this
vulnerability.

RT versions 2.0.0 and above are vulnerable to multiple SQL injection
attacks.  We do not believe these attacks to be capable of directly
inserting, altering or removing data from the database, but an
authenticated user (either privileged or unprivileged) could use them to
retrieve unauthorized ticket data.  Deployments since 3.6.0 are
additionally vulnerable to a more complex attack, which can be used by a
privileged user to retrieve arbitrary data from the database.  We have
been assigned CVE-2011-1686 for this vulnerability.

RT versions 3.0.0 and higher are vulnerable to an information leak
wherein an authenticated privileged user could gain sensitive
information, such as encrypted passwords, via the search interface.  We
have been assigned CVE-2011-1687 for this vulnerability.  This
vulnerability is particularly notable given RT's previous vulnerability
with insecure hashing (CVE-2011-0009).

RT versions 3.6.0 through 3.8.7, as well as 3.8.8 to a more limited
degree, are vulnerable to a malicious attacker tricking the user into
sending their authentication credentials to a third-party server.  We
have been assigned CVE-2011-1690 for this vulnerability.

RT versions 3.2.0 and above are vulnerable to a directory traversal
attack where an unauthenticated attacker can read any file which is
readable by the webserver.  While some servers (Apache, nginx) have
safeguards which mitigate this attack, preventing such traversals from
accessing files outside of RT's document root, many others (including
the standalone server provided with RT, plackup, starman, twiggy, and
lighttpd) are vulnerable to this exploit.  We have been assigned
CVE-2011-1688 for this vulnerability.

RT versions 2.0.0 and above are vulnerable to javascript
cross-site-scripting vulnerabilities, which allow an attacker to run
javascript with the user's credentials.  We have been assigned
CVE-2011-1689 for this vulnerability.


In addition to releasing RT versions 3.6.11, 3.8.10, and 4.0.0rc8, we
have collected patches for 3.6.10 and all releases of 3.8 into a
distribution available for download at this link:

http://download.bestpractical.com/pub/rt/release/security-2011-04-14.tar.gz
http://download.bestpractical.com/pub/rt/release/security-2011-04-14.tar.gz.sig

7d09b1315785a90d915bdbc86da1a0c9bd017a03  security-2011-04-14.tar.gz
7898a45b15474641a0f9c381d0f6f58fb34afcc3  security-2011-04-14.tar.gz.sig

The README in the tarball contains instructions for applying the
patches.

If you need help resolving this issue locally, we will provide
discounted pricing for single-incident support.  Please contact us at
sa...@bestpractical.com for more information.

 - Alex



signature.asc
Description: This is a digitally signed message part
___
RT-Announce mailing list
rt-annou...@lists.bestpractical.com
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-announce


[rt-users] [Rt-announce] RT 3.8.10 Released - Security Release

2011-04-14 Thread Kevin Falcone
This release of RT contains important bugfixes.  You can download it from:

http://download.bestpractical.com/pub/rt/release/rt-3.8.10.tar.gz
http://download.bestpractical.com/pub/rt/release/rt-3.8.10.tar.gz.sig

SHA1 sums

98678a4ce4dbdfb13ceeeb88236d49bd0f5562c7  rt-3.8.10.tar.gz
8e228df450d0cdc255e3db725b5bdf302771c75d  rt-3.8.10.tar.gz.sig

This release, in addition to being a bugfix release, also resolves a
number of security vulnerabilities.  It resolves CVE-2011-1685,
CVE-2011-1686, CVE-2011-1687, CVE-2011-1688, CVE-2011-1689, and
CVE-2011-1690.

* Cleanups identified by perlcritic.
* Clear the system attribute cache to avoid 'sticky' attributes like
  the queue subject tag.
* Fix our signature escaping so we better match FCKEditor and don't
  misidentify signatures during processing.
* Add the ability to create BasedOn Custom Fields from intiialdata
* Provide a callback to affect the display format in admin pages
* Fix id prefixing on Custom Fields to be RTIR compatible
* Fix #16656 - Requestors with OwnTicket could show up in the owner list
  in other Queues.
* Don't attach the original multipart mail to notifications that already
  contain one part of it.
* Work around CGI.pm 3.51 and 3.52 which add ; charse=ISO-8859-1 to our
  utf-8 encoded javascript.


pgpqVoRc2tMty.pgp
Description: PGP signature
___
RT-Announce mailing list
rt-annou...@lists.bestpractical.com
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-announce


[rt-users] [Rt-announce] RT 3.6.11 Released - Security Release

2011-04-14 Thread Kevin Falcone
This is a security release of RT.  It resolves CVE-2011-1686,
CVE-2011-1687, CVE-2011-1688, CVE-2011-1689, and CVE-2011-1690.

You can download it here:

http://download.bestpractical.com/pub/rt/release/rt-3.6.11.tar.gz
http://download.bestpractical.com/pub/rt/release/rt-3.6.11.tar.gz.sig

SHA1 sums

5cd0143cae8f1400e8c82370f2626f9989b02673  rt-3.6.11.tar.gz
126daf79864c1a48ee743b43ff70c5cb4dda5141  rt-3.6.11.tar.gz.sig



pgpqTUD5OlePY.pgp
Description: PGP signature
___
RT-Announce mailing list
rt-annou...@lists.bestpractical.com
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-announce


Re: [rt-users] Changing ticket owner

2011-04-14 Thread Houcem HACHICHA
On Thu, Apr 14, 2011 at 2:49 PM, Houcem HACHICHA
houcem.hachi...@gmail.comwrote:

 Hi. I read from RT's wiki that some rights are needed for an RT user to
 change the owner of a ticket (ownTicket, modifyTicket, etc). However, unless
 I grant the SuperUser right, RT doesn't let my users change a ticket's
 owner.
 I have tried to grant all rights but SuperUser to a user and still nothing.


I want this non-superUser to be able to change ticket ownership to a
superUser. Is that possible with RT?


 Any idea how to solve this?
 Thanks in advance

 --
 *Regads,
 Houcem*







-- 
*Regads,
Houcem*


Re: [rt-users] [Rt-announce] Security vulnerabilities in RT

2011-04-14 Thread Alex Vandiver
On Thu, 2011-04-14 at 10:18 -0400, Murphy, Kevin wrote:
 Just to clarify: after applying the patch to 3.8.9, do I have 3.8.10?
 The page footer and system configuration page still say 3.8.9 and
 don't mention the patch.

No.  The security patchsets are a minimal set of security patches which
do not include the other bugfixes in 3.8.10.
 - Alex



Re: [rt-users] Changing ticket owner

2011-04-14 Thread Kevin Falcone
On Thu, Apr 14, 2011 at 02:49:44PM +0100, Houcem HACHICHA wrote:
Hi. I read from RT's wiki that some rights are needed for an RT user to 
 change the owner of a
ticket (ownTicket, modifyTicket, etc). However, unless I grant the 
 SuperUser right, RT doesn't
let my users change a ticket's owner.
I have tried to grant all rights but SuperUser to a user and still nothing.
Any idea how to solve this?

You can Take or Steal a ticket and then reassign it
You may need to grant those rights also.
SuperUser is not required to change an owner.

If this does not work, you need to explain what doesn't let and
still nothing mean.

-kevin


pgp9tHZlFxhKN.pgp
Description: PGP signature


Re: [rt-users] Changing ticket owner

2011-04-14 Thread Houcem HACHICHA
On Thu, Apr 14, 2011 at 5:10 PM, Kevin Falcone falc...@bestpractical.comwrote:

 On Thu, Apr 14, 2011 at 02:49:44PM +0100, Houcem HACHICHA wrote:
 Hi. I read from RT's wiki that some rights are needed for an RT user
 to change the owner of a
 ticket (ownTicket, modifyTicket, etc). However, unless I grant the
 SuperUser right, RT doesn't
 let my users change a ticket's owner.
 I have tried to grant all rights but SuperUser to a user and still
 nothing.
 Any idea how to solve this?

 You can Take or Steal a ticket and then reassign it
 You may need to grant those rights also.
 SuperUser is not required to change an owner.

 If this does not work, you need to explain what doesn't let and
 still nothing mean.


Thanks Kevin, I granted some additional permissions to my SuperUser and
it worked :)



 -kevin


-- 
*Regads,
Houcem*


Re: [rt-users] RT-Authen-ExternalAuth-0.08 which packages i need for

2011-04-14 Thread Luis Avendaño
 

 Hi John, 

apparently your problem is this: 

'attr_match_list' = [ 'Name',
 # 'EmailAddress', ],
 # 'attr_map' 
 = { 'Name' = 'sAMAccountName',
 ... 

You have to ensure formatting correctly the list. For example: 
'attr_match_list' = [ 'Name' ]... you are doing this: 'attr_match_list' =
[ 'Name', 

In addition, check also attr_map. For example: 

   
'attr_map'  =  {   'Name' =
'sAMAccountName', 

   
'EmailAddress' = 'mail', 

   
'RealName' = 'cn', 

 
  'WorkPhone'
= 'telephoneNumber' 

   
} 

The error you are getting is that the SiteConfig is not correctly formed. 

Hope this helps, 

Best,
 



 Luis Avendaño 
 Grupo Latinoamericano ACM 
 Av. Venezuela Torre America, 
 Piso 1 Ofic 116, Bello Monte. 
 Caracas, Venezuela 
 Phone: (+58) 212-763.4104 
 Fax: (+58) 212-763.1847 
 http://www.acmgrp.com 

  USO DE CORREO ELECTRÓNICO DE
ACM ** 

 Este mensaje puede contener información únicamente de interés para ACM
GROUP o sus negocios y es enviado solamente al destinatario designado, y
puede contener información privilegiada, patentada o privada. La copia,
distribución, revelación o cualquier uso de la información contenida en
este mensaje es permitida solo a personas autorizadas. Si ha recibido este
correo electrónico por error, por favor destruyalo y notifique
inmediatamente a webmas...@acmgrp.com o al remitente 

 ** ACM GROUP INTERNET E-MAIL USE
*** 

 This message may contain information solely of the interest of ACM or its
businesses and is delivered for the designated recipient only and may
containprivileged, proprietary, or otherwise privatetion. Copying,
distribution, disclosure or any use of the information contained in this
transmission is permitted only to authorized parties. If you have received
this e-mail by error, please destroy it and notify webmas...@acmgrp.com or
the sender immediately 

 
**


 

[rt-users] User read only

2011-04-14 Thread Leonardo Vidal
Hi everyone!

I'm using version 3.4.2.
I need to define a user who has permission to see some queues but not
to create/modify/comment on tickets from them.
Any help?

Thanks in advance!

Leonardo.


[rt-users] 3.8.10 problems with RT-Extension-SpawnLinkedTicketInQueue

2011-04-14 Thread Daniel De Marco
Hi,

I just updated to 3.8.10 and RT-Extension-SpawnLinkedTicketInQueue
stopped working. When I click on the Create button I get a 403
Forbidden page: You don't have permission to access
/Elements/SpawnLinkedTicket on this server.

Is there anything obvious I missed during the upgrade?
I checked the permissions on the disk and they are fine, but I don't
that's the real reason...

Thanks, Daniel.



Re: [rt-users] 3.8.10 problems with RT-Extension-SpawnLinkedTicketInQueue

2011-04-14 Thread Kevin Falcone
On Thu, Apr 14, 2011 at 03:39:54PM -0400, Daniel De Marco wrote:
 I just updated to 3.8.10 and RT-Extension-SpawnLinkedTicketInQueue
 stopped working. When I click on the Create button I get a 403
 Forbidden page: You don't have permission to access
 /Elements/SpawnLinkedTicket on this server.
 
 Is there anything obvious I missed during the upgrade?
 I checked the permissions on the disk and they are fine, but I don't
 that's the real reason...

As a security measure, RT now blocks access to code in /Elements
That extension will need an update

Can you file a bug for it on rt.cpan.org?  You should be able to
forward your email to bug-rt-extension-spawnlinkedticketinqueue at 
rt.cpan.org if I'm remembering the syntax correctly.

-kevin


pgpkF1lD2vw6s.pgp
Description: PGP signature


[rt-users] Ticket in default view

2011-04-14 Thread Albert Shih
Hi all

How can I define for every user the Rows per box of the RT at a glance.
The default is 10. I would like to put something like infinite or 1000.

Regards.

JAS
-- 
Albert SHIH
DIO batiment 15
Observatoire de Paris Meudon
5 Place Jules Janssen
92195 Meudon Cedex
Téléphone : 01 45 07 76 26/06 86 69 95 71
Heure local/Local time:
jeu 14 avr 2011 22:25:05 CEST


Re: [rt-users] Ticket in default view

2011-04-14 Thread Albert Shih
 Le 14/04/2011 à 22:33:28+0200, Albert Shih a écrit
 Hi all
 
 How can I define for every user the Rows per box of the RT at a glance.
 The default is 10. I would like to put something like infinite or 1000.

I find: 

Set($DefaultSummaryRows, 500);

in RT_SiteConfig

Thanks to myself ;-)

Sorry for the disturbance

Regards.

-- 
Albert SHIH
DIO batiment 15
Observatoire de Paris Meudon
5 Place Jules Janssen
92195 Meudon Cedex
Téléphone : 01 45 07 76 26/06 86 69 95 71
Heure local/Local time:
jeu 14 avr 2011 22:55:45 CEST


Re: [rt-users] 3.8.10 problems with RT-Extension-SpawnLinkedTicketInQueue

2011-04-14 Thread Daniel De Marco
Thank you for the prompt reply. I'll file the bug at rt.cpan.org .

Daniel.

* Kevin Falcone falc...@bestpractical.com [04/14/2011 15:53]:
 On Thu, Apr 14, 2011 at 03:39:54PM -0400, Daniel De Marco wrote:
  I just updated to 3.8.10 and RT-Extension-SpawnLinkedTicketInQueue
  stopped working. When I click on the Create button I get a 403
  Forbidden page: You don't have permission to access
  /Elements/SpawnLinkedTicket on this server.
  
  Is there anything obvious I missed during the upgrade?
  I checked the permissions on the disk and they are fine, but I don't
  that's the real reason...
 
 As a security measure, RT now blocks access to code in /Elements
 That extension will need an update
 
 Can you file a bug for it on rt.cpan.org?  You should be able to
 forward your email to bug-rt-extension-spawnlinkedticketinqueue at 
 rt.cpan.org if I'm remembering the syntax correctly.
 
 -kevin




[rt-users] issues w/ outbound email to specific addresses

2011-04-14 Thread Sullivan, Rob
RT3.8.9.

We use a 3rd party to handle phone queues and do monitoring of SNMP
analysis during off hours.  When this party needs to open a ticket in
one of several different queues their monitoring software (homebrewed)
sends an email to one of several sendmail aliases which use mailgate to
create tickets.  As the emails all come from the same system they have
the same return address, noc_st...@vendornoc.com (example).  The tickets
are created perfectly fine in all queues.  However RT sends outbound
email for new tickets to the reply address only in the General queue, in
other queues no outbound messages are generated.  If I test from various
other (non-vendor) email addresses this works fine in all queues, all
correspondence is sent as expected- this is only an issue for the
messages generated by the vendor's ticketing system.  Any idea what I'm
overlooking here?
Thanks,

Rob Sullivan
Systems Engineer, Peerless Network Inc
rsulli...@peerlessnetwork.com
312-506-0948




Re: [rt-users] RT 3.8.9 + PostgreSQL 8.4.7 - missing/bad indexes

2011-04-14 Thread Jesse Vincent



On Thu 14.Apr'11 at 15:26:33 +0200, Václav Ovsík wrote:
 Hi,
 because of horrible performance of spreadsheet export of tickets I found
 some badly created or missing indexes. I didn't investigate if other
 RDBMS schemas has the same problem.
 To discover problems I rewrote Results.tsv into command-line shape and
 run it with DBI_TRACE=2 finally. 
 
 For every row of Tickets the following additional problematic queries are
 executed:
 
 
 
 SELECT  * FROM Groups WHERE Instance = ? AND LOWER(Domain) = LOWER(?) AND 
 LOWER(Type) = LOWER(?)
 
 e.g. one my bind params: 106431 'RT::Ticket-Role' 'Requestor'
 
 rt=# EXPLAIN ANALYZE SELECT * FROM Groups WHERE Instance = 106431 AND 
 LOWER(Domain) = LOWER('RT::Ticket-Role') AND LOWER(Type) = LOWER('Requestor');
QUERY PLAN 
  

I'd actually consider this a code bug. We shouldn't be LOWER()ing either 
of those parameters.  Please open a ticket by mailing
rt-b...@bestpractical.com

Thanks!