-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pro search throws an error if using more than one results tag in a template, and you search by keyword #2435
Comments
@agun I was not able to replicate this so far. Would you mind sharing your template code here? |
No problem @intoeetive ... this is in a template called /filter/services.html :
This is for a health related website, so doing a keyword search such as: ...will result in the error. Just using categories it works fine: https://www.mydomain.com/filter/services/?category=27|28 If I remove one of the "results" tags, then it works fine with the keywords (and I do this with plenty of other places through the site ... news, general search, events, resources etc). In Pro_search_words.php if I change line 201 from:
to:
Then it all works fine (which is what I am doing until this is fixed in the core). Cheers! |
Description of the problem
Using multiple {exp:pro_search:results} tags in a template, and then searching by "?keyword" the following error is thown:
How To Reproduce
Steps to reproduce the behavior:
On a single template, I have 1 {exp:pro_search:form} tag with a keyword search input, and a category select input. I also have 2 {exp:pro_search:results} tags, each using a different "collection", and then styling the results differently.
Error Messages
Environment Details:
Possible Solution
It appears that when running the "function stem($word)" multiple times, it only returns the $method = 'stem' the first time. Subsequent iterations (in my case just a second one), then $method = '' ... which results in the error. I appreciate that this isn't a possible solution, but it is the root cause of the issue.
The text was updated successfully, but these errors were encountered: