Good observation. THe other approach is to handle it on the server
in domains.ini, so Witango maps the variants of the hostname to a
unified userreference.
Bill
William M. Conlon, P.E., Ph.D.
To the Point
2330 Bryant Street
Palo Alto, CA 94301
vox: 650.327.2175 (direct)
fax: 650.329.8335
mobile: 650.906.9929
e-mail: mailto:[EMAIL PROTECTED]
web: http://www.tothept.com
On Apr 25, 2008, at 8:05 AM, Jesse Parker wrote:
You might be losing your user reference cookie.
In the JS, you are specifically using "www.homepage.com". Maybe your
userreference cookie was set for e.g. "homepage.com" - the two are
very
different to your browser.
Here is a pretty surefire way to make this work:
top.frames[3].location.href = 'http://<@CGIPARAM
SERVER_NAME><@APPFILE>?_function=Loadstuff&<@USERREFERENCEARGUMENT>';
-----Original Message-----
From: Mark Weiss [mailto:[EMAIL PROTECTED]
Sent: Friday, April 25, 2008 10:58 AM
To: [email protected]
Subject: Witango-Talk: Javascript and uservars
Hi all.
I am on the road and have had a funny thing happen.
Can anyone help me understand why when using
top.frames[3].location.href= "www.homepage.com/tango.taf?
_function=Loadstuff";
user vars would go away?
I am selecting for a db using a user var and if I this action using a
link it works fine. If I hit it using JS the uservar is ignored?
Any ideas?
Mark Weiss
______________________________________________________________________
__
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
______________________________________________________________________
__
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
