List of all RT_SiteConfig.pm directives...?

Does anyone know of a list of all of the directives that one can put
inside of RT_SiteConfig.pm? It may be that my RTFM skills are weak,
but I can not find it anywhere. Specifically, I am looking for the
’Parse HTML’ Directive that Torsten Brumm posted in the “html
transaction appears to have no content, revisited” thread. But I do
want a complete list.

Thanks,
-B

Does anyone know of a list of all of the directives that one can put
inside of RT_SiteConfig.pm? It may be that my RTFM skills are weak,
but I can not find it anywhere. Specifically, I am looking for the
’Parse HTML’ Directive that Torsten Brumm posted in the “html
transaction appears to have no content, revisited” thread. But I do
want a complete list.

See RT_Config.pm!

-Todd

Hello!On Mon, 2005-12-12 at 16:38, Todd Chapman wrote:

On Mon, Dec 12, 2005 at 03:55:15PM -0800, Brian Benson wrote:

Does anyone know of a list of all of the directives that one can put
inside of RT_SiteConfig.pm? […]

See RT_Config.pm!

Mostly true, though I just learned about UseTransactionBatch today from
the wiki. So I guess the answer is mostly yes, but somewhat no. =\

Cheers!

–j
Jim Meyer, Geek at Large purp@acm.org

Hi Brian,

did a small mistake, sorry. The correct values:

if TrustHTMLAttachments is not defined, we will display them

as text. This prevents malicious HTML and javascript from being

sent in a request (although there is probably more to it than that)

Set($TrustHTMLAttachments , undef);

Torsten

Brian Benson schrieb:

I have a user set up in RT that we cannot seem to change their e-mail
address. It gives me an error saying Illegal Value.

Chris

“Chris Hale” chris-lists@pipelinewireless.us writes:

I have a user set up in RT that we cannot seem to change their e-mail
address. It gives me an error saying Illegal Value.

Probably there already exists an unprivileged user in RT with that
e-mail address. Locate that user (Configuration->Users->"Find people
whose email contains ") and change that user’s email address
to something else (junk@example.com, or whatever seems suitable). You
should then be able to change the address of the privileged user.

Leif Nixon - Systems expert
National Supercomputer Centre - Linkoping University