Sign In

Error: No valid form action received -- when previewing an "edit"

Replies
11
Author
Time

😦

Error: No valid form action received
at EventEmitter.<anonymous> (/srv/www/originaltrilogy.com/comitium/node_modules/citizen/lib/helpers.js:246:13)
at emitOne (events.js:96:13)
at EventEmitter.emit (events.js:188:7)
at /srv/www/originaltrilogy.com/comitium/app/patterns/controllers/post.js:255:23
at groupTracker (/srv/www/originaltrilogy.com/comitium/node_modules/citizen/lib/helpers.js:298:9)
at EventEmitter.<anonymous> (/srv/www/originaltrilogy.com/comitium/node_modules/citizen/lib/helpers.js:124:7)
at emitOne (events.js:96:13)
at EventEmitter.emit (events.js:188:7)
at .<anonymous> (/srv/www/originaltrilogy.com/comitium/app/patterns/models/post.js:127:23)
at nrWrappedHandler (/srv/www/originaltrilogy.com/comitium/node_modules/newrelic/lib/transaction/tracer/index.js:372:19)

BTW, the : - ( [extra spaces added here to show the characters] at the top apparently can’t find it’s emoticon graphic. 😃


“Your love of the halflings’ leaf has clearly slowed your mind”

Author
Time

Thanks for pointing this out. I’ve fixed it in my local build and will post the update today or tomorrow.

The things you pwn end up pwning you.

Author
Time

Fixed.

The things you pwn end up pwning you.

Author
Time

Great! I just tested it in my post above and the “preview” now works.

BTW, while not actually editing that post, I just noticed that the edit page (and it’s probably the same on all other “entry” pages) had no “cancel” button.
I wonder if an elegant solution to backing out of an entry/edit, without changes, is to include a cancel button to return to the calling page?
And how would that handle the entry/edit page opened in a new tab?


“Your love of the halflings’ leaf has clearly slowed your mind”

Author
Time

There was a cancel button on pretty much every form until about 2 days ago when I removed it. The back button used to be a non-starter in the early days of the web and that made cancel buttons a common pattern, but users have warmed up to the back button today (and swiping right to go back is pretty much second nature on touch devices).

Plus, if you use the back button, you go back exactly where you were in the previous page, even if you’d scrolled down a bit. When you hit a cancel button, you’re not going back. You’re actually going forward because you’re reloading the previous page, which causes you to lose your place. I could map the cancel button to the back button using JavaScript, but that would be redundant.

Eventually, these edit forms will be inline anyway.

This post has been edited.

The things you pwn end up pwning you.

Author
Time

As long as just closing the new-tab page, or using the back-button on the parent-page, doesn’t cause the any information to linger, or even update, then that’s fine.
(Just a little healthy paranoia. Ha, ha … uh, what was that? … see it just now? … did, did something just update?)


“Your love of the halflings’ leaf has clearly slowed your mind”

Author
Time

Spaced Ranger said:

As long as just closing the new-tab page, or using the back-button on the parent-page, doesn’t cause the any information to linger, or even update, then that’s fine.

Nothing is saved if you don’t hit “submit”.

TV’s Frink said:

Jay, can you fix the lack of a physical back button on my Ipad? I really hate that.

Sure, I’ll PM you my mailing address and I’ll get to work on it as soon as it arrives. Turnaround time is roughly 2 to 12 months.

The things you pwn end up pwning you.

Author
Time

TV’s Frink said:

Jay, can you fix the lack of a physical back button on my Ipad? I really hate that.

This is one of the things I hate about Android.

Such a thing is confusing. When I occasionally use Android, the back button is this sort of game of uncertainty. You never know what’s going to happen. The way iOS handles this is much better by giving the user a clear indication of what’s about to happen.

Also, it’s “iPad.”

Nothing is so perfect that it can’t be complained about.

To the top