Almost finished.
Just my 2 cents, but I would not use the Display location "Self placement" to control whether a filter displays or not. Instead, use the Display field on list option as that would make the most sense, since the filters are on Index and Category pages, so displaying those fields on listing pages, would make sense to also display filters for them.Almost finished.
I tried different options and decided to add an additional field in the "Field" entity and add a filter to the "DefinitionSet" so as not to depend on being on the Index or Category pages.Just my 2 cents, but I would not use the Display location "Self placement" to control whether a filter displays or not. Instead, use the Display field on list option as that would make the most sense, since the filters are on Index and Category pages, so displaying those fields on listing pages, would make sense to also display filters for them.
One of the main use cases for the the Display location "Self placement" is to NOT display those fields anywhere, so admins wouldn't want those fields to be automatically exposed as Filters. Hope that makes sense![]()
View attachment 320842
- Added setting to allow filtering for a custom field
- Fixed a bug where having radio buttons in filters with the “Required” option enabled prevented filtering.
okFeature request for additional field types:
Text field (using LIKE)
Number field (range)
Any upcoming updates for this, it's the final part of the piece I'm missing
Hi. I just got back from a business trip two days ago and started developing. I'll post an update in a couple of days.Any upcoming updates for this, it's the final part of the piece I'm missing![]()
Just to clarify, are we talking about searching by existing types of custom fields or are you asking to add new types of custom fields?Feature request for additional field types:
Text field (using LIKE)
Number field (range)
Yes, existing typesJust to clarify, are we talking about searching by existing types of custom fields or are you asking to add new types of custom fields?
- Added support for all standard custom user field types
- For fields with the Number type, the ability to specify a range of values has been added
elseif (array_key_exists('min', $filter) || array_key_exists('max', $filter)) {
if (array_key_exists('min', $filter)) {
$itemFinder->where('CustomFields|' . $fieldId . '.field_value', '>=', $filter['min']);
}
if (array_key_exists('max', $filter)) {
$itemFinder->where('CustomFields|' . $fieldId . '.field_value', '<=', $filter['max']);
}
}
- Fixed a bug when filtering numeric values in a specified range
I'll think about how to implement it better and add it in the next version.2) The text input field needs an exact match to find anything, which isn't very useful.
Example field: Engine 1.6 SX
I would expect "1.6" or "SX" to show that record, but it doesn't. Only if I enter the full text "Engine 1.6 SX"
- Filtering by text fields no longer uses strict matching
We use essential cookies to make this site work, and optional cookies to enhance your experience.