Rt-3.5.7 new install issues

Hello!

I wanted to check out the latest dev release of rt, to see how far along it
is, and generality evaluate its usability. ( I heard that it’s easier to
extend/customize due to more extensive use of css and whatnot )

Anyhow, I went through the install on two separate machines – and ran into
the same issue both times:

At the initial login screen, the bplogo.gif appears as a broken link ( no
image ), and below it displays the “RT for example.com” text – despite the
fact that I configured my RT_SiteConfig.pm appropriately ( or so I think? ).

I’ve been completely unable to determine/fathom what may be causing this ( I’m
still quite new to RT ); I’m hoping someone could throw me some clues?

( the installs were done on two separate gentoo linux boxes )

Many thanks!

Cheers,

Corey

Is there something different about the way rt 3.5 reads the RT_SiteConfig.pm?

I’ve been able to pinpoint at least one problem so far down to the fact that
it seems my RT_SiteConfig.pm isn’t being used by rt.

mysite etc # pwd
/var/www/support.mysite.org/rt-3.5.7/etc
mysite etc # ls -l RT_*.pm
-r-xr-x— 2 rt rt 18253 Feb 12 16:42 RT_Config.pm
-r-xr-x— 1 rt rt 72 Feb 12 16:43 RT_SiteConfig.pm
mysite etc # cat RT_SiteConfig.pm
package RT;

Set($rtname , “mysite.org”);

Set($DevelMode, ‘1’);

1;
mysite etc #
mysite etc # grep rtname RT_Config.pm
Set($rtname , “example.com”);

Despite what I’ve change in RT_SiteConfig.pm; RT is still setting $rtname to
what’s RT_Config.pm, i.e. example.com rather than mysite.org.

Is there something I’m missing or doing wrong? Has behavior changed?

Thanks,

CoreyOn Sunday February 12 2006 2:24 pm, Corey wrote:

Hello!

I wanted to check out the latest dev release of rt, to see how far along it
is, and generality evaluate its usability. ( I heard that it’s easier to
extend/customize due to more extensive use of css and whatnot )

Anyhow, I went through the install on two separate machines – and ran into
the same issue both times:

At the initial login screen, the bplogo.gif appears as a broken link ( no
image ), and below it displays the “RT for example.com” text – despite the
fact that I configured my RT_SiteConfig.pm appropriately ( or so I think?
).

I’ve been completely unable to determine/fathom what may be causing this (
I’m still quite new to RT ); I’m hoping someone could throw me some clues?

( the installs were done on two separate gentoo linux boxes )

Many thanks!

Cheers,

Corey


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Be sure to check out the RT Wiki at http://wiki.bestpractical.com

Download a free sample chapter of RT Essentials from O’Reilly Media at
http://rtbook.bestpractical.com

WE’RE COMING TO YOUR TOWN SOON - RT Training in Amsterdam, Boston and
San Francisco - Find out more at
http://bestpractical.com/services/training.html

Corey wrote:

Is there something different about the way rt 3.5 reads the RT_SiteConfig.pm?

You have probably already tried this but, have you restarted or stopped
and started apache?

Tracy Phillips
Rackeasy.com
370 South Lowe Ave.
Suite A-105
Cookeville, TN 38501

Tel: 1-800-596-0906
Tel: 1-404-704-0457 ext 1001
Fax: 1-775-205-0590

Corey wrote:

Is there something different about the way rt 3.5 reads the
RT_SiteConfig.pm?

You have probably already tried this but, have you restarted or stopped
and started apache?

Hi!

Thanks for the response - but yep, I had tried restarting apache several
times, among quite a few other things.

However, looks like the issue turned out to be with the gentoo ebuild I was
using – I had modified the known working 3.4.5 ebuild, so that it would
build/install/configure 3.5.7. It appeared to have… “mostly worked”.

When I tried doing a fresh install using the vanilla rt-3.5.7.tar.gz, I was
able to confirm that everything worked as expected - aside from that
secondary issue with the images ( like the bplogo.gif ) still not working;
which, I later figured out was due to an apparent problem with the
autohandler that’s in …/NoAuth/images/ - when I removed it, the images
showed up just fine.

Cheers,

Corey