Bug #33298
Facet option gets removed, if it has value 0
| Status: | Closed | Start date: | 2012-01-18 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | Ingo Renner | % Done: | 100% |
|
| Category: | Frontend Plugins | |||
| Target version: | 2.0 | |||
| TYPO3 Version: | Has patch: | |||
| PHP Version: | Tags: | |||
| Votes: | 0 |
Description
I modified my schema with a field that stores integer values.
I wanted to add a facet for this field, but a facet option get's removed if it has the value 0 (which is possible in my case, since i have an integer field).
I've attatched a patch for this, because i think there's a wrong type comparison in the simple facet renderer. Please review (maybe i'm doing something wrong?), thanks!
Associated revisions
Fixed issue #33298: Facet option gets removed, if it has value 0
Fixed issue #33298: Facet option gets removed, if it has value 0
History
Updated by Ingo Renner over 1 year ago
- Assignee deleted (
Ingo Renner) - Target version deleted (
2.5-dkd)
Please do not set assignees and/or target versions. These fields are "our" fields to plan the roadmap. You can assign an issue to yourself though if you're working on it.
Updated by Ingo Renner over 1 year ago
... also, do not(!) change the schema, use dynamic fields instead. Otherwise you'll have to make those changes over and over again when updating the extension, specifically if the extension update requirers a schema update.
Updated by Ingo Renner over 1 year ago
- Category changed from Solr TYPO3 Plugin to Frontend Plugins
Updated by Ingo Renner over 1 year ago
- Status changed from New to Accepted
- Assignee set to Ingo Renner
- Target version set to 2.0
Updated by Ingo Renner over 1 year ago
- Status changed from Accepted to Resolved
- % Done changed from 0 to 100
fixed in dkd-EAP r 90929
Updated by Ingo Renner over 1 year ago
- Status changed from Resolved to Closed