entering a nonnumeral value to an integer field
results in an empty field without any validation error,

it jast says: %start was changed to %value; after savig the content .(and value is an empty string)

documents in function number_integer_validate() (number.module line 476) says: // No reason to make this an error, just need to inform user what has changed.

but why? It is a validation error so why we should save an emty field to database? setting a validation error makes user to enter a correct number.

float and desimal fields also have this problem.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

abbasmousavi’s picture

Another similar issue is reported in http://drupal.org/node/143697 (patch)
also in
http://drupal.org/node/133984 (patch)
http://drupal.org/node/115632

abbasmousavi’s picture

Title: Integer field validation » Number field validation
Priority: Normal » Critical
Status: Active » Needs review
abbasmousavi’s picture

FileSize
1.97 KB

the patch fixes the problem for decimal, float and integer fields.

abbasmousavi’s picture

Version: 6.x-2.0-beta » 6.x-2.x-dev
yched’s picture

Priority: Critical » Normal

Trying to identify critical bugs blocking an RC.
This one, although important, is not a blocker.

Also, attached patch isn't in the proper format used or drupal.org - see http://drupal.org/patch/create

abbasmousavi’s picture

FileSize
2.8 KB

I have updated the patch style to unified.

abbasmousavi’s picture

Version: 6.x-2.x-dev » 6.x-2.0-rc2

this patch is agaist 6.x-2.0-rc2 version

abbasmousavi’s picture

Version: 6.x-2.0-rc2 » 6.x-2.0-rc6
KarenS’s picture

Status: Needs review » Fixed

I updated this to use the same text as before for the error messages, except for the 'value has been changed to value2' part.

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.