Exception occurs when attempting to use Search block
Permalink
Hey, all.
I'm running concrete5.7.5.2 and experiencing a very strange issue where anytime someone attempts to use a Search block to find pages containing a keyword, the following error appears:
An exception occurred while executing 'SELECT p.cID FROM Pages p LEFT JOIN PagePaths pp ON (p.cID = pp.cID and pp.ppIsCanonical = true) LEFT JOIN PageSearchIndex psi ON p.cID = psi.cID LEFT JOIN PageTypes pt ON p.ptID = pt.ptID INNER JOIN Collections c ON p.cID = c.cID INNER JOIN CollectionVersions cv ON p.cID = cv.cID LEFT JOIN CollectionSearchIndexAttributes csi ON c.cID = csi.cID WHERE ((psi.cName LIKE ?) OR (psi.cDescription LIKE ?) OR (psi.content LIKE ?) OR (ak_meta_title LIKE ?) OR (ak_meta_description LIKE ?) OR (ak_header_extra_content LIKE ?) OR (ak_exclude_sitemapxml LIKE ?) OR (ak_exclude_nav LIKE ?) OR (ak_exclude_page_list LIKE ?) OR (ak_exclude_search_index LIKE ?) OR (ak_tags LIKE ?) OR (ak_thumbnail LIKE ?) OR (ak_exclude_subpages_from_nav LIKE ?) OR (ak_job_posting_department LIKE ?) OR (ak_job_location LIKE ?) OR (ak_blog_entry_topics LIKE ?) OR (ak_project_topics LIKE ?) OR (ak_project_client LIKE ?) OR (ak_project_tasks LIKE ?) OR (ak_project_skills LIKE ?) OR (ak_thumbnail LIKE ?) OR (ak_main_page_color LIKE ?) OR (ak_icon LIKE ?) OR (ak_layout_mode LIKE ?) OR (ak_page_background LIKE ?) OR (ak_number_of_main_areas LIKE ?) OR (ak_number_of_wide_columns LIKE ?) OR (ak_supermint_navigation_type LIKE ?) OR (ak_supermint_theme_preset_options LIKE ?) OR (ak_review_name LIKE ?) OR (ak_review_occupation LIKE ?) OR (ak_review_website LIKE ?) OR (ak_review_website_url LIKE ?) OR (ak_event_multidate LIKE ?) OR (ak_event_exclude LIKE ?) OR (ak_event_section LIKE ?) OR (ak_event_tag LIKE ?) OR (ak_event_thru LIKE ?) OR (ak_event_recur LIKE ?) OR (( ak_gnt_ballotbox_up_votes or ak_gnt_ballotbox_down_votes or )) OR (ak_meta_keywords LIKE ?)) AND (p.cPointerID < 1) AND (p.cIsTemplate = 0) AND (cvIsApproved = 1) AND (p.cIsActive = ?) AND (p.cIsSystemPage = ?) LIMIT 1000' with params ["%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", true, false]: SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ')) OR (ak_meta_keywords LIKE '%test%')) AND (p.cPointerID < 1) AND (p.cIsTemplat' at line 1
The rest of the site works just fine. People can use the search in the toolbar, people can add and edit pages, load files, etc. It's just the Search block itself that gets wonky. I looked for examples of this error in the Forums, and saw that for some folks, it was an issue with custom page types... but this doesn't seem to be associated with a particular page.
Has anyone encountered anything like this before?
I'm running concrete5.7.5.2 and experiencing a very strange issue where anytime someone attempts to use a Search block to find pages containing a keyword, the following error appears:
An exception occurred while executing 'SELECT p.cID FROM Pages p LEFT JOIN PagePaths pp ON (p.cID = pp.cID and pp.ppIsCanonical = true) LEFT JOIN PageSearchIndex psi ON p.cID = psi.cID LEFT JOIN PageTypes pt ON p.ptID = pt.ptID INNER JOIN Collections c ON p.cID = c.cID INNER JOIN CollectionVersions cv ON p.cID = cv.cID LEFT JOIN CollectionSearchIndexAttributes csi ON c.cID = csi.cID WHERE ((psi.cName LIKE ?) OR (psi.cDescription LIKE ?) OR (psi.content LIKE ?) OR (ak_meta_title LIKE ?) OR (ak_meta_description LIKE ?) OR (ak_header_extra_content LIKE ?) OR (ak_exclude_sitemapxml LIKE ?) OR (ak_exclude_nav LIKE ?) OR (ak_exclude_page_list LIKE ?) OR (ak_exclude_search_index LIKE ?) OR (ak_tags LIKE ?) OR (ak_thumbnail LIKE ?) OR (ak_exclude_subpages_from_nav LIKE ?) OR (ak_job_posting_department LIKE ?) OR (ak_job_location LIKE ?) OR (ak_blog_entry_topics LIKE ?) OR (ak_project_topics LIKE ?) OR (ak_project_client LIKE ?) OR (ak_project_tasks LIKE ?) OR (ak_project_skills LIKE ?) OR (ak_thumbnail LIKE ?) OR (ak_main_page_color LIKE ?) OR (ak_icon LIKE ?) OR (ak_layout_mode LIKE ?) OR (ak_page_background LIKE ?) OR (ak_number_of_main_areas LIKE ?) OR (ak_number_of_wide_columns LIKE ?) OR (ak_supermint_navigation_type LIKE ?) OR (ak_supermint_theme_preset_options LIKE ?) OR (ak_review_name LIKE ?) OR (ak_review_occupation LIKE ?) OR (ak_review_website LIKE ?) OR (ak_review_website_url LIKE ?) OR (ak_event_multidate LIKE ?) OR (ak_event_exclude LIKE ?) OR (ak_event_section LIKE ?) OR (ak_event_tag LIKE ?) OR (ak_event_thru LIKE ?) OR (ak_event_recur LIKE ?) OR (( ak_gnt_ballotbox_up_votes or ak_gnt_ballotbox_down_votes or )) OR (ak_meta_keywords LIKE ?)) AND (p.cPointerID < 1) AND (p.cIsTemplate = 0) AND (cvIsApproved = 1) AND (p.cIsActive = ?) AND (p.cIsSystemPage = ?) LIMIT 1000' with params ["%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", "%test%", true, false]: SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ')) OR (ak_meta_keywords LIKE '%test%')) AND (p.cPointerID < 1) AND (p.cIsTemplat' at line 1
The rest of the site works just fine. People can use the search in the toolbar, people can add and edit pages, load files, etc. It's just the Search block itself that gets wonky. I looked for examples of this error in the Forums, and saw that for some folks, it was an issue with custom page types... but this doesn't seem to be associated with a particular page.
Has anyone encountered anything like this before?
I had an attribute included in the sitewide search index that was leading to an error in the SQL query. I unchecked the "include in sitewide search index" box for that attribute and everything's working again.
Sorry for the false alarm, all.