I check the persistent login every time that I login but it does not appear to have an effect. Is anyone else having this issue or is it just my machine being goofy about cookies?

same here :)

Good. I am part of a pilot to lock down users here that were previously admins on their machines. I have seen some wierdness related to the pilot. I didn't really think this was one of them, but I can provide better feedback on the pilot if I can determine the real root cause.

Yeah, something weird in the way DNN processes cookies occurs. For the most part, the "persistent" won't work.

Thanks for the confirmation Don.

Don -
A little background - http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryID/233/Default.aspx. 


Just set the PersistentCookieTimeout value in the appsettings section of web.config to some large value (43200 is a 30 day timeout).

Ah. Useful to know - I'll see what I can do.

Any luck Don? It's more than a little bit annoying.

thanks

Editing the web.config file is non-trivial from a configuration management standpoint - I have a number of updates I'm planning for January, and that's one of them. Think of it in the same context as, say, raising the domain functional level in Active Directory - something you think long and hard about and roll into a broader project :).

I've made the necessary changes to the web.config file. It doesn't seem to be making any difference for me, though.

Not here either.

We're going to table this until I get the new version of the software installed - see "Community Business" forum.

Joe, you are my hero. :)