Our page search has been broken and all arrows point to theposts_pre_query filter in the SolrPower_WP_Query class.
The page search is different because it is a hierarchical post type. And when a hierarchical post type is searched, it uses id=>parent as the return fields parameter.
In the plugin's posts_pre_query filter, it converts "found posts" to just ID's before returning that info to core. So then core goes to map out the id=>parent and it breaks because all it has is an ID instead of a post object.
I will do a PR with the simple fix I made to correct this issue. So far I haven't discovered if this change creates any other conflicts but I will let you know if I do. I, of course, would love to know if you know of any issues with this change.
Our page search has been broken and all arrows point to the
posts_pre_queryfilter in theSolrPower_WP_Queryclass.The page search is different because it is a hierarchical post type. And when a hierarchical post type is searched, it uses
id=>parentas the return fields parameter.In the plugin's
posts_pre_queryfilter, it converts "found posts" to just ID's before returning that info to core. So then core goes to map out theid=>parentand it breaks because all it has is an ID instead of a post object.I will do a PR with the simple fix I made to correct this issue. So far I haven't discovered if this change creates any other conflicts but I will let you know if I do. I, of course, would love to know if you know of any issues with this change.
Thanks!