Database migration chokes on huge value of a "calendar-details" item in table "post_custom_fields"

Well, so that means it has nothing to do with the PG12 update, so not my fault :stuck_out_tongue:

Yeah, as we said several times using either plugin store or post_custom_fields for stuff that is complex is not sustainable long term. That is why calendar is doing this migration to move to proper tables.

Unfortunately looks like it didn’t come early enough for you and a event got in a bad state. Delete the problematic row and stuff should work again.

1 Like