ElkArte Community

Elk Development => Bug Reports => Exterminated Bugs => Topic started by: tycms on April 04, 2013, 11:04:45 am

Title: Javascript error checking in post action
Post by: tycms on April 04, 2013, 11:04:45 am
Quote from: TestMonkey – Ah. This isn't drafts. And it's not a bug, it's a feature! :D
It's the smart js we added to help you know of errors before you submit.

It is intended to inform you that you won't be able to submit, with empty fields like title and post.

I mean, why should it let you submit, load a page, only to find out AFTER that you can't post, with a title empty?

Suppose you quoted a message and started typing a reply. Then for some reason you had to leave it for a long time. When you complete the reply and try to send it, "the message has the following error or errors that must be corrected before continuing:" warning appears without any explanation. I am not sure about the session length. I will try to replicate this on my local install and report back.
Title: Re: Javascript error checking in post action
Post by: Arantor on April 04, 2013, 11:57:49 am
Yeah, it's going to be timing out of the session and the drafts handler returns the session timeout error.

I personally excluded session timeout from draft saving in Wedge, for this very reason.
Title: Re: Javascript error checking in post action
Post by: tycms on April 04, 2013, 11:59:34 am
This is most probably something related to session verification. I suspect that this bug might also appear at other actions.
Title: Re: Javascript error checking in post action
Post by: Arantor on April 04, 2013, 12:12:24 pm
Not the way it's happening here.
Title: Re: Javascript error checking in post action
Post by: emanuele on November 30, 2013, 06:02:11 pm
Started typing now (2013/11/30 @ 14:17 ECT).

I'll post it later when I come back home. :P

ETA: it's now midnight, so about 8 hours after not even a session error... ???
Title: Re: Javascript error checking in post action
Post by: emanuele on December 17, 2013, 05:35:42 pm
I'd say this has been probably fixed in the meantime whatever it was.