I’m developing a Stand Alone Entry Form that has a lot of numeric inputs - and most of the submissions will be made from an iPhone, rather than through a regular browser.

I’ve been reading up on how to default the form input to the numeric keyboard, generally by adding “zip” or “phone” to the name of the input field like this:

That works really well. I’m hardcoding the form input fields in my SAEF like this:

I’m assuming if I add phone or zip to that, it won’t add to the correct field in the DB:

I’m not sure how to get around this. My main idea is to do the following:

I’d enter a number into the first field which will default to the numeric keys because of the ‘_zip”, and use some JavaScript to populate the hidden field with the value of the first field upon form submission.

I don’t have to default to the numeric keys, but it makes form entry on this form much much faster - I have about six numeric fields in a row on this particular form.

Any thoughts on this appreciated…thanks!

For the record, this seems to work:

Then, in the Javascript (I’m using jQuery):

I tried ‘keyup’, ‘change’, and finally settled on ‘blur’ as the only thing I could get the iPhone to recognize consistently and correctly.

Again, this is because I had to append the input name with “_zip” in order to get the iPhone to default to the numeric keys rather than the letter keys. Now I can enter things in this weblog faster from my phone than I can from the Control Panel. BOOM!

That’s really interesting, Ryan.  Could be a great wiki article if you can find the time; I know I may be able to make use of this in the future and I’ll ever find the thread again.

One other thing. Because this is on the iPhone I want the least code possible on the page. I’m using a SAEF, which is kicking out that really lengthy liveUrlTitle() function that I’m not even using, because I’m auto-generating unique titles/URL titles like this:

Is there any way to disable the SAEF from kicking out all that unused JavaScript?

A way around it without hacking into the core files would be to set up your SAEF exactly as you want it to look then view the rendered source code for the form and copy-paste the form into a new template. It should still work as it did before but it will instead be hard-coded. You can then use as much or as little of the form as you may or may not need in your situation.

Admittedly any time you want to make changes to the form you will need to re copy-paste unless you can figure out the form without doing that but sometimes it is a bit quicker to do this than trying to find ways around items that may require a hack to either the module or the core files.

Don’t know if that helps at all though.

Best wishes,

Mark

That’s really cool! Great work.

I second Lisa’s suggestion about making a wiki article.

Just noting that as of iPhone 2.0.x the “_zip” trick no longer works - there is apparently, as I write this, no working solution for defaulting to the numeric keypad. I originally picked up the trick here.