9

Generating the checkboxes Take a good look at what you're trying to achieve, and what you're actually doing. You want a list of checkboxes that contains all options for a given Checkboxes field. So, for example, say your mbr_fieldname contains 3 checkboxes for primary colors. In that field's settings, you've added the three colors in the Multi-Select ...


5

If Low Search is giving no or not all results, check the following things: Native default parameter values negating search results The Results tag extends the native channel:entries tag, so default filtering is in place: status will be limited to open only; show_future_entries will be set to no; show_expired will be set to no. In 9 out of 10 cases, the ...


4

Couldn't you just use a Snippet for this? It would contain the markup and code used inside a tag, which you could re-use with multiple tags. For example: {exp:low_search:results ... } {sn_entry_list} {/exp:low_search:results} {exp:channel:entries ... } {sn_entry_list} {/exp:channel:entries} An so on.


4

The way you're doing it now -- getting the entry IDs from the search and passing them to the low_alphabet:entries tag -- would be the way to do it. There isn't some secret way to seamlessly integrate the two at the moment. I realise that Low Search could do with a single :entry_ids tag to make this easier, but sadly that's not possible at the moment due to ...


4

It's a known bug and will be fixed in the next version of Low Search. To fix yourself, open up /low_search/libraries/Low_search_index.php (v3.0.2), and look up line #79, which reads: die('No collections found'); Change that to: return FALSE; ...and you should be good to go.


4

So thanks to Low stepping in and doing some testing with me, we worked out that the problem was down to an extension hook for Structure that was messing up ALL pagination across the site. Low performed the following sql query to find the hook in question: SELECT * FROM exp_extensions WHERE hook = 'channel_module_create_pagination' and then removed the ...


4

I'm not sure any of the options you mentioned other than Google will actually index the content of PDFs. You may have to create an entry for each one with the text content. Maybe there's an add-on that will grab the text out for you (I know it's possible). I've used Low Search and Super Search. Both are excellent but I'd probably go with Low.


4

I'm using Low Search, it's really more powerful than the native EE search, very well documented, nice user interface. You can parameter the weight of each field, categories of the each collection of search. Easy to integrate in a project. You can parameter complex search. And the Low support is very good and efficient.


4

As I told you earlier today, this is not a Low Search issue, but a conditionals parsing issue. If you turn on Template Debugging, you'll see the opening tag just before it is actually executed. It will look something like this: {exp:low_search:results {if embed:author_id}author_id=""{/if} ... } That is what's executed, and what EE uses to set the internal ...


4

Should be possible using Low Search's Distance filter. If you're using a search form, add a hidden input field that contains the lat/long values of the logged in member, eg: <input type="hidden" name="distance:from" value="{cf_member_lat}|{cf_member_long}"> ...making sure the values are replaced with their actual numerical values. Then, set the ...


4

Keyword searches with Low Search are diacritic insensitive. That is to say, both the collection index and given search terms go through an algorithm to strip them out or replace them with unaccented equivalents. LS uses EE's native $foreign_characters array for this, located in /system/expressionengine/config/foreign_chars.php. For example, take the word ...


4

You use plugin with the same parameters. So EE cached it. Try to add random {exp:stash:set name="sorthead" random} {/exp:stash:set} or change name.


3

With Low Search, you do not "form a URL", but rather you create a search form that you can submit, which will generate the URL for you. How you create the elements in your form depends on what types of filters you will need and how you set up your channels and fields. For the alphabet, you can use the Field Search filter, but you'd have to hard-code the ...


3

I finally got this working (Low Search working with Stash static cached homepage)!!! I added the following rule to my .htaccess, to get it to really really ignore POST requests. I'm not sure why this works (maybe it's my server environment? I'm on a Nexcess EE-Optimized plan). So I added the following RewriteCond RewriteCond %{THE_REQUEST} ^(GET) And ...


3

You should take a look at Low Search Store. This adds compatibility with Expresso Store to Low Search - https://github.com/low/low_search_store :)


3

Yep, that would be a job for the Categories filter. For each group of categories, use a category:group_name parameter name to combine AND and OR matching. For example: {exp:channel:categories category_group="1" style="linear"} <label> <input type="checkbox" name="category:group1[]" value="{category_id}" {if category_id IN ({...


3

The cause turned out to be the creation (and rebuild) of the indexes not including category information. This build also included Publisher and included an extension to add Publisher support to Low Search, which it seems doesn't support categories - I've created a ticket with the developer, so hopefully this will get resolved soon.


3

It's rather awkward that hook is being called every time. Low Search uses the hook to update collections when a channel field is deleted; it's the only hook that can be used to for that action. However, the same hook appears to be called for other reasons too, but LS won't take any action there. You can disable LS for that hook only by setting the enabled ...


3

When I need to use LowSearch with Store I usually also use Solspace PreParse in that channel too. To set this up you will need to do a few steps. Create an additional textarea field in your field group store_detailes_parsed make sure that it searchable. Create an additional template in your partials/embeds folder _partials/store_search In the newly created ...


3

Did you mark the Grid field as searchable after creating entries? If so, you need to re-save those entries in order to populate the exp_channel_data table with searchable data, which Low Search in turn uses for its collection index.


3

Low Search doesnt work, Free Form doesnt work, Free members - basically asks if your sure you want to login as some things might not be secure. These add-ons usually use what you have configured in your "Admin > General Configuration > URL to the root directory of your site". You can also set/override the General Configuration settings using the /system/...


3

@Blatant is on the right track, but the code example isn't optimal. Since the Results tag builds upon the native exp:channel:entries tag, you're able to use the native Relationships Field options. So, to get to an entry's parent, use something like this: {parents field="relationship_field"} {parents:url_title} {/parents} Use that to compose the URL ...


3

When not using encoded queries, Low Search will try and add the GET vars to the pagination URLs automatically. If that fails, you can always add the query string manually, by using this as your pagination links: <a href="{pagination_url}{low_search_query_string}">


3

First of all, the general setup of your search form could be better to work correctly with Low Search. You’re targeting 2 different collections using two different fields. Instead of that, I’d opt for a single input field and a drop down to select the collection. Something like this: {exp:low_search:form result_page="zoek/vac-resultaten"} <input type=...


2

Your example actually worked fine in a test I did. But it could be that the curly brackets are encoded to entities, so the regex doesn't actually match. You could try this: {exp:low_replace find="(\{|&#123;)[\w\-]+?(\}|&#125;)" regex="yes"} {low_search_excerpt} {/exp:low_replace} If you're just filtering out those image tags, you could also ...


2

Stephen is right. The search_mode parameter only applies to keyword searches, so you can safely remove it. The same goes for the min_score parameter. And since the two input fields are single values, you can remove the require_all parameter as well, as that only applies to multiple values. And since you're using GET variables instead of the encoded query, ...


2

OK, So I had to wrap the entire call in a {exp:stash:parse process='end'} tag and then call the values with just {stash:market_ids}. Now seems to be working.


2

Simply ordering by the Low Events channel field would do the trick, so try: orderby="my_low_events_field" sort="asc"


2

Low Search's Distance filter takes lat/long values as from and to values to calculate the distances per entry. If you want to use addresses, it's up to you to transform that into lat/long values, before sending that data off to Low Search. This Google search will give you a nice start.


2

Low Search's Form tag doesn't take any filter parameters, at least not since v3. You're defining 2 filter parameters (collection and search_mode) on the Form tag, but you should add these parameters to the Results tag or add them as (hidden) input fields in side the Form tag. Also, I'd recommend using name="keywords" (utilizing the Keywords filter) instead ...


Only top voted, non community-wiki answers of a minimum length are eligible