7

I don't know why this didn't occur to me before, but you can use {absolute_results} inside the Super Search tags. So, the lesson here is, if you need to use the channel entries style "search:field=" parameter to filter entries (NOT the Super Search "search=" parameter) and you need an accurate number of items returned, use {absolute_results} in place of {...


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

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

The XID (csrf_token in EE 2.8+) is used in POST forms to secure form submissions. A quick test shows that the XID isn't required for GET form submissions, so you can remove this from your GET form without running into issues. If you're using {exp:super_search:search} in your search form, the XID field is provided for you (it's a hidden field), and the only ...


3

The error happens because, sometimes, the conditionals brakes after a stage of parsing. Example: {if {x} != ""} If, x is empty, the conditional will be turned into: {if != ""} Which doesn't make sense. So, you can use: {if "{x}" != ""} Or the what the Template Class calls "short conditionals": {if x} I suggest you to try: {if "{...


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

For the first issue try changing <option val="">Select Category</option> to <option>Select Category</option>... specifically removing the val="". I took a look at the Solspace Supersearch docs and I don't see that keyword is required. So try taking it out.


3

Adding entry_id="{entry_id}" to {exp:primary_category} fixed it. This is not required in channel:entries but is required in Super Search results.


3

Look at me. Found the answer on my own by poking around in EE-settings. It seems that Member Groups > Guests does not have the power to search by default. Set to "Yes", and you don't get that error anymore. Shame on me.


2

You need to make sure the field is set to "searchable" in the field settings page but you should be able to get the two working together. Super Search has limited support for Pixel & Tonic's Playa add-on. You can perform regular searches (excluding exact, ranges, etc) on entry titles within Playa fields, as long as the field(s) are set to ...


2

It was an issue with url paths that weren't changed in the migration. Rookie error but solved.


2

This tutorial might get you started http://blog.aaronmbushnell.com/post/23434803999/creating-an-ajax-filter-using-solspace-super-search If it's just 2 groups you might also consider using dynamic parameters: http://ellislab.com/expressionengine/user-guide/modules/channel/dynamic_parameters.html


2

Since I'm not a big fan of commenting out whole bloc of code my take was to change this line if (isset($this->cache['keywords'][$this->settings['field_id']])) and make it look like this if (isset($this->settings['field_id']) AND isset($this->cache['keywords'][$this->settings['field_id']])) I had this issue only when saving an entry from ...


2

I am experiencing the same problem where it seems to happen when "Is field searchable?" is enabled within the field settings containing the Matrix field-type (not sure why??!)... I found a solution by changing line 7595 from $select .= ', field_id_'.$fields[$key].' AS `'.$key.'`'; to $select .= ', cd.field_id_'.$fields[$key].' AS `'.$key.'`'; Within mod....


2

In my experience, {super_search_keywords} won't parse outside the results loop, despite what SolSpace's documentation says.


2

as I read in the document http://www.solspace.com/docs/super_search/results/ The Super_Search:Results tag displays the entry results from a search query. And since search queries in the URI (and from POST searches) are human-readable (template_group/template/search&keywords=bird&summary=is+the+word), users can bookmark result pages, along ...


2

Super Search works best as a POST form. GET forms are more limited. As mentioned in the docs (http://www.solspace.com/docs/super_search/post_get_or_template/): GET does have it's limitations. As mentioned above, it is impossible to pass search arrays via GET. Try using method="post" instead for your form.


2

Try adding Snaptcha to your supersearch form. It really is very good at preventing automated form submissions. Although supersearch is not supported natively, it is easy to add to any form by just adding the following tag to your template in between your form opening and closing tags: {exp:snaptcha:field}


2

SuperSearch has been obsolete for quite sometime (didn't make it past v2) and will not run on newer versions of EE. Try Low Search.


1

Maybe the docs are just out of date. I found that it worked when I moved the tag within the results loop.


1

When there are multiple categories, {super_search_category} will display the entire category string. In this example, if you have search&category=auckland+photo, then {super_search_category} will parse to: auckland+photo or, in some setups/EE installations, auckland photo To use the individual selections for something, you'll need to break up ...


1

Did you try these conditionals and it didn't work? I would expect that or channel_short_name to work just fine in a conditional. In my test using Supersearch 2.1.3 and EE 2.7.1 this conditional works as expected: {exp:super_search:results} <div class="search-result"> <h3>{title}</h3> {if channel_short_name == "articles"}...


1

The problem with your second block of code is that the option values for the category select field is a URL, when it should be category data, such as a category_id, category_url_title or category_name. Let's say your first search with the first dropdown sends you to http://mysite.com/event/results/search&category=sports On this result page, you can ...


1

Thanks Robson Sobral you set me on the right track the following fixes the conditionals {if "{super_search_keywords}" !=""} <h1>{super_search_keywords} Jobs {if "{super_search_job_location}" !=""} In {super_search_job_location} {/if}</h1> {if:elseif "{super_search_category}" !=""} <h1>{super_search_category} Jobs {if "{...


1

First, I would recommend using the excellent IfElse plugin to reduce load with advanced conditionals. To do this wrap your entire conditional in these tags: {exp:ifelse parse="inward"} code goes here {/exp:ifelse} Now onwards, please post the errors you are seeing as that will help us help you. Second, I would start off by simplifying your entire ...


1

Yes. This is documented in the SuperSearch docs. <select name="category[]"> <option value="{category_name}&&">{category_name}</option> </select> All selects will use name="category[]" and option values will have && at the end


1

Now that you have the search form looking better, try looking at your search results tag. Specifically, category[] This field allows users to search on categories. Default behaviour is searching on category names. To switch this to category ID or URL titles, use the category_indicator parameter in the Results tag Do you have the category_indicator ...


1

Per the comments above by new2EE, this was caused by a blacklist setting in EE.


1

You can't order your Super Search results by a function of another fieldtype like that. But wehat you can do is write a custom extension and then use the super_search_prep_order extension hook. The Rating module uses this hook to sniff for an order directive like order=rating. When it sees that, it runs its own routine to order the list of known entry ID'...


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