Changing the "Example.com" header

RT Users
1

Okay, this is a really stupid question, and I am amazed I cannot find it
anywhere.

When looking at the Queue for RT, basically the first page you see after
logging in, in the upper left it says:

RT for example.com

How do you change that example.com, a grep doesn’t reveal it and I cannot
find it in any of the RT3 tables.

I would assume this is in the preferneces or config somewhere, but am
apparently missing that as well.

Thanks,

Erik

2

See the RT config file in <install_dir>/etc/

3

Erik,

try the RT_SiteConfig.pm file… specifically the Set($rtname,
‘example.com’)

change example.com to whatever it is you like… the docs however say it is
preferred that you use your domain name to make it unique.
also, changing this when there are already live tickets tends to mess
things up becoz new updates to live tickets after the change tend to lose
their way in updating the correct ticket.

4

Paul,

This entry exists in the RT_Cnfig.pm, but not in RT_SiteConfig.pm, in fact
there is not even an entry in RT_SiteConfig.pm for the Set($rtname
parameter.

In the RT_Config.pm file it already lists what I want it to say, it just
doesn’t show up on the web interface nor in the autoreply emails to the
users, everything goes out as example.com.

Any ideas?

Thanks,

Erik

Erik,

try the RT_SiteConfig.pm file… specifically the Set($rtname,
‘example.com’)

change example.com to whatever it is you like… the docs however say it is
preferred that you use your domain name to make it unique.
also, changing this when there are already live tickets tends to mess
things up becoz new updates to live tickets after the change tend to lose
their way in updating the correct ticket.

5

You have to copy the content of RT_Config.pm into RT_SiteConfig.pm, the
you change the parameters.

When you web server starts, it reads only RT_SiteConfig. RT_Config is
only a backup of the original configuration.

Jean-Yan

Erik Boles wrote:

6

That’s not correct AFAIK
RT reads both files, and if it doesn’t found something in RT_SiteConfig.pm,
then it searches for this prarmeter in RT_Config.pm

-Dimitry-----Original Message-----
From: rt-users-bounces@lists.bestpractical.com
[mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Jean-Yan B駻
ub

When you web server starts, it reads only RT_SiteConfig. RT_Config is
only a backup of the original configuration.

7

This entry exists in the RT_Cnfig.pm, but not in RT_SiteConfig.pm, in fact
there is not even an entry in RT_SiteConfig.pm for the Set($rtname
parameter.

RT_SiteConfig.pm contains your changes to the system defaults. So it
won’t be there until you put it there.

RT_Config.pm is the system defaults and you do not want to change them.
All of your changes from system defaults, or site-specific configuration
should always go in RT_SiteConfig.pm. The RT_Config.pm file may get
whacked on upgrades so you would lose all of your customizations if you
add them there.

In the RT_Config.pm file it already lists what I want it to say, it just
doesn’t show up on the web interface nor in the autoreply emails to the
users, everything goes out as example.com.

Have you STOPPED and then STARTED Apache? Restarts don’t count.

8

On 5/11/04 4:12 PM, “bill@daze.net” bill@daze.net, emailed the following:

Have you STOPPED and then STARTED Apache? Restarts don’t count.

Thanks Bill. That was it, didn’t know restarts didn’t work…going to pick
up my app at McDonalds on the way home tonight…

Erik

9

Erik,

I’m using rt 3.0.10 via debian testing (sarge)… according to the docs
i read… there are options not explicitly listed in the
RT_SiteConfig.pm… in my experience the
Set($ParseNewMessageForTicketCcs , undef); option was not in there also
but i manually added it in.

its said in the /usr/share/doc/request-tracker3/INSTALL.Debian.gz file
that…

“Note that the default settings in RT_config.pm are used for any options
you do put into RT_SiteConfig.pm. You should NEVER edit the
RT_Config.pm file directly; always use the RT_SiteConfig.pm… I
recommend that you read /etc/request-tracker3/RT_Config.pm thoroughly
and copy/edit the extra bits you think you need into the
RT_SiteConfig.pm file”

in this case the extra bits that applies to you should probably be the
($rtname) parameter.

hope this helps.

Erik Boles wrote: