New input lost when session expires or No _CSRFToken exist

Hi Jerry, 

Yea, we can give some thought to that.  The problem is servers are sometimes configured to clear cookies before PHP does, so we can lose the login session at any time.

That part of the code is due for a rewrite, might have to be it's own version release.  Here are some thoughts and ideas I have about that: 

• We could keep the user logged in with a background "heartbeat" connection.  Eg: we use javascript to ping the server once a minute to refresh the login token/cookie
• We could check if the user is still logged in before submitting the form.  We'd need to figure out what to do if they're not then, such as a popup login form or something else.
• I could write a debug plugin to test how long servers actually let us keep cookies for, this is something that would be useful to know so CMSB doesn't set the timeout to a greater value
• We could look at caching form input before submission either client-side or server-side.

One workaround for this issue is to open another tab, login in that tab, and then refresh the original page.  But I think the _CSRFToken error happens when the server deletes the session/cookie before CMSB does.  

I'll give it some thought.  Let me know if you have any other input or ideas.

Hi Dave,

That's Great News!

I have no idea what's possible, but I was thinking of an 'auto save' checkbox on the record that's being worked on that a non admin user could check,  If possible, the 'auto save' check box could be a special field that could optionally  be added to the section by the admin during design. 

And an option in the admin to set the auto save repitition rate (every 5 min, every 10 min, etc.) and possibly an 'always autosave' option for admins.

It would be nice if the auto save didn't bring the user back to the record list each 

It might be helpful if you asked the forum community for their input as well.

Best,

Jerry Kornbluth