Database error 1054 after deleted custom field... can't rebuild index
My client is having an issue when publishing an entry in a specific channel. The entry publishes, but they are receiving an error after they submit the entry. It says "Error Number: 1054". I found someone else on this forum that had the same issue, which was resolved after resaving the collection and then rebuilding of the index. I tried that, but it won't rebuild and returns the same error. So, I tried creating a new index for that channel. When I tried to build the index for the first time, it gave me a different error. This time Error Number: 1153 and references this file: low_search_index_model.php. I recently deleted some unneccesary custom fields which I believe is causing this issue. Any help would be greatly appreciated!
Replies
Low 9 Sep 2016 06:25
Re-saving the collection should fix the issue, I think.
What exactly does the error say (the number itself isn't particularly helpful, I'm afraid)?
DennisDerammelaere 9 Sep 2016 06:28
Now I'm noticing that the original index is not giving me the 1054 error anymore. It is giving me the 1153 error (max_allowed_packet). The original issue seems to have been resolved, but now I have a new one. I will ask the server admin to increase the allowed packet size. This should resolve the issue.
Low 9 Sep 2016 06:30
You might be able to work around the max_allowed_packet issue by setting the weight of the searchable fields, specifically any that contain lots of text, to 1.
DennisDerammelaere 9 Sep 2016 06:39
Low, Thank you so much for your quick response! Your work-around worked! We are back in business.