I only set this as a bug because I've been following instructions very closely, and I'm told I should have sortable fields. It is entirely possible I'm missing something. I have no sortable fields, even though I have the string/integer fields indexed. The Search Modules I'm using are:

Database search 7.x-1.2
Search API 7.x-1.11
Search facets 7.x-1.11
Search ranges 7.x-1.5
Search sorts 7.x-1.5+1-dev
Search views 7.x-1.11
Current Search Blocks 7.x-1.3+2-dev
Facet API 7.x-1.3+2-dev
Facet API Bonus 7.x-1.1+7-dev
Commerce Search API 7.x-1.3+1-dev

My currently indexed fields are:

Content type -- String -- 1.0
Title -- String -- 1.0
Date created -- Date -- 1.0
Date changed -- Date -- 1.0
Product Tags -- Taxonomy term
Product Ref -- Commerce Product
Item Type -- Taxonomy term
Weight Sort -- Integer -- 1.0
Product Ref >> Price >> Amount (decimal)(Min) -- Decimal -- 1.0
Product Ref >> Price >> Amount (decimal)(Max) -- Decimal -- 1.0
Title (Fulltext) [search_api_aggregation_1] -- Fulltext -- 1.0
Product Tags (Fulltext) [search_api_aggregation_4] -- Fulltext - 1.0
Item Type name (Fulltext) [search_api_aggregation_5] -- Fulltext - 1.0
Product tags >> Name -- String -- 1.0
Proudct Ref >> Serving Size -- String -- 1.0
Product Ref >> Portion Size -- Fulltext -- 1.0
Item Type >> Name -- String -- 1.0
Product Ref >> Price >> Amount (decimal) -- Decimal -- 1.0

At this point, I'm only trying to get Title, and the min and max price fields sortable. Please let me know if I'm missing something, or if I can provide any extra information or testing.

Comments

vintorg’s picture

In search_api_sorts_index_select() in search_api_sorts.admin.inc, I'm getting an empty result set from:

$results = $query
    ->entityCondition('entity_type', 'search_api_sort')
    ->propertyCondition('index_id', $index->machine_name)
    ->propertyOrderBy('weight', 'ASC')
    ->execute();
vintorg’s picture

My fields now show up after commenting out the block of code suggested by Ravenight:
https://drupal.org/node/2202093

criz’s picture

Status: Active » Closed (duplicate)

Yes, this should be the same bug. Let's mark this one as duplicate.
https://drupal.org/node/2202093