[mfarmerhi]

Hey John,

Yes, I believe your conclusions were right (but again, am not educated in php/mysql, so am not positive how this all is working).

I also think your solution -- adding the new features onto the END of the user tables -- seems to make more sense.

Another vb.org member suggested the problems might just have come because I didn't clear my cookie cache/close browswer/end session; and I suppose that *might* have been part of the proglem with the postbits (if that's how they work)... dunno, and by the time I figured out what I did, I'd been screwing with both hacks for a couple of hours.

But here's something else I noticed:

Can someone else duplicate this error:

Correctly enter in your cell number in your options. THEN go back and enter in your correct phone number in the top space; and a phone number where the last digit is off by one, in the "Confirm Cell Phone Number" box.

E.g. Enter 8085244983 into both boxes the first time.

Then go back to the same options page and enter:
Cell number: 8085244983
Confirm number: 8085244984

and press enter.

Why does the script allow that and process it?

I noticed this error while testing the hack to ensure that providing a non-matching phone number in the "confirm" box would indeed return the error message. I was a little surprised when the system let me get away with it...