RT3 speed (or lack thereof)

RT Users
1

Have you customised Search/Listing.html at all? There’s a line in it
around line 78 that starts:

<A HREF="<% $RT::WebPath%>/Search/Listing.html?

What does the rest of the line look like to you?

Here it is:

<&|/l&>Bookmarkable URL for this search</&>

2

Craig Schenk wrote:

<&|/l&>Bookmarkable URL for this
search</&>

OK, that definitely includes the bugfix Jesse and I have been
talking about. So something else is afoot.

Now, is the search failing in the same way for any text in
the address field? (In particular, does any particular char
in the input – such as the @ sign – trigger the bug?)

3

Now, is the search failing in the same way for any text in
the address field? (In particular, does any particular char
in the input – such as the @ sign – trigger the bug?)

Yes, any text, @ or no @.

4

pdh@bestpractical.com wrote:

Craig Schenk wrote:

<&|/l&>Bookmarkable URL for this
search</&>

OK, that definitely includes the bugfix Jesse and I have been
talking about. So something else is afoot.

Now, is the search failing in the same way for any text in
the address field? (In particular, does any particular char
in the input – such as the @ sign – trigger the bug?)

Just few minutes ago one my friend report that he also see such errorr
on any search. String isn’t unescaped when comes to FreezThaw.
He’s got 3.0.10, mod_perl, CGI-3.01.
Best regards. Ruslan.

5

Craig Schenk wrote:

Now, is the search failing in the same way for any text in
the address field? (In particular, does any particular char
in the input – such as the @ sign – trigger the bug?)

Yes, any text, @ or no @.

Patch attached

It’s against RT-3.0.10

Fix description:
RT shouldn’t unescape input field in forms, browser does it when send
form, but RT must escape HTML in values.

		Best regards. Ruslan.

FreezeThaw.patch (597 Bytes)

6

I seem to recall that this patch was new in 3.0.10 and actively fixed
peoples’ form submission problems. Dan, was it you?

JesseOn Sat, Apr 17, 2004 at 06:37:24PM +0400, Ruslan U. Zakirov wrote:

Craig Schenk wrote:

Now, is the search failing in the same way for any text in
the address field? (In particular, does any particular char
in the input – such as the @ sign – trigger the bug?)

Yes, any text, @ or no @.

Patch attached

It’s against RT-3.0.10

Fix description:
RT shouldn’t unescape input field in forms, browser does it when send
form, but RT must escape HTML in values.

  	Best regards. Ruslan.

RT-Users mailing list
RT-Users@lists.bestpractical.com
The rt-users Archives

RT-Users mailing list
RT-Users@lists.bestpractical.com
The rt-users Archives