4

Here's a basic setup for what you're trying to achieve, with the class .biggie representing the markup for making your entry big, and the absence of that class indicating a "normal" representation of your remaining entires. NOTE: Since the default order for channel entry output is reverse date order (newest first) you do not need to specify any order or ...


4

As I told you earlier today, this is not a Low Search issue, but a conditionals parsing issue. If you turn on Template Debugging, you'll see the opening tag just before it is actually executed. It will look something like this: {exp:low_search:results {if embed:author_id}author_id=""{/if} ... } That is what's executed, and what EE uses to set the internal ...


4

What you're trying to accomplish would be better served using a module, instead of plugins in a template. With a module, you can create a true form action and use pure PHP, rather than fighting the template parser with the spaghetti you've got here. There are good docs on building a module: http://ellislab.com/expressionengine/user-guide/development/modules....


4

The issue is parse order. Read the attached pdf.parse order. Turn on the debugger and then view the template in your browser. Scroll down thru the debugger until you find the tag containing {current_url}. You will see that that {current_url} has not been parsed. According to the attached doc, it is not parsed until step 9 - last. In your module, try $...


3

I would highly recommend using Low Search to provide the filtering you're talking about. http://gotolow.com/addons/low-search/docs/filters#categories By default it would show all entries, and allow you to use your categories as filters to refine your results. It can do some pretty remarkable stuff, highly recommended!


3

I believe you're running into problems with the parse order. When you add quotes, recipients becomes a valid parameter but it isn't parsed yet. When you remove the quotes, it becomes an invalid parameter and is ignored. You should be able to add parse="inward" to the contact_form parameters to parse recipients first. {exp:email:contact_form charset="...


2

There's a sample of this code on user guide. You need to use the start-on parameter and to enable PHP to run at input on the template: <?php $start_time = ee()->localize->format_date('%Y-%m-%d %H:%i', ee()->localize->now - (60*60*24*14)); ?> {exp:channel:entries start_on="<?php echo $start_time; ?>" site="nxtsports" channel="...


2

RewriteRule ^(.*)$ /index.php?/$1 Instead of... RewriteRule ^(.*)$ /index.php/$1 Normally the first thing I try when query strings go wrong!


2

Conditionals are your friend! Assuming both parameters are required: public function eventtitle($eventCode=NULL,$_type=NULL) { // is either of our parameters null? // if so, try and get it from the tag! if (is_null($eventCode) || is_null($_type)) { $eventCode = $this->EE->TMPL->fetch_param("event_code"); $...


2

You can do something like that: {exp:channel:entries channel="test" disable="categories|category_fields|member_data|pagination|trackbacks|relationships" dynamic="no" } {if count%2 == 1} <div class="even"> {/if} <p>{title}</p> {if count%2 == 0 || count == total_results} </div> {/if} {/exp:...


1

Are you absolutely sure you have your DB settings correct in your config.php file? They should have this format in that file: $config['database'] = array ( 'expressionengine' => array ( 'hostname' => '', 'username' => '', 'password' => '', 'database' => '' ), ); Obviously, ...


1

Tags in params aren't going to be parsed unless you add this parameter: parse="inward" The parse order stuff is... hard to grok. Try adding that to your channel entry tag. https://docs.expressionengine.com/latest/templates/language.html#changing-parsing-order


1

Stash is very useful sometimes, but also is notorious for exactly this kind of obscure fail behaviour. Just look at the kind of questions asked about stash in this forum and you will see that you are not alone in encountering baffling behaviour. There probably is a cute / concise solution to your problem: I'm not sure I have such for you, but do have two ...


1

The example you have highlighted is intended to illustrate how you can take advantage of the stash caching system to create multiple cached versions of the same template code based on with different embed variable values. From the same documentation page that you clipped your example: They can be nested, but unlike standard ExpressionEngine embeds you ...


1

Mufaddal's answer will split the results into 2 columns. From your question I'm assuming you want the first X entries to be in a column, then the rest elsewhere...? {exp:channel:entries channel="test" disable="categories|category_fields|member_data|pagination|trackbacks|relationships" dynamic="no" } {if count == 1} <div class=...


1

I've found the simplest way is to use stash like this: {exp:channel:entries channel="childChannel"} {exp:stash:set_list name="related" parse_tags="yes"}<!-- Set the list --> {siblings field="relationship_field"} {stash:title}{siblings:title}{/stash:title} {stash:field1}{siblings:field1}{/stash:field1} {...


1

The dynamic filtering was altered in the updates and the combination no longer functioned. Integration of MySQL Queries was needed to create the desired result.


1

As per the docs (and as Jim says) Try using the `form:attribute parameter. Something like this : form:data-abide="" Might work, might strip the empty tag, however even if not this should get it on the form, it's just if Abide will recognise the data attribute with the 'false' value set. form:data-abide="data-abide" Otherwise, without rereating the form ...


1

The BrilliantRetail catalog tag does not currently allow for changing the number of results to pagination per template. For your use case though I would consider a relationship or using the BR product fieldtype to pull specific products on the main page. We generally setup a home page channel for our clients and allow them to select a few 'featured' products ...


1

A hook would probably not be the best way to do this. With a module, you can extend the functionality of the channel:entries tag by passing your custom module tag off to channel:entries. This gist is an excellent example to follow. Basically you'd have to use the parameters sent to your custom module to create a pipe-separated list of entry ids that you ...


1

EE doesn't support that range syntax out of the box. It expects a single numeric value after the operator. You'd need either the Query module or an add-on like Solspace Super Search or Low Search, by yours truly. With the latter, you can use this syntax: {exp:low_search:results search:cost=">=10|<=20"} Or use the Ranges filter, like so: {exp:...


1

Here is the solution to my question. Instead of using the search parameter i wrote a single result query around my channel entries tag and passed the concatenated entry_id's in the entry_id parameter Separated by | that allowed me to loop through all the entries for each channel. {exp:query sql="Select GROUP_CONCAT(CONVERT(entry_id, CHAR(8)) SEPARATOR '|') ...


1

Without testing your code, I suspect you are getting No Results thanks to both of your search parameters needing to be found, and by definition, this is impossible, because neither channel has both of these values as fields at the same time. This appears to be a job for Stash Lists. You can create lists with Stash, append whatever, and sort them however, ...


1

Looks like the parameter should be "OrderBy" without the underscore. https://exp-resso.com/docs/orders_tag.html#orderby I also verified this in the code that it is indeed looking for the "OrderBy" parameter opposed to "Order_By" :D


1

Looks like it should work at a quick glance. Since it seems that the Channel Search might not work with Title, I think your 2 options are create a new field for Product Name or you can write your own mysql query / plugin to do the search for you.


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