Hi Ankara,

I could not reproduce the issue on your site(http://take.ms/lCNZc). Am I missing something here?

There is an autosave feature in the composer which should save the content every now and then when an author composes.

I can't say for sure what is the problem here. Sometimes it works sometimes not and that is an issue.
After I posted this ticket I changed the time that a session is being kept for more than an hour to make sure that even if an author spends long time writing he will not get loggeded-out.
Anyhow - the autosave does not seem to work as it is supposed to:
My girlfriend was writing a post - took her more than 40 minutes. When she was finished she pressed the publish button but - instead of seing a published post she got logged out and all of her work was gone. If the autosave feature works - how come the session expired? Doesn't autosaving work count as "activity"? Shouldn't it prolong the session? (Or postpone the reset of session to be exact)
And even if the session ends - shouldn't the post be saved in the form that it had just before the session finished?

When I first asked You guys about EasyBlog You said that there is an autosave feature which works like in Blogger - that does not seem to be true. In Blogger I never had to worry if My work will be saved or not.

Hey Ankara,

how come the session expired?

This is what we are trying to find out currently but we have not been able to reproduce the issue on your site yet.

Doesn't autosaving work count as "activity"? Shouldn't it prolong the session?

Yes it should count as 'activity'. As for prolonging the session, there is a keep alive function that do this(http://take.ms/afJCj).

Perhaps you can try to create a post and monitor the browser console and see if this keep alive function trigger every 1 or 2 minutes?

For the autosave, may I know whether you or your authors see this in the composer after the first few minutes(http://take.ms/teXin)? The draft should be saved at the stated time once you see that message near the save draft button.

Can you also provide us the following so we can do some tests?
- login access for one of the authors that is experiencing the issue
- frontend composer url and how the bloggers access this url