Hot answers tagged

4

Low Seg2Cat doesn't pick-up category information associated with channel entry IDs in the URL - it picks up category information associated with category URL titles in the URL. So, it is working, but it doesn't do what you thought it might do.


3

Did you mark the Grid field as searchable after creating entries? If so, you need to re-save those entries in order to populate the exp_channel_data table with searchable data, which Low Search in turn uses for its collection index.


3

Low Search doesnt work, Free Form doesnt work, Free members - basically asks if your sure you want to login as some things might not be secure. These add-ons usually use what you have configured in your "Admin > General Configuration > URL to the root directory of your site". You can also set/override the General Configuration settings using the /system/...


3

I hear what you're saying about automating but in reality just how many holidays do you honour? It's not going to take too long to do it manually. I would create a channel for holidays and create an entry for each holiday with the entry and expiration dates set. Then on your template use a channel entries tag pair with show_future_entries="no" In theory ...


2

Try making this a global variable in your config file, then you can do all the date checking in PHP. Go to http://www.epochconverter.com/ and get the start and end date of when you're closed, then add this to your config.php file. if (time() > 1387497600 && time() < 1388016000) { // Use this in your template {hours_open} and it'll show if ...


2

Low Seg2Cat currently (v2.8.0) expects lowercase category url titles. If you have any uppercase characters in them, they will not be matched. By default, this should pose no problem, as EE will always lowercase them. But if you're importing them, or manually setting them, they might have uppercase letters in them. To change all category url titles to ...


2

Using an early parsed var (or a Snippet for that matter) like that doesn't work. To illustrate, using the var you geva as an example, and using it like this: {exp:low_events:entries entry_id="not {lv_exclude_id}"} ... {/exp:low_events:entries} ...will result in this code when we come to the stage where tags are parsed: {exp:low_events:entries entry_id=...


2

I wouldn't say the documentation stinks, there's an example near the top of the page under Usage close to what you want. In your case, it looks like you probably want: /tournaments/public-schedule/archives/{year:regex[(\d{4})]}/{month:regex[(\d{2})]}/ Then you will access your segment variables with {segment:year} and {segment:month}.


2

tl;dr: use exact="search:order-model" on your Results tag. You're not using the Keywords filter here, but the Field Search filter. Hence, the search_mode parameter is not used; it's only used in conjunction with the Keywords filter. The Field Search filter is basically the native search:field_name parameter on steroids, so you can mimic what you'd normally ...


2

Try upgrading Low Search to the latest version. Version 3.1.6 has this bugfix: Fixed a bug where a page URL could be falsely rewritten to maintain the query string ...which should probably fix the issue. If it does not, try changing the hrefs of the pagination links to: href="{pagination_url}?{current_query_string}"


2

As per the docs: [P]arameters can be applied in two ways: as input fields in a Form, or as hard-coded parameters in the Results or URL tag. You've got the filter parameters set on the Form tag, which will have no effect (as per v3.0, anyway). You should move all those parameters (except result_page and form_class, which are valid Form tag parameters) to ...


2

It's not possible to order by a column in a Matrix field. Just imagine how that's supposed to work: if a Matrix field has multiple rows (and therefore multiple prices), which price should be used for ordering? It doesn't really make sense. If you want to order by price, there should be a dedicated field that contains the price by which you can sort and ...


2

I reported this bug to Pixel & Tonic, and they right away got working on a "duct-tape" type fix. It seems, to get this working, in Assets 2.6, you can change line 1810 of system/expressionengine/third_party/assets/ft.assets.php from if (! $field_name) to $tagparts = ee()->TMPL->tagparts; if (! $field_name || (isset($tagparts[0]) && $...


1

When using the Parse or Pair tag to output a Grid field, the tag will act the same as a regular Channel Grid field would. That means you can use the same template tags and parameters. That means the var_prefix parameter won't do anything, because it's not a valid Grid parameter. It also means you need to prefix all Grid columns with the field/var name. So ...


1

Make sure Early Parsing is enabled for that Pill variable, then use this syntax: {if lv_metasocial_meta_title_display == "title_site_name"} ...which is EllisLab's recommended syntax for conditionals.


1

Alright, I did a fix. I renamed my en, fr and es fields with a prefix label_. In my template I did this: {/stash:nocache} {exp:low_variables:parse var="var_eleads_countries"} <option value="{var_eleads_countries:code}"> {var_eleads_countries:label_{segment_1}}</option> {/exp:low_variables:parse} {stash:nocache} The nocache tag is ...


1

Try using the :one_day modifier. {if '{event_date:one_day}' != 'y'} Show stuff for multiple days {/if}


1

Appears the problem was a conflict with another custom add-on that was installed. I've disabled it for the time being and I'll review the source code to fix at a later date.


1

It's not yet clear if you're encoding queries or not. If you are, then having paginate_base="search" will not include the encoded query in the pagination links, and will therefore 'forget' the query. Try either using paginate_base="search/{segment_2}" or removing that parameter altogether. Since you're using Structure, make sure the actual encoded query is ...


1

I'll get the error fixed in the next version. For now, open up /low_search/filters/keywords/lsf.keywords.php and look up line #869, which reads: $row['auto_path'] = $this->_urls[$row['channel_id']] . $row['url_title']; Change that to: $row['auto_path'] = @$this->_urls[$row['channel_id']] . $row['url_title']; Note the @ added before $this->.


1

If I understand correctly, you only want to execute the exp:ajw_export tag if the logged in member ID is 1. For this, you don't need the low_variables:parse tag. Instead, in the Low Variables settings, make sure Early Parsed Member Data is set to Yes. Then use (simple, pre EE2.9) conditionals: {if logged_in_group_id == 1} {exp:ajw_export sql="SELECT * ...


1

Took a look and saw you were using the same fields twice: once for mobile, once for desktop. One of those would be hidden based on User Agent, but the checkboxes would be checked anyway, as they were still in the DOM. That means checking one checkbox would actually check 2, resulting in a parameter like category="1&1", which triggered the No Results. ...


1

If I understand you correctly, the content of the lv-seg1-taxonomy-node-id variable is that big if-statement. Then you're using the LV as part of another conditional: the one in your first example. This will not work because of Parse Order. Your variable is set to parse early, which means the template will change this: {if node_id == {lv-seg1-taxonomy-...


1

I'm not entirely sure what you mean by "that channel, and any other within its "blog" category are not available to create a collection", but Low Search Collections do not take categories or category groups into account. Collections are made per channel, regardless of category, category group, status, etc. In any case, I recommend upgrading to the latest ...


1

You need to include the parameter shortcut="[shortcut name]" in your {exp:low_search:results} tag. The value can be taken from your url segments. e.g. If the url was www.mysite.com/search/bacon and you had a shortcut set up for "bacon" then your search results tag would be {exp:low_search:results shortcut="{segment_2}"} You can combine this with the ...


1

Instead of using Low Nice Date, why not try the :one_day modifier that is available in Low Events itself? That should let you achieve what you want without an extra add-on: {if event_date:one_day == 'y'} {event_date:start_date format="%j %F %Y - %H:%i"} {if:else} {event_date:start_date format="%j %F"} - {event_date:end_date format="%j %F %Y"} {/if}


1

Low Yearly Archives isn't specifically compatible with Transcribe. But if the languages can be differentiated by, for example, status, then you can use that parameter to filter the entries. Otherwise, some sort of hack would be required.


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.


1

Issue was that the jquery.min.js file was in the footer, it was preventing the map from being rendered


1

I believe the only part of the original URL you need is the numeric part, which contains the event ID. You should be able to build an anchor using something like this: http://www.shareasale.com/r.cfm?u=841156&b=234786&m=27601&afftrack=&urllink=www%2Eticketfly%2Ecom%2Fpurchase%2Fevent%2F{some regex that will extract numbers from your URL ...


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