Re:Newbie needs help

[FrankMoehle]

Hi,

I had a similar problem when movin or old gnats/gnatsweb to a newly comfigured computer.
I think the problem is gnatsweb.pl. It is very sensitive to the version of the CGI.pm perl module.
First i had similar, broken url's, but after we reverted to CGI.pm version 2.68, everything was fine again.

Actually, you can also try to set the -oldstyle_urls pragma of the CPI module.
- open gnatsweb.pl
- change the parameters of the second "use cgi" statemanet to "use CGI 2.56 qw/-oldstyle_urls -nosticky/;"
afterwards, the  whole block looks similar to this:

# end customization
#-----------------------------------------------------------------------------

# Use CGI::Carp first, so that fatal errors come to the browser, including
# those caused by old versions of CGI.pm.
#use CGI::Carp qw/fatalsToBrowser/;
use CGI::Carp qw(fatalsToBrowser);
# 8/22/99 kenstir: CGI.pm-2.50's file upload is broken.
# 9/19/99 kenstir: CGI.pm-2.55's file upload is broken.
use CGI 2.56 qw/-oldstyle_urls -nosticky -no_xhtml/;

The gnatsweb README says:

    * Perl 5, with the fine CGI.pm module, version 2.56 or newer.
      Note that the unofficial 3.x versions of CGI.pm have been
      reported not to work. There has been trouble reported with a
      version of perl prior to 5.004_04.

best wishes,

Frank.

I noticed on your website that your top menu button URLS are functional.
  

Date: Tue, 06 Nov 2007 16:16:50 -0600
From: Chad Walstrom chewie@...
Subject: Re: Newbie needs help 
To: dwinner@...
Cc: help-gnats@...
Message-ID: 26940.1194387410@...

Wow, that's one crazy URL.  Not sure what's going on there.  You're
welcome to a copy of my local site configuration pl file.  I'll try to
get it to you later tonight.

Chad

_______________________________________________
Help-gnats mailing list
Help-gnats@...
http://lists.gnu.org/mailman/listinfo/help-gnats

[Duane Winner-2]

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
Help-gnats@...
http://lists.gnu.org/mailman/listinfo/help-gnats

[LLoyd Bailey-2]

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: help-gnats-bounces+joseph=swi.com@...
[mailto:help-gnats-bounces+joseph=swi.com@...]On Behalf Of Duane
Winner
Sent: Friday, November 09, 2007 7:55 AM
To: help-gnats@...
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
Help-gnats@...
http://lists.gnu.org/mailman/listinfo/help-gnats



_______________________________________________
Help-gnats mailing list
Help-gnats@...
http://lists.gnu.org/mailman/listinfo/help-gnats