Hi chriso. When you make a major change in your node (aside from corrected a typo or adding a mild clarification sentence), it's helpful if you note the change. In this case, you replaced your code with something completely different. That's a shame because I was going to comment on your first code (not answering your question, but rather, pointing out some serious problems.)

First off, your code had a significant security hole. I saw this:

That looked suspicious to me, so I read down further and saw this:

There are a variety of issues with this. First off, you're allowing someone to atttempt to open any file on your system. What do you do when someone types in ../../../../../some_file_name? If the Web server is running with permissions to open that file, something very bad could happen. Unfortunately, since you list your URLs, bad guys not only know what the security hole is, they know where it is.

If they don't have permissions to open the first file, you then have them attempt to open a second file. If the second open fails, it will do so silently and your code will not work.

You may wish to read lesson three of my CGI course. That lesson covers basic security. The other lessons will probably benefit you, too, but that one is a good start.

I'm guessing that you are running under mod_perl with the Apache::Registry module. If that is correct, then you are experiencing a classic problem with coding cgi style programs and running them under mod_perl.

I'd suggest reading the excellent mod_perl user's guide http://perl.apache.org/docs/1.0/guide/. You might start with the chapter "CGI to mod_perl Porting", and pay special attention to the section called "Global Variables Persistence".

Basically you want to use a lexically scoped variable (my $var;), scoped in manner that will go out of scope between each request.

Coding cgi style programs under mod_perl contains several traps for those who aren't very familiar with Perl's variable scoping (and closures). Personally I feel that coding regular mod_perl handlers is much more straight forward.

Just to elaborate a little bit, if you're running this script under mod_perl or similar, every time the script is executed it just executes the code again, exactly as it was typed. In this case, because you use global variables, every time through the script you push more questions onto your array, and it never gets reset. The best way to fix this is by using my variables:

{
  my @allquestions;
  ...
  push(@allquestions,"question");
  ...
  print @allquestions;
}
[download]

This will cause the variable to be newly created every time your code is called, which will make it start off empty.

In general, all of your variables in a mod_perl script should be my variables, unless you've thought about it and you really want them to retain their values between runs.

You should also consider running your code under use strict and use warnings, and you should definitely configure your mod_perl to use "taint mode", which will stop mistakes like the one Ovid pointed out from becoming crippling security holes.

"The best way to fix this is by using my variables:

{
  my @allquestions;
  ...
  push(@allquestions,"question");
  ...
  print @allquestions;
}
[download]

This will cause the variable to be newly created every time your code is called, which will make it start off empty."

If I use "my" within an "if" statement, doesn't this make it impossible for me to pass that variable to another script when I use a form and pass them via a hidden variable if the hidden variables are outside the if statement?

Kind regards,
Chris