What I would do in this case would be to comment out all your redirects first-- then anyplace you have a redirect-- do a <cfdump var="#SESSION#"/><cfabort />
And verify that the server is getting the info that it needs. I also have found that instead of accessing the SESSION scope directly, you are better off either adding a global function to access the structure-- the point being you cannot depend on the SESSION scope to actually exist before you depend on it for critical processes. SESSION/COOKIE scopes can bite you an the rear if not managed effectively, try to encapsulate all access to those scopes in one place, it will save you these headaches in the long run. -- /Kevin Pepperman "They who can give up essential liberty to obtain a little temporary safety, deserve neither liberty nor safety." - Benjamin Franklin ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:331395 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
