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

Craft 3.7 issue "Column not found" error stemming from BasePredefinedField #119

Open
chasegiunta opened this issue Sep 25, 2021 · 3 comments · May be fixed by #120
Open

Craft 3.7 issue "Column not found" error stemming from BasePredefinedField #119

chasegiunta opened this issue Sep 25, 2021 · 3 comments · May be fixed by #120
Labels

Comments

@chasegiunta
Copy link

Description

I have predefined field called "payments", and upon saving an entry that includes that field, Craft now throws a

 [-][1][-][error][barrelstrength\sproutfields\fields\BasePredefinedField::processFieldValues] SQLSTATE[42S22]: Column not found: 1054 Unknown column 'field_payments' in 'field list'

As this field lives alongside other predefined fields with no problem, and this field is the only one in the fields table with a columnSuffix column populated, I have a sneaking suspicion this is due to something with craftcms/cms#6922

Looks like there was a change made with 3.7 that broke saving newer predefined fields 😕

Additional info

  • Craft version: 3.7.13
  • PHP version: 7.4.22
  • Plugins & versions: Sprout Fields 3.8.5
@yoannisj
Copy link

I am experiencing the same issue here with Sprout Fields 3.8.5 on Craft 3.7.32

@BenParizek
Copy link
Member

Hey folks. I'm currently working on getting many of our plugins updated to Craft 4 and am in the process of simplifying the number of things I have to support in the process. Unfortunately, I do not plan to migrate the Predefined Field or Predefined Date field to Craft 4, and while I've labeled this a bug and will try to address it for Craft 3 when I have a chance, my focus is on the plugins we'll be continuing support for on Craft 4 right now.

My apologies for the inconvenience. If anybody would like to fork and split the Predefined Field and Predefined Date Field out into another plugin, please feel free to, and feel free to reach out if I can help with anything to make it happen.

@chasegiunta
Copy link
Author

@BenParizek FYI, in case you overlooked, I did open a PR to fix this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
3 participants