Custom logo broken. Does share/html/NoAuth/images/autohandler do the right thing?

I have production (mod_perl) and development (standalone_httpd) RT instances.

The mod_perl instance is configured according to RT’s README but Mason
still tries to interpret the image.

Same thing happens in my standalone_httpd RT, even with the
autohandler. I think the default BP logo doesn’t have any bits that
can be mistaken as Mason markup.

This is with the inplace layout, though I’m not sure that matters.

Ideas?

Yeah, that’s true that mason tries to parse things even when there is
autohandler in the same or above dir. This happens as a comp may
define autohandler or drop all of them.

However, I do recall we did something about that in custom handler.On Wed, Feb 25, 2009 at 2:18 AM, Todd Chapman todd@chaka.net wrote:

I have production (mod_perl) and development (standalone_httpd) RT instances.

The mod_perl instance is configured according to RT’s README but Mason
still tries to interpret the image.

Same thing happens in my standalone_httpd RT, even with the
autohandler. I think the default BP logo doesn’t have any bits that
can be mistaken as Mason markup.

This is with the inplace layout, though I’m not sure that matters.

Ideas?


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

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Best regards, Ruslan.

I found one of the problems. The RT README says to configure mod_perl with this:

<Location /NoAuth/images>
    SetHandler default
</Location>
<Location />
    SetHandler perl-script
    PerlResponseHandler RT::Mason
</Location>

which didn’t work for me. When I changed the order to this it started working:

<Location />
    SetHandler perl-script
    PerlResponseHandler RT::Mason
</Location>
<Location /NoAuth/images>
    SetHandler default
</Location>On Wed, Feb 25, 2009 at 4:27 AM, Ruslan Zakirov <ruslan.zakirov@gmail.com> wrote:

Yeah, that’s true that mason tries to parse things even when there is
autohandler in the same or above dir. This happens as a comp may
define autohandler or drop all of them.

However, I do recall we did something about that in custom handler.

On Wed, Feb 25, 2009 at 2:18 AM, Todd Chapman todd@chaka.net wrote:

I have production (mod_perl) and development (standalone_httpd) RT instances.

The mod_perl instance is configured according to RT’s README but Mason
still tries to interpret the image.

Same thing happens in my standalone_httpd RT, even with the
autohandler. I think the default BP logo doesn’t have any bits that
can be mistaken as Mason markup.

This is with the inplace layout, though I’m not sure that matters.

Ideas?


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

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com


Best regards, Ruslan.