In its current state, the module doesn't support fields, which should be fixed before releasing the module, especially since we can't have support for taxonomy terms otherwise – a big drawback for any search.
fago suggested in #939460-1: Views integration troubles to use entity_metadata_get_properties() for extracting the properties, since this will also return fields. I will have to check it out.
@ fago: Is there any reason why, for just reading the available fields, I shouldn't use that function instead of an empty wrapper? (Apart from having to rewrite one of the ugliest functions in the whole project … ;))
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | search_api_fields.patch | 668 bytes | fago |
Comments
Comment #1
fagoHm, I think it does already support fields. Probably the problem is only the specification of the right bundle. The attached seems to work for me basically.
Don't know whether this is taken into account for views now automatically? Probably it should.
Comment #2
drunken monkeyWow, thanks a bunch, I don't think I would have thought of that! And yes, it seems I did the Views thing well enough that this now also works for views.
So, patch committed, thanks again!