I agree that you have this problem in non-CF sites. But the program flow is much more
apparent in a Fusebox site than in other sites. I restricted access using session
variables and am in the process of converting the site to fusebox. Other than using a
step variable does anyone know of another way to do this?
>>> [EMAIL PROTECTED] 05/02/01 18:06 PM >>>
Couldn't they do that in a non-CF site too?
What you're talking about sounds to me like a regular programming process
problem. You could set a client variable on each page with the step number,
and send bad users to the right page.
NAT
> -----Original Message-----
> From: Jim Stahlin [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 02, 2001 1:50 PM
> To: Fusebox
> Subject: Managing program flow
>
>
> I have a problem in getting my mind around how you can restrict
> the flow of actions in fusebox. I have a site that in the
> checkout process requires the user to pick shipping method, then
> Credit Card info, then Shipping info, then approve the order. If
> I use Fuseactions to do this the user could pass the last
> fuseaction in the URL variable and skip all the entry screens.
>
> Archives: http://www.mail-archive.com/[email protected]/
> Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=sts
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
