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
Filters not working on channels with multiple entry types? #15
Comments
Hi, looks like there is a server error. Can you provide a full stack trace so that I can debug the issue? Thanks.
Best Regards,
Poh Nean
… On 24 Nov 2021, at 6:37 AM, sonoflee ***@***.***> wrote:
I can't seem to apply omnisearch filters on Channels that have different Entry Types. Clicking the "+ Filter" button just brings up a search field ("Search Attributes") that is unresponsive. In the channels I'm testing this on, the different entry types do have different fields.
in console, I see the error:
Failed to load resource: the server responded with a status of 500 (Internal Server Error)
[site url]/actions/omnisearch/fields?elementType=craft\elements\Entry&source=section:ef7c591c-185e-444f-b322-66ac110e58b0
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Please let me know if you need additional information, and thanks for the quick reply!
|
What are the section types for these entries? Channels, singles, or Structure? Can you provide a screenshot of where the error occured? |
I'm also experiencing this issue. I've narrowed it down to whether or not the section that I'm trying to search contains an "Entries" field type that has "Use this field’s values as search keywords" enabled. The related entry field that I'm trying to make searchable/filterable is a Channel. |
Here's a short screencast I did of toggling the field on / off and the error that I'm seeing: Kazam.mp4 |
Both of the affected section types are Channels. Attaching a screen grab of what happens: Screen.Recording.2021-11-24.at.12.55.49.PM.movboth of the affected channels do have "Entries" fields with "Use this field’s values as search keywords" checked, like @stevecomrie - I haven't yet been able to test whether unchecking will fix the issue yet but will look into that ASAP |
Unchecking that box won't "fix" the issue, but it will prevent that field from showing up in the filter selection list. At best it's a stop-gap replacement that will still let you use most filters except the one field that's throwing errors. |
Thanks everyone. I'm investigating the issue now. |
Fixed in 1.2.3. |
I can't seem to apply omnisearch filters on Channels that have different Entry Types. Clicking the "+ Filter" button just brings up a search field ("Search Attributes") that is unresponsive. In the channels I'm testing this on, the different entry types do have different fields.
in console, I see the error:
The text was updated successfully, but these errors were encountered: