hi tim,
thanks for your reply. what puzzled me was that by setting the CFPARAM with the cookie scope i was actually creating a persistent cookie that was accessible from other templates.
i know that using CFPARAM with the URL and FORM scope will only create a local variable unless it is passed...
hi,
i ran into a problem today where a 'cfparam' value set with the 'cookie' scope was creating a persistent value. i thought that any variables created with 'cfparam' were strictly local and to write to a cookie required use of the 'cfcookie' tag. an example of the code is as follows:
==...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.