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

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


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

Something like that is not possible with the first party search module. It would be possible to build queries like that with Low Search or Solspace SuperSearch however.


3

AFAIK, there are no tools that would allow Solr search integration. You may consider one of these search tools for EE: Search (included in default install) Low Search SuperSearch There are also tools that integrate Google Search: Low GoogleSearch and Google Custom Search


3

Looks to me like you have a space after your 'URL to the root directory of your site' in 'Admin' > 'General Configuration' settings.


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

Twitter's switch to v1.1 of their API isn't supposed to happen until next month, though this may have been one of their "blackout tests". Definitely API related at any rate. Regardless, CE Tweet is the only Twitter add-on I know of that's currently compliant with the API changes. I would strongly recommend migrating.


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

Simple Search won't natively search categories. Luckily there's an add-on called Preparse from Solspace which will help make it work. Low posted on his blog about using Preparse to add categories into a searchable text field. Though the post refers to using Preparse with Low Search, it would function the same with Simple Search as well.


3

Calendar events do not use regular entry entry_date and expiration_date values, but rather specialized event data stored in Calendar itself. Since the EE simple search form uses the regular EE channel entries library, it won't be able to filter for upcoming events based on entry_date and expiration_date. Further, occurrences of an event are not necessarily ...


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

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

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

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

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

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

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


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