Jump to content


Unsigned number field bug

unsigned field number

  • Please log in to reply
3 replies to this topic

#1 saulimus

saulimus

    Advanced Member

  • Members
  • PipPipPip
  • 40 posts

Posted 28 September 2012 - 12:40 PM

I have a column in the database with datatype INT, unsigned.
In edit/add mode, Gcrud creates an input element like this:
<input id="field-testinteger" name="testinteger" type="text" value="51256" class="numeric" maxlength="10) unsigne"/>
The maxlength is all messed up... in my browser (Opera) this makes one unable to use backspace.
The problem probably lies in the model, function get_field_types_basic_table() ...where it tries to find the db_max_length.

#2 web-johnny

web-johnny

    grocery CRUD Author

  • Administrators
  • 1,150 posts
  • LocationLondon

Posted 01 October 2012 - 06:48 AM

Hello saulimus ,

Yes I can confirm that this is a bug for all browsers. I will try to fix that for the next version. https://github.com/s...crud/issues/102

Cheers
Johnny
Posted Image

#3 saulimus

saulimus

    Advanced Member

  • Members
  • PipPipPip
  • 40 posts

Posted 02 November 2012 - 08:52 AM

Ok, it seems the problem was a little different.
The "backspace not working in Opera" bug is caused by the jQuery numeric plugin...
It seems it doesn't like Opera much when detecting special keys...
http://www.texotela....jquery/numeric/

#4 web-johnny

web-johnny

    grocery CRUD Author

  • Administrators
  • 1,150 posts
  • LocationLondon

Posted 03 November 2012 - 09:48 AM

Hmmm, I see. This is already reported at: https://github.com/S...ugins/issues/17 . I don't know perhaps if you just add a comment there that say +1 , yes it would be good to be fixed actually.
Posted Image





Also tagged with one or more of these keywords: unsigned, field, number

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users