You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don’t have steps to reproduce, but there are columns in my matrixcontent tables that I never created for the respective block types. The columns don’t follow the naming schema for custom fields in a block type, the part for the block type handle is missing.
Examples: field_endDate field_ticketOrderUrl
I have fields with this handles in my global context, but I am very sure I never created them within any Matrix field. This installation was created with 3.1 from the start.
Hm, strange. Can you check if you have any database backups from before these columns were added? What is the version in the info table at the time? What is the first Craft version where you see the fields show up? (Note that the Craft version listed in Craft’s auto-generated backup files will generally be the version that you were updating to at the time, as backups aren't made until after Composer is done fetching the new version. So it’s best to just look at the actual info table value.)
Sorry, but I didn’t find any backups that don’t have these columns. In the meantime I have added many more global fields and fields in Matrix block types, and the issue didn’t happen again.
It’s probably best to close here, until someone runs into the same issue and can provide more info.
Description
I don’t have steps to reproduce, but there are columns in my matrixcontent tables that I never created for the respective block types. The columns don’t follow the naming schema for custom fields in a block type, the part for the block type handle is missing.
Examples:
field_endDate
field_ticketOrderUrl
I have fields with this handles in my global context, but I am very sure I never created them within any Matrix field. This installation was created with 3.1 from the start.
The issue might be related to #3809
Additional info
The text was updated successfully, but these errors were encountered: