After digging and trying out module after module I think this one will work great for what I need. The only thing at this point that is still a problem is how to get the "value" to work with exposed filters?

Use Case:
- I am building a real estate site with apartment listings
- Each apartment community may have 1 bedrooms, 2 bedrooms, or 3 bedrooms
- My attributes are
- 1/1 Apartment (1st number is # of beds, 2nd number is # of baths)
- 2/2 Apartment
- 3/2 Apartment
- 1/1 Townhome
- 2/2 Townhome
- 3/2 Townhome
- My categories are
- Apartment
- Townhome
- The VALUE field is where I would like to put the RENT amount. It would be great if we could change this field to an integer field as opposed to a text field.
- I then need the VALUE field to show up as an exposed filter (in between filter) so that I can add it to my search of Min/Max rent.

Does that make sense?

Great work on this module so far!

Comments

podarok’s picture

podarok
🇺🇦 he/him/his
Primary language Ukrainian
Location Ukraine
commented

subscribe

this solution is in my todo list for the project with 800+ categories with 30+ uniq properties for each with 2100000 products at all

i'm thinking about creation dynamic forms or making possible export properties as exposed filters for views

Sylense’s picture

Sylense commented

I actually went a different route to get my desired results but maybe this thread may be what some others need. Instead of going this route I just set my beds/baths & rent as a separate content type, used references, the url reference widget, and configured my views properly to get my desired result. A little more dirty approach but it works and may be more flexible this way.

logicexpertise’s picture

logicexpertise commented

I would like to implement a similar solution for a classified ads site. The site will have categories such as real estate (rent or buy), automobile, household appliances, etc.

@Sylense, can you share more details of your solution?

joachim’s picture

joachim commented

I see several ways to do this as an exposed filter, any of which may be useful.

1: have the attribute as a fixed setting on the filter.
So eg I have two attributes, foo and bar. In the filter setting I select attribute foo and then give a value. As an exposed filter this would allow choosing the attribute value. This has to add two clauses to the query thus:

 (field_data_field_myfield.field_myfield_attribute = 'foo' AND field_data_field_myfield.field_myfield_value LIKE '57' ESCAPE '\\') ))

(Not sure why Views is putting a LIKE rather than an = here but that's another matter.)

1b: Same as 1 but allow more than one attribute to be chosen. In the query this would mean the field_data_field_myfield.field_myfield_attribute = 'foo' clause is one of several with ORs.

2. Expose the attribute as well as the value so the user can choose the attribute from a dropdown or select list and then enter the value.

I'm still at the stage of evaluating this module for a project so I don't have the time to write a patch yet. If I do use it I'll write handlers for the above; if not, that should set someone else on the right track at least :)