[ic] window.opener property missing in new window

[Honest to Goodness]

I now have a perl routine that opens a socket to the Canada Post server,
delivers some xml and receives a big pile of ready to go html full of
shipping options. Now do I have to define my perl routine as a
globalsub? Or can I just put in inline into checkout.html? I am on a
hosted server so I can't easily modify interchange.cfg. Could I put a
globalsub into catalog.cfg so it will be available to only my catalog?
In fact I tried that with a simple test_global_sub that returns a hello
world and it doesn't work, even after applying changes.

Also after I get past this problem, with or without anyone's help, how
will I turn off the internal ic shipping routines and allow the user to
update the shipping value based on their choices?

 

On Fri, 2002-03-15 at 14:49, Honest to Goodness wrote:
> On Thu, 2002-03-14 at 17:37, Honest to Goodness wrote:
> > I'm implementing the Canada Post eparcel service in my modified
> > foundation checkout page. In the pages/ord/checkout.html page there is a
> > little bit of javascript that verifies the form input and from there I
> > open a new window with just some hello world stuff in it for now.
> > 
> > The plan is that the new window will contain some html sent back to me
> > from the Canada Post server in response to some XML that I have composed
> > and sent to them. Their html is a cute little form with radio buttons
> > allowing the customer to choose how quickly they want their products
> > delivered and what the price will be.
> > 
> > My fantasy is that when the customer chooses their shipping the charge
> > will be sent to the checkout page via the window.opener javascript
> > property and will magically appear in the form.
> > 
> > As I write this I realize how totally naive I am. My new window doesn't
> > have any window.opener property because it was coughed up by the cgi
> > program. And the checkout page is not going to just sit there and be
> > updated, it will have to be rewritten based on the changes in some
> > variables.
> > 
> > So the alternative is to have my Canada Post page show up before the
> > checkout page in a serial fashion and then pass it's output on? It would
> > be nice to have it embedded right in the check out page though ...
> > 
> > Any ideas? I seem to have too many.
> 
> I now have a [include file="pages/shippy.html"] tag in my checkout page.
> It loads a look alike of the html I'm likely to receive from Canada Post
> and it looks very good. But it needs to be the result of a form
> submitted to the postal server or a send of some XML through a socket
> connection and not this static html.
> 
> Also when the user selects their shipping and causes a Recalculate I
> need to know what shipping variables will need updating.
> 
> This interchange stuff is kind of fun in the detective.sluething way but
> also frustrating in the grope.at.fragile.things.in.the.dark sort of way.
> 
> 
> > 
> > _______________________________________________
> > interchange-users mailing list
> > interchange-users@interchange.redhat.com
> > http://interchange.redhat.com/mailman/listinfo/interchange-users
> 
> 
> _______________________________________________
> interchange-users mailing list
> interchange-users@interchange.redhat.com
> http://interchange.redhat.com/mailman/listinfo/interchange-users