Bug #4269
adv search on checkbox can't search on NO
| Status: | Resolved | Start date: | 2009-08-19 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assignee: | Balisky Christophe | % Done: | 0% |
|
| Category: | TCA engine | Spent time: | - | |
| Target version: | - | |||
| Branch: | ||||
| Votes: | 0 |
Description
If I set an advanced search on a checkbox field, I get the appropriate selector (yes/no). This works ok for choosing "yes" -- gets appropriate search results and shows up in the list of applied filters. However, if I select "no" the checkbox field is not considered. In other words, it doesn't show up in the list of applied filters -- and I don't think it provides appropriate search results.
History
Updated by Chris Paige almost 4 years ago
REVISION:
-- My checkbox data is faulty due to a different bug. This made my search results appear wrong on checkbox=NO, even though they were accurate.
-- It looks like any advanced select selection, which has a value of zero (checkbox_no=0 or select_options=0) will make that criteria not show up in the list of filters, even though the search is happening.
Updated by Balisky Christophe almost 4 years ago
- Category set to TCA engine
- Status changed from New to Accepted
- Assignee set to Balisky Christophe
Need mor einfo
Updated by Chris Paige over 3 years ago
Seems like the search results are correct on checkbox = No. However, the labeling for the search filters does not show up (e.g. we get "aucun" if the checkbox is the only search criteria).
In function getListItemTemplate(&$conf), it only reports search filters if ($val). Probably, this should be an is not null condition, instead of a simple boolean, which triggers false when $val = 0.
Updated by Chris Paige over 3 years ago
here we go...
change if($val) to if($this->metafeeditlib->is_extent($val))
Updated by Chris Paige over 3 years ago
- Status changed from Accepted to Resolved