Hot answers tagged

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

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

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


4

To identify the categories selected in low search, we use low search variable low_search_category In low search form, You need to select your query {exp:low_search:form query="{segment_3}"} Use low_search_category to identify category you searched. <select name="category[]" id="type" class="form-control selectpicker show-tick" title="Choose One" data-...


3

Super Search has fuzzy searching, which basically means plural/singular matching, "sounds like" matching and some spelling matching. However, as far as I know, this is limited to English only. A solution that would work for both Low Search and Super Search, is to have a hidden field with searchable keywords per entry, which you'd have to populate manually. ...


3

My reccomendation here is to create a dedicated relationship channel. It's a bit complex at first, but I promise a simple concept. That channel looks like: We use this structure, but with all these extra fields for extendability. The kind of logic flow is using this channel to link two or more entries. So it looks like you have people and vehicle listings....


3

The native EE Search module does not have the ability to search either the Title or any custom field based only on the first letter contained therein, no. It also contains no hooks to allow you to manipulate the search query. Just buy Low Alphabet and be done with it!


3

Update Since the VMG Chosen Member is a custom field that just captures the member_id and doesn't override the author_id of the entry, you could use the search parameter with Low search to find the correct entries: {exp:low_search:form collection="fsr" search_mode="all" search:fsr-customer="{logged_in_member_id}" result_page="search/...


3

There isn't really an elegant way to do this... All ways are "creative". Using the conditional to exclude is the easiest way IMO because it only affects that template.


3

I set up a status for "hide from search" or similar. This means that the results aren't shown as my search is only showing open entries. Of course, it does mean that you need to set any entries tags that are meant to show these entries to include the status as well as just showing those with a status of "open".


3

With entry_date you can use a start_on and stop_before parameter in your channel loop but cannot do an equivalent for custom date fields. You have two good options here. The first is to use the {exp:query} module in place of a channel entry loop, and the other is to use a third-party search module such as Low Search If you opt for the query method you ...


3

Maybe there's a better native ee way without enabling php, but I would use Stash or Low Search. Use Stash (set_list) to set a list of all your search results and then you could have more control over outputting for each tab/channel (using get_list). When you set your list set a variable for channel (i.e.: "my_cached_channel_var"), and then when you output ...


3

If you aren't going to manage the content with EE, you won't be able to search the content with EE. Either move your content to channels as suggested (I've had sites with channels with two fields - title and page content, the latter holding whatever HTML is necessary), or implement a Google Custom Search that will search your rendered pages. Low has a nice ...


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

WOW!!! I feel a little embarrassed on this one. I will still post the answer since I have seen several other posts in various sites, be it EllisLab support, here, or others. Another fine example of forgetting something very simple and why reviewing the docs on a regular basis is a great idea. ;) Adding the following allowed the search of the entry inside ...


3

You've almost got it. {count} is the current count of the displayed entry in the tag's loop. Think of your entries as a numbered list, the {count} is the position in the list. {absolute_results} however is total number of entries in the "list", so you want to build your conditional from it. Here is one example using your markup: {if count == 1} <h4&...


2

Reefine is awesome. Used it a couple of times. However, I have found (And it is mentioned in the docs) that if you are using it on a ton of entries, it can be a little slow. You may also be able to harness dynamic parameters. You can filter a lot down with that. Or even perhaps the search:field_name= Docs here and use segment variables to filer down. Hope ...


2

I've not tried it, but have you considered Reefine? http://devot-ee.com/add-ons/reefine


2

There are two search Modules that offer lots of flexibility. You'll need to dig through docs to make sure they match exactly what you need to do... Low Search http://gotolow.com/addons/low-search Solspace Super Search http://www.solspace.com/software/detail/super_search/


2

Yup: {channel}. Note that all of the Channel Entries variables are available within the Search Results tag.


2

You can't. Global variables (which LV are, essentially) aren't searchable by the native Search module, nor by any 3rd party search add-on that I know of.


2

If you are asking what I think you're asking then you would need to set the base path for each channel within the channel's preferences.


2

Not sure why there are channel:entries loops in this template - I'm assuming you've inherited this site from another developer? Start by removing the opening and closing channel:entries tags.


2

Check out Preparse from Solspace. It's a free extension that allows you to run a template against your entries when you save them and store the output in a field. Low actually talked about this on his blog in the context of Low Search, but you can use the same principle for the native search module as well. I recommend taking a look at the blog post and ...


2

The native search module, and in this case the exp:search:search_results tag, expects a URL like this, assuming the tag is put in the search/results template: domain.com/search/results/HASH The hash is supposed to be at least 32 characters long (alphanumeric). If the hash is not there, the error is triggered. The hash is used to look up a submitted search ...


2

Have you considered the reverse? e.g. start at the brand channel and get the parents (e.g. products)? Might be more easy. Grid is quite new and the relationship field also was recently changed (2.6) search and categories are not mature i guess (Relationship field tag parameters). Have you also tried Grid search:column_name=? edit as noted in the comments ...


2

The {excerpt} variable, which is defined in the Channel Preferences, consists of the first 50 words from the field specified (see docs). If you need more than that, you're probably better off using the regular custom field notation and using something like Hacksaw or TruncHTML to limit that field to 200 words. To make sure the {excerpt} is defined correctly:...


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