I am currectly upgrading a version 6.0.5 umbraco instance to version 7. The install seems to have been successful and all database changes seem to have completed as planned. However when trying to save a content node which contains a not required numeric field with no content supplied in the field it fails to save with a validation error stating "The value is not a valid integer".
Has anyone else found this issue and a way to fix it as it's stopping me proceding with the upgrade?
I was able to confirm this bug (on a clean install, so I don't think it's an upgrade-related issue). I think you may be able to use a textstring property with a regex validator that only accepts numbers or empty strings as a temporary workaround, but I tried to get this working and wasn't able to find a regular expression that did this. Maybe you'll have better luck, you can look on Stack Overflow and on here: http://regexlib.com
Umbraco 7 numeric fields can't be empty
I am currectly upgrading a version 6.0.5 umbraco instance to version 7. The install seems to have been successful and all database changes seem to have completed as planned. However when trying to save a content node which contains a not required numeric field with no content supplied in the field it fails to save with a validation error stating "The value is not a valid integer".
Has anyone else found this issue and a way to fix it as it's stopping me proceding with the upgrade?
Thank you in advance
Dave
Hello fellow David,
I was able to confirm this bug (on a clean install, so I don't think it's an upgrade-related issue). I think you may be able to use a textstring property with a regex validator that only accepts numbers or empty strings as a temporary workaround, but I tried to get this working and wasn't able to find a regular expression that did this. Maybe you'll have better luck, you can look on Stack Overflow and on here: http://regexlib.com
Regards,
Dave
Since I was able to reproduce the issue and it seems to be a pretty obvious bug, I put in a bug report on the issue tracker:
http://issues.umbraco.org/issue/U4-3728
Maybe you'd like to go in and vote for it so it gets more attention?
This also occurs with DateTime fields. I have created a seperate issue for Datetime and voted for the Numeric issue
http://issues.umbraco.org/issue/U4-3730
is working on a reply...