Grid data left orphaned in database when deleting Fluid Field block #3529
Comments
intoeetive
added a commit
that referenced
this issue
Aug 3, 2023
…ill left in database after removing from Fluid
intoeetive
added a commit
that referenced
this issue
Aug 3, 2023
…ill left in database after removing from Fluid (cherry picked from commit 2d04357)
intoeetive
added a commit
that referenced
this issue
Aug 9, 2023
…field-revisions Resolved issue where it was not possible to save loaded revision if Fluid field has some fields deleted; Resolved #3639 where is was not possible to save loaded revision with removed Grid rows; Resolved #3529 where records for Grid and Relationship fields were still left in database after removing from Fluid
bryannielsen
added a commit
that referenced
this issue
Aug 14, 2023
…revisions Resolved issue where it was not possible to save loaded revision if Fluid field has some fields deleted; Resolved #3639 where is was not possible to save loaded revision with removed Grid rows; Resolved #3529 where records for Grid and Relationship fields were still left in database after removing from Fluid
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
if you have a Grid field setup as available to a Fluid Field where the Grid requires exactly one row (ie so the delete row button doesn’t show) and you delete the entire Fluid Field block, the data stays orphaned in the
exp_channel_grid_field_xxxtable. I'm not certain whether this also happens if there’s more rows in the grid, but I imagine it does. I beleive this is an issue and deleting the Fluid Field should also delete the Grid data.The text was updated successfully, but these errors were encountered: