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

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

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

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

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

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

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


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

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

Have you played with the category_indicator= parameter to make sure it's matching the way you are indicating your categories? I find it's always much more robust when using category url titles.


1

Can you try rebuilding the Super Search Lexicon? (go to: SuperSearch > Utilities). I have a feeling that Super Search only updates this if you add the entries through the Control Panel.


1

replace : $this->EE->pagination->get_template(); with: $this->EE->TMPL->tagdata = $this->EE->pagination->prepare($this->EE->TMPL->tagdata); Updates: I don't use Super search before, I just tell you what you must change. if you use $channel->pagination->get_template() then change it to $channel->pagination-&...


1

Ahmad, thank you for your response. I edited what I originally stated above to move it into an actual answer. The fields did need to be checked again to verify that they were truly searchable. However, now that they are I have found that some fields will be included in the search results while the categories do not get included in the search. From my ...


1

a lot of custom fields here. I don't know about Super Search , but for EE search you can search in Matrix data if you mark the field as searchable as mention here; Matrix & Simple Search I hope this will help you. Regard's.


1

I had to do this before and there doesn't seem to be a way from the interface. I did it by going into phpmyadmin and then into the EE database.From here search for the exp_super_search_terms.Once you find the table you can use the export function and export the search terms to CSV or what ever you want.


1

After some testing, both the Super Search and the native EE Simple Search form had the issue. Here is the explanation and solution: Your channel preferences indeed had a custom field set as your excerpt field, but this setting was likely not registered in the database. Re-saving the channel preferences should save the excerpt value in the EE database, and ...


1

My apologies as it turns out this issue wasn't completely related to Super Search. There was also suggestive search results being powered by the following code: <?php $term = $_GET['term']; ?> {exp:ifelse parse="inward"} {if group_id == '20' OR member_id == '79' OR member_id == '9' OR member_id == '113' OR member_id == '129'} [{exp:query ...


1

If you only have a single channel that you are trying to exclude I often find it easier to use the not parameter to your template tags. The following would not show any entries from a channel with a short name of "excluded_channel" or any entries that have a status that is set to closed. {exp:super_search:results channel="not excluded_channel" ...


1

You can set specific channels to limit results on your exp:super_search:results tag like: {exp:super_search:results channel="news|another_channel" limit="20" hightlight_keywords="strong" } (see solspace docs here, and under "why does it work that way" heading). Setting the channel parameter here should prevent results from showing up from the ...


1

My guess is that if you instantiate the class and it's not working, you need to also dive into their code to see why you aren't getting any results. If I had to guess, it's because there are no template parameters set. You can programmatically set parameters like so: ee()->TMPL->tagparams['param_name'] = 'some value'; Or in versions of EE prior to 2....


1

As per the comparison tool at http://www.solspace.com/software/detail/super_search/ Solspace suggest that Low Search would be the better tool for Grid or Matrix searching. Details about Low Search can be found at http://gotolow.com/addons/low-search


1

First of all, Matrix data columns need to be set to "searchable" for its data to be stored, as a concatenated string, in exp_channel_data. Once that is set up, searching in this Matrix field using Super Search is limited since Super Search will only look for a string match between your search and what is stored in exp_channel_data. In other words, there are ...


1

Consider checking out Stash instead of Transplant using it's set_list & get_list's -> match / against params. (I probably need more info to help with the regex if any) See this wiki article for Filtering Lists with match against. Note: in that example Mark is manually creating the list but, you'd do it with Super Search (or channel entries tags etc.) ...


1

Ended up creating tags for each of the form areas. Then using a jquery plug-in to help load in my information via ajax.


1

In Low Search, if you want the Matrix data to be searchable via Keywords, you'd have to use the same approach as Super Search: set the columns as "searchable". However, you can also use Low Search's Field Search filter to target specific Matrix columns, regardless of whether they're marked as searchable or not. Both searching methods will return the entry ...


1

If you set your Matrix columns as "searchable", data in the Matrix field get saved in exp_channel_data, which Super Search can use in its searches. You could then search in your Matrix field for the word "Pine", for example, and if there is a match, use regular Matrix tags to pull out the specific row containing "Pine".


1

I cannot comment about Super Search, but Low Search can handle this using the Categories filter and its group syntax. In your case, you could use name="category:functions[]" for the one group, and name="category:materials[]" for the other. See also the second part of the Categories filter example here.


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