Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1

TOPIC:

Numeric Validation -Fails Integer [2.5 BETA TESTS] 21 Jun 2013 16:55 #7593

  • BTB300
  • BTB300's Avatar Topic Author
  • Offline
  • Moderator
  • Moderator
  • Posts: 415
  • Thank you received: 132
Searched for this one but could only find posts from 6 -7 months ago (sorry if it is already a known issue in 2.5 beta)

Today I created an integer field and set the properties as follows
- required -> yes
- unique -> no
- default value -> 365
- prefills form -> yes

validator -> numeric (set by default when field created)

in the validation test box any integer such as 2011, 365, 35465... fails validation

also fails in downloaded component

Please Log in or Create an account to join the conversation.

Numeric Validation -Fails Integer [2.5 BETA TESTS] 21 Jun 2013 18:19 #7596

  • BTB300
  • BTB300's Avatar Topic Author
  • Offline
  • Moderator
  • Moderator
  • Posts: 415
  • Thank you received: 132
After some trouble shooting - rule names miss matched perhaps?

an integer value lets say 2...

Fails
numeric
positive integer

passes
decimal
positive decimal
percentage

A decimal value lets say 2.0 or 2.00

passes
percentage rule only

fails
All other predefined number validation rules

Hope the above information helps to find the resolution

Please Log in or Create an account to join the conversation.

Last edit: by BTB300.

Numeric Validation -Fails Integer [2.5 BETA TESTS] 23 Jun 2013 21:43 #7619

Hi,
I had the same experience, the numeric regex has an unexpected behaviour (in my opinion).
I thought it should allow any integer positive or negative, but I was wrong. it works only with a numeric range between -9 and 9.
I think this should be changed, also because this validation is used on the ordering field, so when the list becomes higher then 1 digit (for example: 10), the validation give a false error in the form.

I fixed it, using this regex pattern: ^-{0,1}\d+$
The following user(s) said Thank You: admin

Please Log in or Create an account to join the conversation.

  • Page:
  • 1
Time to create page: 0.082 seconds

I jumped and started to work on a demo component... but 2 days later this demo component became the real component. I just showed today the end result to my customer and he turned to me and said... "this is more than I expected"... All of this is because Cook did cut about 70% of my work and provided me more ways to improve the usability of the component. The end result was 17 tables all related between than to generate a full dashboard for the travel agents. Thanks for Cook developers for such great tool. This component would not be possible to be done at short time with all the features in it
Griiettner (Forum)  

Get Started