Low Search / Publisher upgrade gone wild.
Hi Low,
I recently upgraded a site from ee 2.6.1 to 2.10.1. This included a publisher upgrade and a Low Search upgrade.
Now none of our low_search_excerpt fields are populating.
It appears that there were some changes to the whole Publisher/Low Search thing between the versions we changed - namely, you added a language field to collections. With Publisher, both languages could/should be represented by a collection, because they're equally represented in the channels themselves, so I'm not entirely sure what to do here.
Are you able to explain what configurations I need to change or re-tool or point me to some docs/articles that explain this? I'm apparently terrible at Google.
Replies
Low 16 Jul 2015 09:31
Hi Caroline,
As mentioned, the Low Search - Publisher compatibility is arranged by the Publisher Low Search add-on by BoldMinded. If things are not working with that add-on enabled, then you're probably better off asking Brian.
I'm not entirely sure how Brian intended Publisher to work with LS. I guess you can just leave the language selection blank per collection (although that will cause the Lexicon to stay empty, and therefore you can't use search suggestions).
If the excerpts are empty (and so are some other {low_search_x} vars in the Results tag, like {low_search_collection_name}), then that would point to an extension conflict where one extension overwrites the changes of another (here, an extension using the channel_entries_query_result hook would overwrite LS's changes). So that's a thing to check out, too.
carolinecblaker 17 Jul 2015 17:27
" then that would point to an extension conflict where one extension overwrites the changes of another (here, an extension using the channel_entries_query_result hook would overwrite LS's changes). So that's a thing to check out, too."
THANK YOU. This is what is happening here at least. How does one check this out? Link to resource?
carolinecblaker 17 Jul 2015 17:36
I queried the hook and disabled an extension that fixed this. Thank you.
Still interested in what it might take to fix the extension I had to disable. Or like what to google for that ;)
Low 18 Jul 2015 08:55
It's usually just a matter of making sure the extension checks the last_call property of the Extensions class and returns the correct value. I'd contact the developer of the extension and point him/her to the docs I linked.