Field group bug

I will take a look at the data in the database later tonight. Why did this problem occur at all ?

Why did this problem occur at all ?

I redesigned our CB Repeat jQuery plugin so it doesn't have to re-index the entire repeat usage every time a row was added, removed, or moved. Large repeat usages would lose data when this re-indexing failed and it often did in large repeat usages especially when moving rows. That can't happen anymore now that it's redesigned to only index new rows and it will keep track of repeat usages indexes so it knows the next index. This process was also incredibly slow and it's now lightning fast.

I think the bug had corrupted my data in the row where I had tried to save new values:

{"1":{"cb_teammode":"2022-12-14"}}

I changed it to:

[{"cb_teammode": "2022-12-14"}]

And now I can save new values to the field again.

Both formats are perfectly valid and don't cause any issues in my tests. The first format can happen if you have 2 rows and deleted the first row this causes index 0 to be removed and index 1 to remain. Adding a new row should then have an index of 2 not 1 or 0.

Please be sure you've ran both database fix tools as instructed earlier as this will be a problem if the column is stuck as JSON instead of TEXT, which it shouldn't be as that should've migrated on install.

See the below screenshots of this structure working fine.

Single Row
 
Add New Row
 
Stored 2 Rows
 
Displayed 2 Rows