I've used this module just fine for integers, but don't have floats show up when I define a new range facet ... thoughts on implementing?

I'd also like to use computed fields - perhaps treating them as text?

Any pointers would be appreciated.

Comments

dillonm’s picture

dillonm commented
Category: support » feature

Well, here's how I was able to add floats and number-based computed fields. I realized it didn't really make sense to have textual computed fields. All I did was add additional checks on the field type to include floats and computed fields. Both are work as expected, despite a warning I get when I create the facet ranges.

In fsrange_number.module change the if statement in the function number_fsrange_fields() from:

if ($field['type'] == 'number_integer' || $field['type'] == 'number_decimal') {

to

if ($field['type'] == 'number_integer' || $field['type'] == 'number_decimal' || $field['type'] == 'number_float' || $field['type'] == 'computed') {

Additionally, if you wanted to add textual based fields, have a look at the if statement in the function text_fsrange_fields() in the file fsrange_text.module. To find out the machine name type of the field, have a look at your db. If you've already created a field for it, it'll be in the "type" column of content_node_field.

Would be great to get support for floats and computed fields in this vital module.