RE: Newbie needs help

Hi Duane,

I had the same URL problem after going into the create PR.

There is an issue with the CGI.pm file.

Here is a bug report for CGI.pm
(http://rt.cpan.org/Public/Bug/Display.html?id=24479)
dated Jan 21, 2007 which claims that _name_and_path_from_env has problems
with query strings
that contain "//".

The suggested fix to the CGI.pm is this:

Change:

sub _name_and_path_from_env {
    my $self = shift;
    my $raw_script_name = $ENV{SCRIPT_NAME} || '';
    my $raw_path_info   = $ENV{PATH_INFO}   || '';
    my $uri             = unescape($self->request_uri) || '';
    ...
To:

sub _name_and_path_from_env {
    my $self = shift;
    my $raw_script_name =  $ENV{SCRIPT_NAME}  || '';
    my $raw_path_info   =  $ENV{PATH_INFO}    || '';
    my $uri             =  $self->request_uri || '';
    $uri                =~ s/\?.*$//;
    $uri                =  unescape($uri)     || '';
    ...

============================

The substitution is trying to strip out everything after the first ?


Lloyd Bailey
Associate Technical Consultant
Systemware Innovation Corporation



-----Original Message-----
From: [email protected]
[mailto:[email protected]]On Behalf Of Duane
Winner
Sent: Friday, November 09, 2007 7:55 AM
To: [email protected]
Subject: Re: Newbie needs help


Thanks all for your help w/ the broken URLS. It seems like my main
problem was straying from a standard /cgi-bin/ ScriptAlias; when I
reinstalled the gnats port and redid Apache to just use /cgi-bin/
instead my goofy /gnatsbin/, all is well.



But now for something compeletely different.....

I'm hoping I didn't get too far into giving gnats my blessing for
production implementation without fully understanding the privileges
mechanism.

Here is what our site needs:

1) Our development team needs to be able to submit, query, edit and
manage gnats.

2) We want users (i.e. clients) to be able to log on and submit ONLY --
not see the progress of the tracking, other PR's, etc.

It seems I may have foolishly assumed without testing first that between
gnatsd.user_access and the submitters file that we could accomplish
this. But now that I'm trying to set this up, it appears that nobody can
log on unless they have an entry in gnatsd.user_access. However, I see
no way of limiting them to submit only in there. And now I'm finding
that the submitters file does not mean "submitters" as in "a user who
can submit."

Anybody using gnats in a similar fashion or know of a way to accomplish
these requirements?

Thanks!
DW


_______________________________________________
Help-gnats mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/help-gnats