# Bug with number field in form block

**URL:** <https://forums.concretecms.org/t/bug-with-number-field-in-form-block/10096>\
**Category:** Using Concrete / Help\
**Tags:** bug\
**Created:** [October 20, 2026, 9:20am UTC](https://forums.concretecms.org/t/bug-with-number-field-in-form-block/10096 "2026-10-20T09:20:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![MichaelJK](https://forums.concretecms.org/user_avatar/forums.concretecms.org/michaeljk/32/5178_2.png) [@MichaelJK](https://forums.concretecms.org/u/MichaelJK)\
**Post date:** [October 20, 2026, 9:20am UTC](https://forums.concretecms.org/t/bug-with-number-field-in-form-block/10096/1 "2026-10-20T09:20:55Z")

</div>

Hallo,

My user added a form block to their website and wanted to add a phone number field to it, but they accidentally chose a number field. The issue is that their clients used this form and filled in a phone number like “31612345678”, and it caused a crash in the concrete form block, namely:

An exception occurred while executing ‘INSERT INTO atNumber (value, avID) VALUES (?, ?)’ with params [“31612345678”, 5544]:  
SQLSTATE[22003]: Numeric value out of range: 1264 Out of range value for column ‘value’ at row 1

I manually changed it to an actual phone number block, but I think a fallback warning to let the user know it exceeds the number limit should be added to prevent it from fully crashing like it did now.

Concrete version: 9.5.5  
PHP version: 8.5.11

---

<div class="post-metadata">

**Author:** ![plitochnik](https://forums.concretecms.org/user_avatar/forums.concretecms.org/plitochnik/32/6298_2.png) [@plitochnik](https://forums.concretecms.org/u/plitochnik)\
**Post date:** [November 4, 2026, 12:06pm UTC](https://forums.concretecms.org/t/bug-with-number-field-in-form-block/10096/2 "2026-11-04T12:06:06Z")

</div>

Hello, the value column in atNumber is a decimal(14,4), so it only fits 10 digits before the decimal point, and a phone number with the country code is 11. Agree it should come back as a normal validation message instead of an exception though.
