Re: is there anything more VEXING than checking the $cgi->checkbox ?

In CGI.pm 4.60, the code you showed works as advertised. Here's an SSCCE:

use warnings;
use strict;
use CGI;
my $cgi = CGI->new();
print "CGI.pm Version: $CGI::VERSION\n";
print $cgi->checkbox( { -name => 'cb-1', -value => 1, -label => "", -c
+hecked => 'checked' } );
print "\n\n";
__END__

CGI.pm Version: 4.60
<label><input type="checkbox" name="cb-1" value="1" checked="checked" 
+/></label>
[download]

So I don't know what you're doing wrong, but it should work.

Aside: I don't know whether you've read the documentation in the last few years, but CGI.pm makes it pretty clear that its HTML Generation functions should no longer be used, and explains the reasons. (That note has been there since 4.04 released in September 2014.) As it explains, though it's recommended to use a full framework when possible, it is still reasonable to use CGI.pm for handling the input parameters and otherwise handling the Common Gateway Interface requests and responses (though CGI::Fast or others give the same hooks in a smaller package), but you should definitely use a templating toolkit of some sort for actually generating your HTML.

Comment on Re: is there anything more VEXING than checking the $cgi->checkbox ? Download Code

Replies are listed 'Best First'.
Re^2: is there anything more VEXING than checking the $cgi->checkbox ? by misterperl (Friar) on Nov 20, 2023 at 14:38 UTC
We're on CGI 4.51 perhaps an update is required. This is an odd presumption: I don't know what you're doing wrong. Perhaps it's more accurate to suggest I don't know what the CGI checkbox sub author was smoking that day! `CGI.pm sub checkbox states "$checked -> (optional) turned on by default if true` Suggested that any value other than 0, '', or undef, should "turn on" checked. What "turned on" means is unspecified. It should result in the word "checked" in the HTML . Im passing "on" and it's not there. I edited the perl lib module CGI.pm . First I added die $checked; and it said "on". So far so good. Then I removed that, and at the end where it "returned", I changed that to die. And I get: `<label><input type="checkbox" name="dev" value="on" class="readonly" / +></label>` [download] proving my checked is set to "on",and its missing in the result.	[reply] [d/l] [select]
Re^3: is there anything more VEXING than checking the $cgi->checkbox ? by pryrt (Abbot) on Nov 20, 2023 at 15:30 UTC
I'm sorry that my phrasing offended you. If you still want help, you can continue reading, and try the experiments I recommend. If you don't want help, then sorry for wasting your time. edit: The further revelations in Re: is there anything more VEXING than checking the $cgi->checkbox ? change my interpretation. Moved this answer into a spoiler, as it's not likely relevant anymore. We're on CGI 4.51 perhaps an update is required. I just installed a copy of CGI 4.51 and ran my exact code from my last post. It behaved exactly as I expected: `% perl -Mlocal::lib=./locallib pm11155672.pl CGI.pm Version: 4.51 <label><input type="checkbox" name="cb-1" value="1" checked="checked" +/></label>` [download] Thus, based on my experiments, I conclude that the difference in CGI.pm version between your 4.51 and the more-recent 4.60 does not appear to be what's causing the difference in output, because the two different versions both produce the same output with the same script for me. Im passing "on" and it's not there. That's not what you said you were doing in is there anything more VEXING than checking the $cgi->checkbox ? . Which are you actually doing? Can you post actual runnable code, rather than just a one-line approximation of your code? That said, I changed the script I showed, using CGI.pm 4.51, to use `-checked => 'on'` instead of `-checked => 'checked'`, and it still gave the HTML output that I showed above in this post. So it's not the difference between `checked` and `on` , as far as I can tell, either. `I edited the perl lib module CGI.pm .` Editing the module is probably the last thing I would have tried. And my experiments are still showing that given a specific call to CGI.pm's `->checkbox()` method, CGI.pm outputs the correct HTML, so I cannot see a need for modifying it yet. The results of your editing experiment don't match with what I would expect, based on the runnable code I've provided. But since you don't show us the code that you used to run your experiments, there's nothing I can do to try to reproduce those results. Could you please return CGI.pm to its original state (in 4.51, or upgrade to a correct copy of 4.60 -- I don't care which, as long as you say which you chose in your reply), and try to run the exact code I posted, and see whether it works for you on your setup? If my exact script with the original CGI.pm (whether 4.51 or 4.60) behaves differently for you than it does for me, then could you please share `perl -V` results -- maybe you've got something different in your perl setup, which is causing behavior to change. On the other hand, if my exact script with the original CGI.pm behaves the same for you as it did for me, then you will need to investigate the difference between how my script calls things and how your script calls things, and see if you can narrow down the differences; if you need help with that, you will have to show short actually-runnable code (the SSCCE = "Short, Self-Contained, Correct Example" that I mentioned above) that shows the behavior that you see, in contrast to my short script which is working.	[reply] [d/l] [select]