Using the Search button on the top nav-bar, RT 3.0.9 used to redirect
my browser to the Search interface. Now, RT 3.0.10 encapsulates the
request and serves it from the page I requested.
However, the redirected pages have a different base URL.
The consequences:
Search for a queue by name. The bulk update link is broken.
Search for a ticket by number. The Reply and Comment links that go
with each email are broken.
(My custom index.html broke too. Feh!)
It’s also broken in rt3.fsck.com.
FAEROES
SOUTHEASTERLY 5 OR 6 INCREASING 7, PERHAPS GALE 8 LATER. OCCASIONAL
RAIN. MODERATE
Using the Search button on the top nav-bar, RT 3.0.9 used to redirect
my browser to the Search interface. Now, RT 3.0.10 encapsulates the
request and serves it from the page I requested.
Right. Because the redirects were broken for folks on various strange
platforms.
However, the redirected pages have a different base URL.
The consequences:
Search for a queue by name. The bulk update link is broken.
K. That’s fixable.
Search for a ticket by number. The Reply and Comment links that go
with each email are broken.
Really? That’s something we explicitly fixed.
It’s also broken in rt3.fsck.com.
rt3.fsck.com is running a now-out-of-date snapshot of 3.1
PGP.sig (186 Bytes)
It’s also broken in rt3.fsck.com.
rt3.fsck.com is running a now-out-of-date snapshot of 3.1
Is rt3.fsck.com also good for us to check encoding problems? Is this machine running perl 5.8.3?
It is interesting for example for the error in quick search with strange characters.
Thanks
SAmuel
Quoting Jesse Vincent jesse@bestpractical.com (2004-04-01 16:57:07 BST):
Using the Search button on the top nav-bar, RT 3.0.9 used to redirect
my browser to the Search interface. Now, RT 3.0.10 encapsulates the
request and serves it from the page I requested.
Right. Because the redirects were broken for folks on various strange
platforms.
Fine 
However, the redirected pages have a different base URL.
The consequences:
Search for a queue by name. The bulk update link is broken.
K. That’s fixable.
Thanks.
Search for a ticket by number. The Reply and Comment links that go
with each email are broken.
Really? That’s something we explicitly fixed.
I attach the page I get back when I go to
http://wompom.dur.ac.uk/rt3/index.html?q=81
It shows that, for example, Reply =>
http://wompom.dur.ac.uk/rt3/Update.html?id=81&QuoteTransaction=1042&Action=Respond
This is a vanilla system – all my customisations are in a directory
which is chmod 000 right now.
It’s also broken in rt3.fsck.com.
rt3.fsck.com is running a now-out-of-date snapshot of 3.1
Heh, okay.
FITZROY
SOUTHWESTERLY BECOMING CYCLONIC 6 TO GALE 8, OCCASIONALLY SEVERE
GALE 9. THUNDERY SHOWERS. MODERATE OR GOOD
index.html (12.9 KB)
Search for a ticket by number. The Reply and Comment links that go
with each email are broken.
Really? That’s something we explicitly fixed.
I attach the page I get back when I go to
http://wompom.dur.ac.uk/rt3/index.html?q=81
It shows that, for example, Reply =>
http://wompom.dur.ac.uk/rt3/Update.html?
id=81&QuoteTransaction=1042&Action=Respond
Urgh. I agree with your diagnosis. Now to figure what happened to the
bloody patch. But, after some coffee.
Jesse
PGP.sig (186 Bytes)
Fine
However, the redirected pages have a different base URL.
The consequences:
Search for a queue by name. The bulk update link is broken.
K. That’s fixable.
And a bunch of other links on that page were broken too. Can you tell
me if the attached path makes this better?
Thanks.
Search for a ticket by number. The Reply and Comment links that go
with each email are broken.
Really? That’s something we explicitly fixed.
I attach the page I get back when I go to
http://wompom.dur.ac.uk/rt3/index.html?q=81
It shows that, for example, Reply =>
http://wompom.dur.ac.uk/rt3/Update.html?
id=81&QuoteTransaction=1042&Action=Respond
Can you test this again, after wiping the mason cache? On my clean
3.0.10 systems, I can’t replicate this.
baseurl.patch (1.56 KB)
Quoting Jesse Vincent jesse@bestpractical.com (2004-04-05 16:45:40 BST):
Fine
However, the redirected pages have a different base URL.
The consequences:
Search for a queue by name. The bulk update link is broken.
K. That’s fixable.
And a bunch of other links on that page were broken too. Can you tell
me if the attached path makes this better?
Yes, that’s great. Thanks.
Search for a ticket by number. The Reply and Comment links that go
with each email are broken.
Really? That’s something we explicitly fixed.
I attach the page I get back when I go to
http://wompom.dur.ac.uk/rt3/index.html?q=81
It shows that, for example, Reply =>
http://wompom.dur.ac.uk/rt3/Update.html?
id=81&QuoteTransaction=1042&Action=Respond
Can you test this again, after wiping the mason cache? On my clean
3.0.10 systems, I can’t replicate this.
Yes, it was the cache to blame. Stephen built 3.0.10 for Debian, then
after a couple of days’ continued 3.0.9 usage, I tried it out. Of
course, since the Mason cache works on timestamp, the cached version
was still newer than the built one.
I think our post-install script will have to do something like:
find -type f |xargs touch
Hugely ugly but it at least works. It’s better than ripping out the
cache directory because we can’t tell when the users are going to
re-start the web server.
SOLE LUNDY FASTNET
NORTHWEST VEERING NORTH 5 OR 6, OCCASIONALLY 7. SQUALLY SHOWERS.
GOOD
Hi,
How escalation work in RT. I want to build it if it is not there. Any
suggestion?
Cheers!!
Kuldeep Singh Tomar