Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unrelated columns in matrixcontent tables #3810

Closed
carlcs opened this issue Feb 8, 2019 · 2 comments
Closed

Unrelated columns in matrixcontent tables #3810

carlcs opened this issue Feb 8, 2019 · 2 comments

Comments

@carlcs
Copy link
Contributor

carlcs commented Feb 8, 2019

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

  • Craft version: 3.1.8
  • Database driver & version: MySQL
@brandonkelly
Copy link
Member

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.)

@carlcs
Copy link
Contributor Author

carlcs commented Feb 25, 2019

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.

@carlcs carlcs closed this as completed Feb 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants