CGI Question

[Gregory Lypny]

Thank you for your responses, Jacqueline and Mark.

Jacqueline,

     Setting the defaultStack did the trick.  Of course, it will take  
a little while to get used to testing handlers in the use-stack-as- 
CGI style because (and this should have been obvious to me)  
information put into fields doesn't appear in the instance of the  
stack that you are working on; you have to close it and reopen it to  
see the changes made as a result of the submission of a web form.

     Regards,

         Greg


     "OK, dynamics with tension,
        fun and laughter for all."
         -John Lennon (Lost Weekend Sessions)


On Aug 31, 2005, at 11:50 PM, use-revolution-request at lists.runrev.com  
wrote:

> Message: 13
> Date: Wed, 31 Aug 2005 18:17:16 -0500
> From: "J. Landman Gay" <jacque at hyperactivesw.com>
> Subject: Re: CGI Question
> To: How to use Revolution <use-revolution at lists.runrev.com>
> Message-ID: <43163A7C.8070005 at hyperactivesw.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Gregory Lypny wrote:
>
>
>> I'm simply
>> trying to gather data from a form, redisplay it on a web page,  
>> and  save
>> it in a field in the stack.  The problem is that writing to a  field
>> gives me an error.  If I comment-out the sixth line from the  end,  
>> that is,
>>
>>     put webOutput into fld "Another List"
>>
>> it works fine; but when I reinstate it, I get a server error.   
>> What  am
>> I doing wrong?
>>
>
> It's been my experience that you need to either set the  
> defaultstack to
> the one you want to write to, or else specify a full reference.  
> That is,
> do something like:
>
>   put webOutput into fld "another list" of cd 1 of stack "myCGIstack"
>
> Also, if the stack doesn't have the correct permissions set then you
> won't be able to write to it. (Also don't forget to save the stack to
> disk, because when the CGI terminates the stack will be closed.)
>
> Take a look at the web server's error log, you should see a more exact
> description in there of what the problem is. If the server isn't on  
> our
> own machine, you'll have to find where your ISP keeps the log.  
> Virtually
> all of them allow you to see it via a control panel or something  
> similar.
>
> -- 
> Jacqueline Landman Gay         |     jacque at hyperactivesw.com
> HyperActive Software           |     http://www.hyperactivesw.com
>
>