Empty row

Hi,

for some reason the table data seems to be corrupted or there is a new browser version in which the script no longer works correctly. It would help if you could describe to me what happened before the error.

Try to fix the problem step by step:

• reload the page
• delete all broken lines and re-enter them
• delete the last correct line and try to create a new one
• delete all lines and enter new ones
• delete all columns and enter new columns and rows
• delete the Gutenberg block and enter a new one

If none of this helps, I need more information to reproduce the problem.

• Which Browser name and version the issue appears?
• Does the issue appears on other browsers?
• Which Operating system was used?
• Which location is the table field applied to?
• Is it applied to a page using the Gutenberg editor?

Thanks much for reporting me that issue and helping me to resolve this,
Johann

Thanks for your response.

I try all step but it’s not working :

• Which Browser name and version the issue appears?
  • Safari Version 17.6
• Does the issue appears on other browsers?
  • Same issue in Chrome
• Which Operating system was used?
  • MacOS 14.6.1
• Which location is the table field applied to?
  • In custom post type editing
• Is it applied to a page using the Gutenberg editor?
  • No, we don’t use Gutenberg editor

Hi,

I integrated a table auto repair in the next unpublished version of the plugin (v1.3.25).
You can pre testing it, if that version helps to fix the table issue.

Downloadlink v1.3.25:
https://downloads.www.ads-software.com/plugin/advanced-custom-fields-table-field.1.3.25.zip

On loading the page, the table with the protruding cells should be displayed repaired. The repaired table will only be permanently repaired when the page/content is saved. The contents of the protruding cells will be lost.

Cheers,
Johann

Thank you for your help, but version 1.3.25 worsens the result a bit as I no longer have any data when reloading the page.

This means that the column information in the table data is may incorrect or missing. Can you please send me the output of get_field( 'your_broken_table_field_name', $post_id, false ); ? This allows me to see exactly what went wrong with the table data.

Thanks!

Thank you for your help. I can’t test it right now, but I’ll send it to you this evening, or by tomorrow morning at the latest.

Good evening, as requested, you will find the output of the field in the post that is causing the issue.

Array ( [p] => Array ( [o] => Array ( [uh] => 1 ) ) [h] => Array ( [0] => Array ( [c] => ) [1] => Array ( [c] => Grumes ) [2] => Array ( [c] => Bois d'industrie ) [3] => Array ( [c] => Bois énergie ) ) [b] => Array ( [0] => Array ( [0] => Array ( [c] => 2006 ) [1] => Array ( [c] => 804 ) [2] => Array ( [c] => 598 ) [3] => Array ( [c] => 256 ) ) [1] => Array ( [0] => Array ( [c] => 2007 ) [1] => Array ( [c] => 831 ) [2] => Array ( [c] => 641 ) [3] => Array ( [c] => 211 ) ) [2] => Array ( [0] => Array ( [c] => 2008 ) [1] => Array ( [c] => 776 ) [2] => Array ( [c] => 540 ) [3] => Array ( [c] => 217 ) ) [3] => Array ( [0] => Array ( [c] => 2009 ) [1] => Array ( [c] => 757 ) [2] => Array ( [c] => 436 ) [3] => Array ( [c] => 277 ) ) [4] => Array ( [0] => Array ( [c] => 2010 ) [1] => Array ( [c] => 697 ) [2] => Array ( [c] => 434 ) [3] => Array ( [c] => 323 ) ) [5] => Array ( [0] => Array ( [c] => 2011 ) [1] => Array ( [c] => 739 ) [2] => Array ( [c] => 468 ) [3] => Array ( [c] => 424 ) ) [6] => Array ( [0] => Array ( [c] => 2012 ) [1] => Array ( [c] => 661 ) [2] => Array ( [c] => 352 ) [3] => Array ( [c] => 341 ) ) [7] => Array ( [0] => Array ( [c] => 2013 ) [1] => Array ( [c] => 598 ) [2] => Array ( [c] => 291 ) [3] => Array ( [c] => 490 ) ) [8] => Array ( [0] => Array ( [c] => 2014 ) [1] => Array ( [c] => 614 ) [2] => Array ( [c] => 229 ) [3] => Array ( [c] => 557 ) ) [9] => Array ( [0] => Array ( [c] => 2015 ) [1] => Array ( [c] => 583 ) [2] => Array ( [c] => 142 ) [3] => Array ( [c] => 609 ) ) [10] => Array ( [0] => Array ( [c] => 2016 ) [1] => Array ( [c] => 537 ) [2] => Array ( [c] => 136 ) [3] => Array ( [c] => 642 ) ) [11] => Array ( [0] => Array ( [c] => 2017 ) [1] => Array ( [c] => 532 ) [2] => Array ( [c] => 158 ) [3] => Array ( [c] => 590 ) ) [12] => Array ( [0] => Array ( [c] => 2018 ) [1] => Array ( [c] => 506 ) [2] => Array ( [c] => 170 ) [3] => Array ( [c] => 638 ) ) [13] => Array ( [0] => Array ( [c] => 2019 ) [1] => Array ( [c] => 517 ) [2] => Array ( [c] => 142 ) [3] => Array ( [c] => 604 ) ) [14] => Array ( [0] => Array ( [c] => 2020 ) [1] => Array ( [c] => 438 ) [2] => Array ( [c] => 186 ) [3] => Array ( [c] => 678 ) ) [15] => Array ( [0] => Array ( [c] => 2021 ) [1] => Array ( [c] => 541 ) [2] => Array ( [c] => 237 ) [3] => Array ( [c] => 734 ) ) ) [c] => Array ( ) [acftf] => Array ( [v] => 1.3.20 ) )

Thanks, that helped. I will come up with a solution.

Hi,

you can test the version 1.3.26 that now has repairing missing data sections and ensures that all table sections and rows have the same number of columns. This might repair the table data consistency, but it will cause the data from cells that were created across the number of columns to be lost.

https://downloads.www.ads-software.com/plugin/advanced-custom-fields-table-field.1.3.26.zip

One reason for such data inconsistencies can be incorrect programmatic modification of table field data by using update_field().

I hope that the adjustment in v1.3.26 will ensure that such data inconsistencies do not destroy the usability of the table in the future.

Johann

Thank you very much. It works perfectly.