RE: Problems getting a simple form to work.
It's OK, my feelings aren't hurt :)
On Fri, 2003-04-04 at 15:45, Hughes, Andrew wrote:
> I think you meant, "Thanks, Rob."
>
> Andrew
>
> -Original Message-
> From: Mike Butler [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 04, 2003 4:45 PM
> To: Rob Benton
> Cc: Hughes, Andrew; [EMAIL PROTECTED]
> Subject: RE: Problems getting a simple form to work.
>
>
> Thanks, Andrew. That did it. It's working now. :) :) :)
>
> Thanks everyone for all your help.
>
> - Mike
>
> -Original Message-
> From: Rob Benton [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 04, 2003 4:38 PM
> To: Mike Butler
> Cc: Hughes, Andrew; [EMAIL PROTECTED]
> Subject: RE: Problems getting a simple form to work.
>
>
> Give this a shot and see if it errors:
>
> use CGI;
> my $query = new CGI;
> my %params = $query->Vars;
>
> my $username = $params{'username'};
>
>
>
> On Fri, 2003-04-04 at 15:29, Mike Butler wrote:
> > Thanks, Andrew. I added CGI::Carp qw(fatalsToBrowser); to the script.
> That's
> > a big help. The error message that I get now is:
> > Software error:
> > Undefined subroutine &main::param called at simpleform.cgi line 6.
> >
> > Line 6 is my $username = param('username');
> >
> > Any idea why param is undefined?
> >
> > Thanks,
> >
> > - Mike
> >
> >
> > -Original Message-
> > From: Hughes, Andrew [mailto:[EMAIL PROTECTED]
> > Sent: Friday, April 04, 2003 3:09 PM
> > To: [EMAIL PROTECTED]
> > Subject: RE: Problems getting a simple form to work.
> >
> >
> > I would also add
> >
> > use CGI::Carp qw(fatalsToBrowser);
> >
> > along with
> >
> > use CGI;
> > use strict;
> >
> > This way your errors will get displayed in your browser.
> >
> > Also, check with your hosting company to make sure that your path to perl
> is
> > correct (ex. is it #!/usr/local/bin/perl -wT vs. #!/usr/bin/perl -wT)
> >
> > Andrew
> >
> > -Original Message-
> > From: Li Ngok Lam [mailto:[EMAIL PROTECTED]
> > Sent: Friday, April 04, 2003 2:37 PM
> > To: Mike Butler; [EMAIL PROTECTED]
> > Subject: Re: Problems getting a simple form to work.
> >
> >
> > [..]
> > > #!/usr/local/bin/perl -wT
> > > use CGI;
> > > use strict;
> > >
> > > $username = param('username');
> >
> > should be :
> > my $username = param('username');
> >
> > because you've using strict;
> >
> > >
> > > print "Content-type: text/plain\n\n";
> > For what I know, I would write as "Content-type: text/html\n\n";
> >
> > > print "You entered: $username\n";
> > >
> > > The permissions look like this:
> > >
> > > Permissions for cgi-bin: rwxr-xr-x
> > > Permissions for simpleform.cgi rwxr-xr-x
> > > Permissions for simpleform.htm: rwxr-xr-x
> > >
> > > I have changed to
> > > action="http://www.mikyo.com/cgi-bin/simpleform.cgi";>.
> > >
> >
> > 2 suggestion here :
> >
> > 1. use CGI::Carp 'fatalsToBrowser'; # the die message will goto your
> > browser.
> > 2. Try simpler script, so you will know if your form is going to a right
> > place :
> >
> > #!/usr/bin/perl
> > print "Content-type: text/html\n\n";
> > print "Hello world";
> >
> >
> >
> >
> >
> > --
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> > --
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> > --
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> --
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Problems getting a simple form to work.
Give this a shot and see if it errors:
use CGI;
my $query = new CGI;
my %params = $query->Vars;
my $username = $params{'username'};
On Fri, 2003-04-04 at 15:29, Mike Butler wrote:
> Thanks, Andrew. I added CGI::Carp qw(fatalsToBrowser); to the script. That's
> a big help. The error message that I get now is:
> Software error:
> Undefined subroutine &main::param called at simpleform.cgi line 6.
>
> Line 6 is my $username = param('username');
>
> Any idea why param is undefined?
>
> Thanks,
>
> - Mike
>
>
> -Original Message-
> From: Hughes, Andrew [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 04, 2003 3:09 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Problems getting a simple form to work.
>
>
> I would also add
>
> use CGI::Carp qw(fatalsToBrowser);
>
> along with
>
> use CGI;
> use strict;
>
> This way your errors will get displayed in your browser.
>
> Also, check with your hosting company to make sure that your path to perl is
> correct (ex. is it #!/usr/local/bin/perl -wT vs. #!/usr/bin/perl -wT)
>
> Andrew
>
> -Original Message-
> From: Li Ngok Lam [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 04, 2003 2:37 PM
> To: Mike Butler; [EMAIL PROTECTED]
> Subject: Re: Problems getting a simple form to work.
>
>
> [..]
> > #!/usr/local/bin/perl -wT
> > use CGI;
> > use strict;
> >
> > $username = param('username');
>
> should be :
> my $username = param('username');
>
> because you've using strict;
>
> >
> > print "Content-type: text/plain\n\n";
> For what I know, I would write as "Content-type: text/html\n\n";
>
> > print "You entered: $username\n";
> >
> > The permissions look like this:
> >
> > Permissions for cgi-bin: rwxr-xr-x
> > Permissions for simpleform.cgi rwxr-xr-x
> > Permissions for simpleform.htm: rwxr-xr-x
> >
> > I have changed to
> > http://www.mikyo.com/cgi-bin/simpleform.cgi";>.
> >
>
> 2 suggestion here :
>
> 1. use CGI::Carp 'fatalsToBrowser'; # the die message will goto your
> browser.
> 2. Try simpler script, so you will know if your form is going to a right
> place :
>
> #!/usr/bin/perl
> print "Content-type: text/html\n\n";
> print "Hello world";
>
>
>
>
>
> --
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
> --
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> --
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with regular expressions!!!
How does it translate? * = 0 or more of preceding char ? = 1 or 0 of preceding char *? = ??? On Tue, 2003-03-18 at 21:41, Michael Kelly wrote: > On Tue, Mar 18, 2003 at 05:53:45PM -0600, Rob Benton wrote: > > It looks odd to me b/c * and ? are both quantifiers... > > * and ? alone are both quantifiers, but *? is a non-greedy *. > > -- > Michael > [EMAIL PROTECTED] > http://www.jedimike.net/ > > -- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with regular expressions!!!
It looks odd to me b/c * and ? are both quantifiers which usually
triggers an error when you try to run it. See if this works for you:
$file_completename =~ /([^.]*)\.(.*)/;
On Tue, 2003-03-18 at 15:28, Marcelo Taube wrote:
> As u probably have guessed some part of my code is not working properly and
> i don't understand why!!
>
> This is the code.
> #
> $file_completename =~ /(.*?)\.(.*)/;
> if ($2 eq $extension]) {
> #DO SOMETHING!!!
> }
> #
> As u see, i'm trying to separate the complete name of a file in two parts,
> the filename ($1) and the extension($2)... then i check to see whatever a
> extension is of some kind and if it is, i do something.
> However this doesn't work. Because in $2, perl adds a "." before the
> extension.
> 4 example: if file_completename equal to "myfile.jpeg", then $2 equials to
> ".jpeg", but it should be "jpeg".
> What am i doing wrong?
> Thank u very much,
> Marcelo Taube
>
>
>
> _
> The new MSN 8: advanced junk mail protection and 2 months FREE*
> http://join.msn.com/?page=features/junkmail
>
>
> --
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
passing cgi params
If I use: my $query = new CGI; my %params = $query->Vars; to grab the incoming parameters is it safe to just send all of them over to a new cgi script like this: my $form = CGI::FormBuilder->new( fields => \%params, method => 'POST'); print $form->render(); Or will that pass along built-in parameters that should be? -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
CGI::FormBuilder
Is there a way to print a 'button' input type without a label next to it using the FormBuilder object? I can't find the right combination. I always wind up with this +---+ Next |Next | +---+ and what I want is +---+ |Next | +---+ $form->field(name => 'next', value => 'Next', label => 0) is all I could think of to try but that doesn't work. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: html table limit
Scroll up and down to the bottom of the page then see if the borders screw up. On Wed, 2003-03-12 at 14:57, Bob Showalter wrote: > Rob Benton wrote: > > Mozilla, Konqueror, Opera, and IE all act the same way. Check out this > > page to see what I mean. The top, bottom, and right side of the > > table borders act funky: > > > > http://www.geocities.com/emperorrob/test.html > > Hmm, this page displays fine for me in IE6. > > > > > I tried the validator but it keeps timing out. :) I guess the file > > is too big. > > I was able to run the validator. The only problem is you're missing a > section and some complaints about the junk yahoo adds on. No > problem with the table. > > -- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: html table limit
1000+ rows is a rare situation on my page but in can happen. It's a dbi script. I couldn't really think of a better design but I am open to suggestions... On Wed, 2003-03-12 at 15:07, Brett W. McCoy wrote: > On 12 Mar 2003, Rob Benton wrote: > > > > > Is there a limit to how many rows you can put in an html table? I > > > > can't find anything wrong with my script but when I get over 1000 > > > > rows or so in my tables they start drawing weird borders. > > I think if you are needing tables on an HTML page that have over a 1000 > rows you might want to redesign your UI. Just IMHO, of course. :-D > > -- Brett > http://www.chapelperilous.net/ > > I have never understood the female capacity to avoid a direct answer to > any question. > -- Spock, "This Side of Paradise", stardate 3417.3 > > > -- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: html table limit
Mozilla, Konqueror, Opera, and IE all act the same way. Check out this page to see what I mean. The top, bottom, and right side of the table borders act funky: http://www.geocities.com/emperorrob/test.html I tried the validator but it keeps timing out. :) I guess the file is too big. On Wed, 2003-03-12 at 12:02, Bob Showalter wrote: > Rob Benton wrote: > > Is there a limit to how many rows you can put in an html table? I > > can't find anything wrong with my script but when I get over 1000 > > rows or so in my tables they start drawing weird borders. > > That would be a function of the browser, so see if your browser has any > limits. Try viewing the page with different browsers. Also, make sure your > all your tags are balanced ( with , with , etc.) > > You can run your HTML through a validator such as http://validator.w3.org/ > > > -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
html table limit
Is there a limit to how many rows you can put in an html table? I can't find anything wrong with my script but when I get over 1000 rows or so in my tables they start drawing weird borders. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
CGI::FormBuilder parsing
I've noticed that when using the formbuilder that field names that have underscores in them are replaced with spaces. And also that if a field has a '.' in it, that . and everything after are truncated when printing. Is there any way to modify this? -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
