Cookies deleted, then page goes nowhere ...

I am trying to understand a situation with using cookies and then having those cookies deleted outside of CF.

The process flow is the following (kind of long but trying to explain the best I can):

A user visits the homepage and a window asks the user to accept the Internet Usage Policy. The user clicks accept and a cookie is set that will expire in 7 days. Another window will pop and ask the user to accept the Terms & Conditions of the site. The user accepts and another cookie is set; never to expire. (Not the greatest way to approach entering the site but it's what the client wanted for their intranet).

Now there seems to be an issue with deleting the cookies from the users profile before CF can expire them on it's own. For whatever reason the cookies are being deleted via Windows Explorer or some other means and when the user goes back to the site, they cannot enter because the cookies are not there. However, the windows are not popping to allow them to agree to the policies. So it seems like CF says the cookies are there because the windows don't pop and yet they aren't because they can't get anywhere inside the site.

What code would need to be posted for review (if any)? Really everything works fine if the cookies are in place and are not removed outside of CF.

Has anyone heard of something like this before?

thanks

First off your client is wierd, but to his defense i had a dumber client once that wanted information on a form to be processed without being submitted via a button.

Second i got bored reading your manuscript so im just going to wing it and give u ideas, hope im not too incoherent.

Suggestion: Forget cookies although i love them and use them all the time (Kiteless seems to have a distaste for them). I would not use it here cause they have to last 7 days. Anybody that looks at porn will tell you that they delete their files and cookies off explorer daily (right kiteless ).

So what you should do is have a column in a database table called permission or whatever you want. Then when the client hits the checkbox you Input via an <CFQUERY> the word ON or YES or whatever. Then you do a scheduled event page where it Inputs via a <CFQUERY> the word OFF or NO in every row that is older than 7 days.

There you go a bit didactic and trite, hope it helps

-Alas (Tha Man)

- Got that right

There was actually an error in the cookie logic that we were able to fix and everything worked fine after that. Thanks for your response.

Cookies have numerous limitations, including the fact that they can only hold simple values, that there are limits on their length, that there are limits on the number of cookies per domain, and that they are so easy to disable and are viewed by many to be a privacy concern. Even though that is really not true it doesn't change the fact that relying on cookies is risky.

Alas I know you think you are being cute but please knock off this kind of talk, I don't appreciate it.