I would suggest that you use the cf_location tag available. It solves all
these problems. It is a drop in replacement for cflocation. It as the same
syntax, and has a couple of nice features that are nice for fuseboxers. It
is available at http://www.fusebox.org
Thanks,
David Sparkman
Application Development Team Leader
Weberize
http://www.weberize.com
-----Original Message-----
From: Nichols, Robert H. [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 10, 2001 2:42 PM
To: Fusebox
Subject: RE: Client variables and cflocation
Except that didn't work -- the bit about using URL_ files. Client variables
are erased when a cflocation is used unless an addtoken=yes is used.
But since the user wasn't logged in yet, I couldn't use an addtoken=YES.
I finally had to figure out a way to pass it as an URL variable and the go
back to it. I doubt this is the way that it was meant to work, but it works
for me. if any one else has some suggestions, please send 'em my way.
Robert H. Nichols
Web Developer
Center for Engineering & Environmental Technologies
Information Delivery Systems <http://ids.rti.org>
Research Triangle Institute
Voice: 919-541-8009 Fax: 919-541-6936
-----Original Message-----
From: Kevin Bridges [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 10, 2001 1:52 PM
To: Fusebox
Subject: RE: Client variables and cflocation
That's what the url fileas are for ... at the end of your switch you just
call a url file that has the cflocation in it and then client variables
don't dissapear.
-----Original Message-----
From: Nichols, Robert H. [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 10, 2001 11:36 AM
To: Fusebox
Subject: RE: Client variables and cflocation
Actually I am *not* using cookies.... here is my cfapplication
statement....
<cfapplication name="AT"
clientmanagement="Yes"
sessionmanagement="Yes"
setclientcookies="No"
sessiontimeout="#CreateTimeSpan(0, 0, 40, 0)#">
However, when I set a client variable and then use a cflocation, the client
variable becomes undefined.
So....
Client.ReturnFuseAction = /index.cfm?fuseaction=Display%5FContents
<cflocation url="#Attributes.GotoURL#" addtoken="No">
client.returnfuseaction = Undefined
-----Original Message-----
From: Scott Van Vliet [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 10, 2001 1:00 PM
To: Fusebox
Subject: RE: Client variables and cflocation
For good practice, I use a JavaScript redirect when I am setting
cookies and redirecting:
<cfcookie name="ckMyCookie" value="MyValue">
<script language="JavaScript" type="text/javascript">
<!--
this.location = "myLocation.cfm?variable=#SomeValue#"
//-->
</script>
Scott
-----Original Message-----
From: Bob Silverberg [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 10, 2001 9:38 AM
To: Fusebox
Subject: RE: Client variables and cflocation
Are you using cookies to store your client variables? That might explain
it, as you cannot set cookies on a page and then do a cflocation.
Bob
-----Original Message-----
From: Nichols, Robert H. [mailto:[EMAIL PROTECTED]]
Sent: April 10, 2001 12:05 PM
To: Fusebox
Subject: Client variables and cflocation
My client variables seemed to be wiped out when I use a cflocation. Any
quick ideas on why this would be happening.
I think I have been staring at this for too long, I know the solution must
be simple. :)
Robert H. Nichols
Web Developer
Center for Engineering & Environmental Technologies
Information Delivery Systems <http://ids.rti.org>
Research Triangle Institute
Voice: 919-541-8009 Fax: 919-541-6936
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
