Hot answers tagged

19

I have a comment in the Search module docs on this. Inside your Analytics tracking code block, you can do something like this (change the segment conditionals to match your specific case) var _gaq = _gaq || []; _gaq.push(['_setAccount', 'UA-XXXXXX-X']); _gaq.push(['_trackPageview']{if segment_1 == 'search' && segment_2 == 'results'}, ['/search/...


16

This is a bug (see bug report #19102). It's because the excerpt is being filtered through PHP's preg_quote(). You can either remove the preg_quote() from line 1507 of mod.search.php for now and just leave it as $excerpt and hope you don't have anything that looks like a replacement pattern in your search excerpts, or just show the custom fields themselves in ...


15

I actually had to do this recently. It's not too difficult to grab all that Matrix data, concatenate it, and save it to your field. First, backup your database (!). Next, create a new template, enable PHP on it, then put this in it: <?php $this->EE =& get_instance(); $channel_id = 1; $field_id = 20; $matrix_cols = array( 'col_id_1', '...


9

If you're going the category route, you could use the native Dynamic Parameters, possibly with Dynamo, to filter entries. However, using Low Search (or Super Search), you can also filter by Relationship fields (including Playa fields), so that would be more flexible. For example, you can use inclusive filters, allowing to mimic category="1&2&3" as ...


9

You're correct that the native search:field_name param only works on custom fields and not titles, annoyingly, so we do need an addon to do this. Stash is overkill for this use case though and requires a lot of code to get the (fairly simple) job done. I'd use another fine Croxton product instead: the Search Fields Plugin, just wrap it around your {exp:...


8

You cannot use OR clauses inside of a {exp:channel:entries} tag. The best way to handle this would be to write a custom plugin that would do the selection, or use the Active Record plugin. You should not use the built-in Query plugin because it unsafe to pass user-submitted values (such as {segment_*} variables) to this plugin, while the Active Record ...


8

Do away with the <ol> and use the variable {absolute_count} instead.


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


6

Anyone that's not logged in is part of the "Guest" group: Members > Member Groups > Edit Member Group (Guest) Should be here: /system/index.php?S=0&D=cp&C=members&M=edit_member_group&group_id=3


5

I think you are right, that isn't possible with a core EE install. Low search and solspace's super search do that, but it also seems like this free add-on does it too in a very limited way: http://devot-ee.com/add-ons/search-fields


5

Have you tried using the query module instead of the channels module? I've done a lot of fancy stuff. You could also try dynamic parameters instead of search. CreateSean's response is a good way to go through it as well :)


5

This is a bug in EE 2.7.3 when Secure Forms is disabled. It is currently marked as "fixed in upcoming release". (Bug tracker link.)


5

Take a look at Members › Member Groups › Guests › Access search utility. Should solve your problem


4

"Super search" supports human-readable ( and therefor analytics-friendly ) queries: http://www.solspace.com/docs/addon/c/Super_Search


4

It sounds like using Pixel & Tonic's Playa module might be your best bet. It has tags for pulling entries based on relationships.


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

Actually, the "Is field searchable?" checkbox relates only to the native Search module. The search parameter on the Channel Entries tag is only the most basic way to handle searches in EE. Your other native option is to use the Search module, specifically the Advanced Search Form. But it is somewhat limited, and its URLs are not bookmark-able (as they ...


4

Low is totally correct, but I thought it might be worth adding some info about why this is necessary and how you might implement his solution. The reason the counters on your <ol> appear 'off' is that they are automatically generated from the HTML document, which has no awareness of your pagination, so as each page is a new ordered list the first ...


4

You could nest another conditional: {if total_results < 3} {if count==total_results} {embed="includes/homepage-properties"} {/if} {/if}


4

EE doesn’t have a search index; it just queries exp_channel_data directly on every search. The issue is that Matrix primarily saves its data in exp_matrix_data, not exp_channel_data. It’ll dump the content from any columns listed as Searchable into exp_channel_data precicely so that it’s discoverable by EE search, but only when an entry is saved. It does ...


4

This is quite simple, and why I prefer EE over other systems. It easily allows you to customize your markup anyway you want to. The {exp:search:simple_form} tag has two parameters to let you target and style the form with CSS (Docs). form_id & form_css. Re: placeholder text for the input, you can add the placeholder HTML5 attribute to the form. If you ...


4

Your code looks correct. Could it be that you only have a single page of search results? I see you have a limit parameter on the tag, but it actually does not accept that parameter. The number of search results per-page is actually determined by the results parameter on the Search Form tag which sends you to the results page.


4

It's a bug in EE's native Search module. Bug reported here: https://support.ellislab.com/bugs/detail/19828 Here's the fix: Starting in line 1290 of system/expressionengine/modules/search/mod.search.php REPLACE if ($query->num_rows() == 0 OR $query->row('total_results') == 0) { return ee()->output->show_user_error('off', array(lang('...


4

You might use "Low Alphabet" See the tags from here: http://gotolow.com/addons/low-alphabet/docs/tags For last_name, just pass parameter orderby="last_name" within {exp:low_alphabet:entries}


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

By default, you cannot do this, however, there is a simple extension you can use called Categories to Text to save your categories into text fields automatically. If you set those text fields to be searchable, then essentially you are searching the categories. And you can choose to hide those text fields on the backend by modifying the the publish layout. ...


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

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

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


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