Answers

• tangerine Posts: 3,365Questions: 39Answers: 395

  November 2020

  Why is it a varchar field if it's always four digits?
  And if you never want to display leading zeros, why not have the database return the required format?
• colin Posts: 15,240Questions: 1Answers: 2,599

  November 2020

  It's definitely worth considering tangerine's comments and consider changing the database schema.

  • if the first digit is zero, datatables do not display the leading zero.

  You would need to do that check in columns.render, and remove it there.

  If still no joy, could you update this test case to demonstrate the issue, please.

  Colin
• Alex_ander Posts: 11Questions: 4Answers: 0

  November 2020

  Thanks a lot for reply!
  tangerine, the problem is that for digits are not digits, but a string (they are part of passport number and it is important to keep the leading zero. For example 0123 is not the same as 123 from passport number point of view).

  colin, the task is not to remove the leading zero, but to show the string "as is", without removing zeroes
• tangerine Posts: 3,365Questions: 39Answers: 395

  November 2020 edited November 2020

  Oh, okay.
  I don't know why DataTables would not be representing your string correctly. I suggest you provide a test case so we see your code running.
  https://datatables.net/manual/tech-notes/10
• Alex_ander Posts: 11Questions: 4Answers: 0

  November 2020

  My case is similar to this example:
  https://editor.datatables.net/examples/simple/fieldDefaults.html
  How is possible to save 0123 and, then, to represen it in column Ext of this example?
• tangerine Posts: 3,365Questions: 39Answers: 395

  November 2020

  I just looked at the example, and did a couple of edits, and I don't get why it won't display leading zeroes.
  Also, the "New" button isn't working.
  We need one of the development team in here.
• colin Posts: 15,240Questions: 1Answers: 2,599

  November 2020

  Yep, it's on Allan's list, so he'll be replying at some point today.

  Colin
• allan Posts: 63,761Questions: 1Answers: 10,510 Site admin

  November 2020 Answer ✓

  It is being caused by this change. Basically when JSON_NUMERIC_CHECK is used, it will return any numeric strings as an actual JSON number - which can sometimes be desirable (1, 2).

  But not in all cases!

  The immediate solution is to use:

  $data = Editor::inst( $db, 'datatables_demo' )
      ->fields(
               // ....
      )
      ->process( $_POST )
      ->data(); // note the use of `data()` rather than `json()` here
  
  echo json_encode($data);
  

  I think we should probably remove that option from the default code since it was only added recently. We'll make it optional. That will be done for 1.9.6.

  Allan
• Lapointe Posts: 430Questions: 81Answers: 4

  November 2020 edited November 2020

  hi @tangerine

  for add button, perhaps in sample use of def value for extn ...

                  label: "Extension:",
                  name: "extn",
                  def: "0000"
  
• tangerine Posts: 3,365Questions: 39Answers: 395

  November 2020

  Thank you, Allan!
• allan Posts: 63,761Questions: 1Answers: 10,510 Site admin

  November 2020

  Fix committed here. As I say, it will be in 1.9.6.

  The new way to pass json_encode options is a second optional parameter for the Editor->json() method - e.g.:

  ->json(true, JSON_PRETTY_PRINT);
  

  Allan
• Lapointe Posts: 430Questions: 81Answers: 4

  November 2020

  @allan is the ? best ?
• Alex_ander Posts: 11Questions: 4Answers: 0

  November 2020

  Allan, thank you so much!! It works now as I need!