27

Okay, this may take a while, but first, read my Low Search Primer. Now you know searching is simply filtering entries by keyword. Low Search uses its collections and their indexes for high quality keyword filtering. In a Low Search form, you can use an input field with name="keywords" to trigger filtering by keywords. Keyword filtering The Keywords filter ...


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 ...


7

The "You are not authorized to perform this action" error in this case was caused by users using their browser's back button while testing the form. Adding the secure="no" parameter to the exp:low_search:form tag fixed the problem: {exp:low_search:form secure="no"}


7

For the record, I know devot-ee uses Low Search for searching only. The filtering you mention is done by a custom add-on they have developed internally. But that doesn't mean you can't achieve something similar with Low Search; you just have to approach things a bit differently. First, you need to create a Low Search form on the results page. You then add ...


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

It works fine with checkboxes. For native checkboxes {option:value} and {option:label} will output the same thing. For the P&T Fieldpack, each one will correspond to the option : label.


4

The main problem here is this: keywords="{segment_3}" You probably don't have keywords in the third segment, but an entire encoded query. You're feeding that query as keywords to the URL tag, essentially encoding it twice. If you use the URL tag and you want to work from an existing search action, use query="{segement_3}" to pass all the details from the ...


4

If you goto Admin > Channels Administration > Channel > Edit Preferences and set the comment path to the proper URL (i.e. {site_url}/blog/comments ) you can use the {comment_url_title_auto_path} parameter also. It can be easier then doing conditionals for each channel you might be searching through.


4

Short answer: Nope. Slightly longer answer: native search, Super Search and Low Search all use the Channel module in some shape or form to display search results. Combining channel entries with other content types in a single tag is currently very cumbersome, if not impossible. Basically, EE's current API simply isn't built for that sort of thing. You'd ...


4

Yes. From the docs: Low Search v2.4+ can also add category information to the index, making entries searchable by keywords present in their categories. Just like the regular channel fields, you can add weight to the category name, description and any of the category custom fields. Note: if you’re using ExpressionEngine 2.7+, making changes to a category ...


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

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

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

This is a tricky issue. Low Search sits 'on top of' the native Channel Entries method. It optionally executes some non-native filters (like keywords, ranges, search:title, etc) and feeds that to the channel:entries method, which takes care of any native filtering (category, status, search:channel_field, etc). That means that before calling channel:entries, ...


3

Firstly, check if your collection 'nieuws' has weighted fields. At least one of the fields in the collection should have weight of > 0. A weight of 0 means the field is not added to the index. Secondly, you can simplify your tags somewhat. You've already got the collection and search_mode parameters set in the Form tag, so no need to repeat them in the ...


3

The PXX is the offset of the total results & the limit set within the tag. So if you set a limit=20 in the low_search:results tag, page 4 would be P80. low_search:results acts just like the channel:entries tag, so you can use any of those parameters to tweak your pagination. {exp:low_search:results query="{segment_2}" limit="20" paginate="...


3

The answer is to use the Low Search URL tag, which can produce a human-readable ACT URL with the keywords as a param. http://gotolow.com/addons/low-search/docs/tags#url-tag


3

Yes. Having a query="" parameter in the Results tag will trigger no results if the parameter is empty or invalid. Omitting the parameter altogether will allow the Results tag to show all entries. So, this will return no results if {segment_2} is empty: {exp:low_search:results query="{segment_2}" ... } And this will show all results if {segment_2} ...


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

Couple of things here. I don't think you need the Preparse option as Jeremy suggested, as you can filter by country/department ID, not by their actual names. Here's what to do: Results tag Use something like this in your Results tag: {exp:low_search:results channel="careers" query="{segment_3}"} code to display careers here {/exp:low_search:results} ...


3

No, there's no hook, but depending on the amount of data you want included, you can get the data included in searches (be it native EE, Low Search or SolSpace search). I had the same issue with Expresso Store that the modifiers (colour/size) didn't appear in the search results - only SKUs were included by default. You'll need to have some sort of fieldtype ...


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

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 ...


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