The problem with saving the draft server side is if the server is down or the connection is lost then so will the draft be once you click submit.
It needs to be locally saved.
I don't think the autosave is a good idea, wordpress uses it and there has been talk that it can fast bloat your database.
Have my vote. Many people have said they gave up on a long post after this happens. This will in turn encourage more posting.
Could be cookie-stored with the thread ID and if threadid is set in cookie, display draft...This would be nice but i think it's a resource issue.
It'd have to only be stored for a set period though. I don't want post drafts stored for days on end... 60 minutes maximum. If a user doesn't come back to a post within 60 minutes, they don't want to reply to it.I'd prefer server-side storage so it would work across browsers/devices.
It'd have to only be stored for a set period though. I don't want post drafts stored for days on end... 60 minutes maximum. If a user doesn't come back to a post within 60 minutes, they don't want to reply to it.
It'd have to only be stored for a set period though. I don't want post drafts stored for days on end... 60 minutes maximum. If a user doesn't come back to a post within 60 minutes, they don't want to reply to it.
We use essential cookies to make this site work, and optional cookies to enhance your experience.