Support archive

Database error when submitting an entry.

ldavid20 16 Dec 2013 16:34 problem, complete

EE: v2.5.3
Low Search: 3.0.2

Also am using Playa and Channel Images in this same form.

I am confused because low search is not a field but it says that's where the error is! Any help is greatly appreciated, this project is on a tight deadline.

Thanks!

Replies

1. Low 16 Dec 2013 16:38

   I'll need to take a look myself. Please send SuperAdmin login credentials to hi at gotolow dot com if you can.

2. Low 17 Dec 2013 08:30

   Okay, I looked, and it seemed like it's resolved now. I re-saved the collection that triggered the error. I think a field might have been deleted that was still referenced in the collection field list, so it tried to get data from a non-existent field. Re-saving the collection and rebuilding its index solved the issue.

3. ldavid20 17 Dec 2013 14:03

   Awesome. Thank you very much for your help.

4. louisk 2 Oct 2017 11:03

   JEEZ just had this same error....
   
   I think I have discovered a bug.
   In a channel I'm change out one field type for another with the same name.
   I do that by first creating the new field type and giving it a prefix of "new_".
   Than I fill the new field type with data for every entry and when all is done, I remove the old field type and give the new field the same name as the old one.
   
   After I did that, I had some errors when saving an entry in the CP.
   I realised that low search was hooking into the data being saved. So I went to low search cp page and it told me to rebuild the index of the channel in which I just changed the field type. Upon rebuilding I got the same error.
   
   After removing the collection, and re-adding it, all errors are gone.
   
   So basically, when you remove a field that is currently being included in a search collection, than it doesn't remove that field in the 'exp_low_search_collections' > 'settings' column.

   Low 2 Oct 2017 11:22

   Removing a field that belongs to a collection will do that. I once (in the EE2-version) had a method in place to check for field deletion and change the collection when that was the case, but that turned out to be a resource hog (due to the nature of the EE extension hook fired).
   
   I added a different method in v5.1.0 that uses EE3's way of broadcasting that a field was deleted.
   
   In any case, re-saving the collection where the field was removed will resolve the error.