We installed RT 2.0.11, and after working out some version conflict
glitches between apache and perl everything seems to be working, except
that sometimes the stylesheet doesn’t seem to “take” and the styles of
links etc. revert to defaults. A few hits of the reload button usually
cures this, but not permanently. We see this with both Netscape 4.77 and
Konqueror 2.1.1 so I don’t think this is a browser problem per se.
This is a pretty minor cosmetic flaw, but I’m wondering if anyone else
has seen anything like it, and if there might be a fix. We have been
very pleased with the RT software otherwise; it’s really quite good.
I have had problems with Mozilla .9.6 - .9.9 not seeing some images and
stylesheets properly, if I did not COMPLETELY remove the previous version
before installing the update.
Most recently, moving from .9.8 to .9.9, I had to remove the (I use NT)
mozilla directory from the application data directory in my profile (that’s
an NT profile, mind you). Now that I have I nuked both the Mozilla
directory in Program Files and the App Data directory, everything is working
as expected.
In previous upgrades, I was able to keep the Aplication Data directory
without ill effect.
We installed RT 2.0.11, and after working out some version conflict
glitches between apache and perl everything seems to be working, except
that sometimes the stylesheet doesn’t seem to “take” and the styles of
links etc. revert to defaults. A few hits of the reload button usually
cures this, but not permanently. We see this with both Netscape 4.77 and
Konqueror 2.1.1 so I don’t think this is a browser problem per se.
This is a pretty minor cosmetic flaw, but I’m wondering if anyone else
has seen anything like it, and if there might be a fix. We have been
very pleased with the RT software otherwise; it’s really quite good.
We installed RT 2.0.11, and after working out some version conflict
glitches between apache and perl everything seems to be working, except
that sometimes the stylesheet doesn’t seem to “take” and the styles of
links etc. revert to defaults. A few hits of the reload button usually
cures this, but not permanently. We see this with both Netscape 4.77 and
Konqueror 2.1.1 so I don’t think this is a browser problem per se.
This is a pretty minor cosmetic flaw, but I’m wondering if anyone else
has seen anything like it, and if there might be a fix. We have been
very pleased with the RT software otherwise; it’s really quite good.
I haven’t run those two apps but I can report that Mozilla-0.9.8 had
issues when you submit a resolve. I upgraded to 0.9.9 and the issue is
gone. Try Mozilla
-Wash
Odhiambo Washington wash@wananchi.com “The box said ‘Requires
Wananchi Online Ltd. www.wananchi.com Windows 95, NT, or better,’
Tel: 254 2 313985-9 Fax: 254 2 313922 so I installed FreeBSD.”
GSM: 254 72 743 223 GSM: 254 733 744 121 This sig is McQ!
Advice to young men: Be ascetic, and if you can’t be ascetic,
then at least be asceptic.
AD> We installed RT 2.0.11, and after working out some version conflict
AD> glitches between apache and perl everything seems to be working, except
AD> that sometimes the stylesheet doesn’t seem to “take” and the styles of
Check for core dumps or other errors in your apache log file when this
happens.
We installed RT 2.0.11, and after working out some version conflict
glitches between apache and perl everything seems to be working, except
that sometimes the stylesheet doesn’t seem to “take” and the styles of
links etc. revert to defaults. A few hits of the reload button usually
cures this, but not permanently. We see this with both Netscape 4.77 and
Konqueror 2.1.1 so I don’t think this is a browser problem per se.
My installation displays similar problems. We are using Apache, RT’s
“external” authentication and authenticate against a Kerberos server.
The Apache error log will show you what’s going on.
For us, this happens because the stylesheet and the RT logo image that
are included in every web page are retrieved and authenticated
separately for every request. Since the Kerberos server sees these
requests in a very short time, it occasionally rejects some of them
because it suspects a replay attack.
This is a pretty minor cosmetic flaw, but I’m wondering if anyone else
has seen anything like it, and if there might be a fix. We have been
very pleased with the RT software otherwise; it’s really quite good.
I haven’t found a way of telling Apache not to authenticate the stuff in
the NoAuth section except taking an approach similar to the recommended
fastcgi setup. You would set up two virtual hosts where one serves the
NoAuth data.
Unfortunately, that requires to replace all references to NoAuth in the
RT source code by a configurable URL. It’s probably just a couple of
minutes of work, but I haven’t found the time to do that and submit a
patch. Here’s how the Apache setup could look like:
