I have recently upgraded to 4.3.4 and am having trouble with keeping users logged in when they check the box. 

In 4.0.3, there was a setting in web.config for keeping users logged in for n seconds, and I just made it a huge number.

In 4.3.4, I set the following.

<membership defaultProvider="AspNetSqlMembershipProvider" userIsOnlineTimeWindow="512640">

I believe that is in minutes, so I set it to a year of minutes.  Users are still complaining of being logged out after a certain time. 

Another problem is that sometimes a user can NOT log out.  It just refreshes the pages. 

I also have a problem with pages hanging since I moved to 4.3.4.   I just got the same thing when I went from dotnetnuke.com homepage to forum.  Any ideas?

Can someone tell me the best settings to have in the web.config and scheduler for a site that has 5000 visitors/day and 1,000,000 page views/month?

I have the authenticated cacheability set to Public.  I don't have a store, so I think this is the best, correct?

Is there any documenation on all the features available with 4.3.4 that gives the pros and cons of each setting?  Something like that would eliminate the majority of these posts.

Thanks,

Chad

You're not using the correct setting you need for persistent cookies (i.e. for users using the 'remember me' checkbox) . See my blog http://dotnetnuke.com/Community/Blogs/tabid/825/EntryID/233/Default.aspx for details.

The value you've changed is for the usersonline capability, making it a large value like that will just make your amount of users online count incorrect, and probably mean the details will be held too long in the database, causing it to grow large.

I haven't heard of issues with users failing to log out.

I detail the logic behind cachability settings here - http://dotnetnuke.com/Community/Blogs/tabid/825/EntryID/472/Default.aspx , in your case public sounds fine.

Settings that can be set at the host/portal level are template driven, and can be read about in DotNetNuke Portal Template.pdf and Hardening DotNetNuke Installations.pdf (for the security related ones).

Cathal

actually it's the cookie that maintains the user login, so if they can't log out it usually points to something stopping access to their cookies e.g. norton internet security.

Cathal