Support archive

Custom field value ignored after Datagrab import, need to resave first

stevieg_83 10 Feb 2014 11:33 problem, complete

Low, I thought this was a Super Search issue and so started to implement your search module. However I'm finding the same thing http://expressionengine.stackexchange...

Beginning to think it's not either search module to blame but can't understand why resaving the entry makes a difference?

Replies

1. Low 10 Feb 2014 11:57

   How is the field value ignored? Using the Keyword filter? Or the Field Search filter?

2. stevieg_83 10 Feb 2014 12:17

   field search filter.
   
   

    
    {exp:low_search:form result_page="search/results" query="{freebie_3}"} 
   
           <select name="search:cf_dog_gender"> 
                    <option value="">Any gender</option> 
                    <option value="Male">{lv_dog_male_{freebie_1}}</option> 
                    <option value="Female">{lv_dog_female_{freebie_1}}</option> 
            </select> 
    {/exp:low_search:form} 
    

   
   
   The results return both genders.

3. Low 10 Feb 2014 12:22

   I can imagine that "Male" would return both "Male" and "Female", as the former is a substring of the latter, and the Field Search will, by default, always search for substrings.
   
   Try using this as your options:
   
   

   <option value="=Male">...</option> 
    <option value="=Female">...</option>

   
   
   Or you can add the parameter name to the exact="" parameter (either a hidden field, or set to the Results tag):
   
   

   exact="search:cf_dog_gender"

4. stevieg_83 10 Feb 2014 17:46

   ah, of course. Not sure why that's the issue with SS though but not really your concern :)
   
   This works great in this instance so probably easier to roll that out.
   
   Thanks.