Additional data type suggestions
- Status
- Open
- Subject
- Additional data type suggestions
- Version
- 21.x
25.x - Category
- Easy for Newbie Dev
- Feature request
- Feature
- Trackers
- Resolution status
- New
- Submitted by
- hman
- Lastmod by
- hman
- Rating
- Description
I would like to suggest additional data types with built-in syntax checks that could make life easier for people dealing with user's input into forms:
- Telephone numbers. Basically those should be strings, but with the syntax check that allow only for numbers, spaces, braces () and ONE plus sign (for international numbers, but this must be at the very beginning). Also thinkable would be some special characters, letters, sometimes needed on PBX systems: number sign (#) and asterisk (*) and P for pause, F for hook flash, E for earth.
But please do not make strict checking for a 3-3-4 digit scheme, because this only exists in the US and Canada...
- Zip codes. These should be configurable for the country, as US Zip codes vastly differ from those in Europe (in Germany they are 5 digit numbers only!).
- IBAN international bank account numbers. Those consist of two letters (for the country) and two check digits, then 18 digits for the number. Check digits could also be checked, so typos by the user can be detected (and rejected) upon entry, eliminatin frustrating SEPA withdrawals... And it would be swell if IBAN output could be formatted into 4-4-4-4-4-2 digit scheme with separating spaces!
- BIC Bank interchange codes, these are 11 digit strings
- Debatable: Credit card numbers. Those are actually not allowed in databases containg personal data (PCI, see my feature request for a second DB for those). CC card numbers have a 4-4-4-4 digit numerical scheme, and 2-2 for expiration.
- Not necessary, because outright a compliance problem is the CVC or CVC2, the Card Validation Code (the digits printed, but not embossed, on the back of credit cards so they do not imprint). Those must never be stored anywhere. Not in databases, not on paper, nowhere. They can only be used for online verification and even must not be cached (direct violation of your contract with your card processor).
- Importance
- 5
- Easy to solve?
- 5
- Priority
- 25
- Demonstrate Bug on Tiki 19+
-
This bug has been demonstrated on show2.tiki.org
Please demonstrate your bug on show2.tiki.org
Show.tiki.org is not configured properlyThe public/private keys configured to connect to show2.tiki.org were not accepted. Please make sure you are using RSA keys. Thanks.
- Demonstrate Bug (older Tiki versions)
-
This bug has been demonstrated on show.tikiwiki.org
Please demonstrate your bug on show.tikiwiki.org
Show.tiki.org is not configured properlyThe public/private keys configured to connect to show.tikiwiki.org were not accepted. Please make sure you are using RSA keys. Thanks.
- Ticket ID
- 8068
- Created
- Wednesday 09 February, 2022 21:53:31 UTC
by hman - LastModif
- Wednesday 09 February, 2022 22:09:39 UTC