Well now you have me doubting myself...

Are we *SURE* at this point, that this affects all 1.3.6 users, or is it my contrib that caused the problem in the first place?? I thought I tested on a fresh copy, but maybe I got mixed up... I didn't know you had SessionWatcher going too.

I don't want to install another fresh copy (too busy right now) so can someone WITHOUT sessionWatcher please follow Jeff's instructions and confirm the problem?

Thanks.

- Steven