Editor "timeout" problem

Rate this topic:

Please Register to post a reply.

Another benefit of registration is the ability to subscribe to and recieve notifications of new posts.

Author

Messages

jncraig
Posts:79

01/31/2008 6:32 PM
John, I can use your good advice again. This is about DotNetNuke 4.6.2 ... If I leave an editor window open too long, then the editor "times out" and clicking submit or update results in a return to the editor window, with new content missing. This happens using the default DNN editor in Active Modules and also when editing Text/HTML module contents. "Too Long" seems to be somewhere between 15 and 20 minutes. The good folks at ActiveModules tell me that this is a problem with the application pool recycling after 20 minutes of inactivity. So ... I set the recycle time for inactivity to 60 minutes, and restarted IIS. No change! I also opened and editor window, typed in some stuff, and made sure that the site stayed active visiting pages on that site from another browser window. No changes. After about 20 minutes the editor still "dies". Do you have any ideas, suggestions, suggestions for debugging, etc.?

John Mitchell
Posts:3188

01/31/2008 8:17 PM
The authentication cookie in DNN is only good for 20 minutes between posts. It is tied to your browser session so unless you are using the same browser session it will time out. One way around that is to use the remember me function when you login so that the auth cookie can automatically be recreated after it expires.

jncraig
Posts:79

02/02/2008 11:47 AM
Thanks ... but ... I have these two in my web.config file: < add key="PersistentCookieTimeout" value="12096" / > < forms name=".DOTNETNUKE" protection="All" timeout="100000" cookieless="UseCookies" / > The second was timeout="1440", but I set it to match the "100000" that is in the web.config file of a site that doesn't exhibit this problem. With that change, I don't see any change in behavior. The editor still dies after about 20 minutes of inactivity. Since i have this problem on one site, but not on another ... can you suggest any other possibilities?

John Mitchell
Posts:3188

02/02/2008 1:48 PM
You could modify the source in the DotNetNuke class libray at HttpModules\Membership\MembershipModule.vb It looks like they have made that expire in only a minute now. Does remember me work after adjusting the timeout settings? I know that PesistentCookieTimeout value was not working for several versions.

jncraig
Posts:79

02/02/2008 2:02 PM
Hmmmm ... that could be the problem. My site that "works" is 4.7.0, whereas the site that doesn't work is 4.6.2. Which of the items should be the one that controls it. Is it the PersistentCookieTimeout, or the other one?

John Mitchell
Posts:3188

02/02/2008 2:12 PM
I change mine on the Forms node and I also add slidingExpiration: timeout="10080" slidingExpiration="true" cookieless="UseCookies"

jncraig
Posts:79

Please Register to post a reply.

Another benefit of registration is the ability to subscribe to and recieve notifications of new posts.