CGI-Callout Issue

Hello,

I'm facing an issue with cgi-callout in the DCT. I have attached the DCT code and .ipl file with the post. I'm passing parameter 'document' in the url which I want to read in the ipl file 'WNewspromptFileUpload.ipl'.

I'm getting blank when I read the argument. Please let me know how should I read it in the ipl file.

Regards,
Harshita

Find more posts tagged with

Comments

ISCBorisB

I'm getting blank when I read the argument

Your DCT sample does not assign any value whatever to CGI "document" Argument.
Your CGI code does not show any attempt to read "document" argument value, whether it is present or not.
In other words, code that you've provided and your stated issue are unrelated.

In general, you may want to search Forum for "onCallout" FormAPI Event processing samples plus so called
"callback" Functions. This technique represents much more flexible and powerful CGI processing than ancient
"iw_callback_var" access mechanism.

And by the way, "Document" (with capital D) is one of the native DOM Objects. If I were you, I would refrain
from the use of ambiguous parameter names.

Icebreaker

Hello Harshitha,

Guess this may help you...

In your DCT, you can have a call-out like this..

[html]

[/html]

In your cgi / ipl you can have the following code to call the path variables along with values.


use TeamSite::CGI_lite;
use CGI qw(:standard);

my %options;

foreach my $optPair (split m|/|, path_info()) {
        my ($key, $value) = split /=/, $optPair;
        $options{$key} = $value;
}
if (! exists $options{'allow_past_dates'} ) {
        $options{'allow_past_dates'} = 1;       #Determines whether dates in the
                                                                                        #past are selectable
                                                                                        #1 for true, 0 for false
}

Jay

Rick Poulin

In your cgi / ipl you can have the following code to call the path variables along with values.

Why would you use this nonstandard URL notation rather than

/iw-bin/blah.cgi?param1=val1&param2=val2

? Then you'd avoid cross-browser oddities and also be able to use the proper APIs in CGI.pm...