Why does missing information in speaker request require requester to retype all info?

[carehart]

Related to another request I just made (#10), I've noticed that if a person making a speaker request fails to provide any required info (like the event date, time, and attendee count), the error page offers a "click here to try again" button, but that takes the person back to an entirely blank page. All the info they entered is gone. That doesn't seem right.

Thankfully, they may be able to back up in their browser, but for a web-savvy audience like this, if a button to "try again" is going to be offered, I think the presumption would be that it's preserving the previously entered data.

[ddspringle]

It was not developed to maintain the field data (unlike the speaker sign-up form). An oversight, perhaps, in the rush to get progress made and get this operational.

Feel free to jump in and fix it, or add an issue to have it fixed. :)

[carehart]

But Denny, I did add it as an issue. That’s what this note was generated from. :-) (And I had said in the first one I filed that I just didn’t have time to attend to these, but was noting them to get them on the record.)

In that you aren’t able to tell that I opened this as a ticket, is it that you are getting the emails in some way that doesn’t make it clear to you that it’s coming in as a github issue? That could seem to cause confusion down the road. Ad always, just trying to help.

/charlie

From: Denard Springle [mailto:[email protected]]
Sent: Tuesday, December 23, 2014 12:49 PM
To: teamcfadvance/cfSpeakerList
Cc: carehart
Subject: Re: [cfSpeakerList] Why does missing information in speaker request require requester to retype all info? (#11)

It was not developed to maintain the field data (unlike the speaker sign-up form). An oversight, perhaps, in the rush to get progress made and get this operational.

Feel free to jump in and fix it, or add an issue to have it fixed. :)

—
Reply to this email directly or view it on GitHub #11 (comment) . https://github.com/notifications/beacon/AAXyckVpM6R2xgnd_XJZG0sfVTZiG4T4ks5naaJ4gaJpZM4DLnuP.gif

[ddspringle]

These 'issues', frankly, seem to be questioning the motives behind why the system currently operates the way it does, not positive suggestions that could be used to improve the system. Nor do they give any clear direction to TCFA members on how it could be resolved. As such, I'm answering them as the 'why' questions they are.

[ddspringle]

Added a new issue for this. Closing this one.