6

The variables inside the field need to be prefixed with the Grid variable name, like this: {lv-home-slider:slide} {lv-home-slider:caption}


5

The reason you do not have access to that variable outside the loop is because your stash tags (getters and setters) are not parsed at the same time. EE module tags are parsed recursively from the outwards inwards, peeling them one after another like a oignon. In your code above, your stash set tags are inside an entry loop (level 2), while your get tag is ...


5

To extend Robson's answer, I've just been implementing this myself in the past few hours!: MX Mobile Detect and on Devotee I could simply detect which device it is (e.g. ipad, iPhone, blackberry, etc), but that's too specific for my needs. I just want to detect the different sizes of device so I can drop smaller images... So, in addition to my JS ...


5

It looks like you moved your templates folder to outside the system folder. Since you already did it, why not move it to above the web root? Just remember to update the related settings. (see "Server path to site’s templates" at the bottom of the page) To keep all system files above the web root is good practice. Alternatively... If for some reason you ...


3

The issue is one of parsing order... User Defined global variables are the last thing to be parsed. This PDF outlines ExpressionEngine’s Parse Order. This page in the docs details the Rendering Stages of the EE template engine. The solution is to switch to using a Snippet instead.


3

The only way of do this is using addons. There's a lot of them on Devotee. This looks a good bet, but I never used any of them. Maybe it's better to use some front-end technique for this.


2

When you save a variable with a specific scope (in this case, scope="user") you should use the same scope when you get it. However, if you're showing the errors within the same page request there's no need to actually save the variable at all. It's possible in this case that the tag pairs {global_errors} and {field_errors} are removed from the template by ...


2

After the parsing of the related entry, if there's no related entry, your conditional will became this: {if:elseif == 48} As you can see, this doesn't make any sense. So, add quotation marks: {if:elseif "{related_entries id='privacy'}{entry_id}{/related_entries}" == 48} After the parsing of the related entry, if there's no related entry, your conditional ...


2

Depth isn't an issue with embeds and neither is URLs, so if the embed works from template A, it will work from Template B. So it isn't any parameter issue (unless you use embed variables in the parameters - see 2 below). Three factors that are most likely: The embed in Template B is within a conditional which is not being met. You're passing embed ...


2

I would suggest you just to use pages module for Products channel and enter the random string into Page URI of Pages. But it wouldn't be good approach to generate and enter a URI (like /products/xA39sZ7s) containing random string into Page URI each time while editing or publishing an entry. To overcome it, just develop a small extension which will do update ...


2

You’re missing the “/” in “{/near_hotels}”.


2

Try this instead: {if logged_in} <br /><a href="{path='store/my_orders'}">My Orders</a> {/if} {if logged_out} <br /><a href="{path='account/login'}">Login</a> {/if} Not sure if it's an EE version thing, but {if:else} never used to work for me on older EE versions, but does with the latest. Either that or it'...


2

Since you're evaluating a string, the arguments should be enclosed in quotes ("). {if "{month}" == "{segment_4}"}class="current"{/if} You may need to add a OR operator for a second condition to check. Update Just realized I misunderstood your question. I found this Multi Language Module that allows you to define phrases ...


2

You're running into a parse order issue here. The conditionals are parsed before the global variables, and therefore your comparison is taking place with the actual value you have within the conditional instead of the parsed value. There are a couple things you can do. 1) Use a snippet instead of a global variable, as these parse much earlier 2) Use an ...


2

So it looks like the issue was with the flexslider zip. I looked at the demo included in the zip and it has the same issue. I resolved the problem by grabbing the js file from the live demo page.


2

If you want your variables to be in the subscriptions:sub4 format, you should try this: foreach ($subscriptions as $key => $value) { $data['subscriptions:'.$key] = $value; } return $this->EE->TMPL->parse_variables_row($this->EE->TMPL->tagdata, $data);


2

you issue is that all your records have class="active". It is happens because count is going from exp:channel:entries and for all playa records is the same - 1. You have already var_prefix parametr for playa:children, so you just need to add it into condition. <ul class="pill tabs-content contained"> {exp:playa:children field="...


2

You can do this with a Stash list nested inside itself, like so: {exp:stash:set_list name="regions" parse="yes"} {exp:channel:entries channel="regions" dynamic="no" orderby="title" sort="asc" disable="categories|member_data|pagination" } {stash:entry_id}{entry_id}{/stash:entry_id} {stash:title}{...


2

With Stash: {exp:stash:set name="categories" parse_tags="yes"}{exp:gwcode_categories channel="products" depth="1" style="linear" backspace="1"}{cat_name}|{/exp:gwcode_categories}{/exp:stash:set} {exp:stash:parse} {exp:switchee variable="{segment_2}" parse="inward"} {case value="#^P(/d+)$#|category|''"} {switchee variable="{segment_3}"} ...


2

This turned out to be a bug in the Template class: https://support.ellislab.com/bugs/detail/21054


2

Can’t see any problem off hand, but I’d try some of this: According to the docs, the backspace parameter counts as four characters, so change the backspace value to 4. Removing the <br> Removing the backspace parameter Ensure that category group is indeed assigned to the ‘trips’ channel Try putting group 6 after group 7 and see if the same thing ...


1

This has to do with the new template parser introduced in EE 2.9.0. What you're seeing is a template annotation, and it's removed from the template late in the parsing process. Since you're manually calling exit(), it never gets the chance to do so. My advice: turn this code into a simple plugin instead. This amount of PHP in a template is always trouble ...


1

I've seen this. I think it's because the line breaks for {exp...}, {datablock} and so forth are added to the source, even if the code on those lines doesn't insert anything visibly into the page. It really kind of makes sense, when you think about it, although it definitely makes for less clean-looking source code, and marginally more HTML data that has to ...


1

I beleive you can get some info from this ist : https://gist.github.com/croxton/9d012297096892ca5c10 The premise is the insides of the stash tag is parsed at the stage the module tags are parse, whereas conditionals are passed before (simple) and after (advanced). Have you tried messing about with {exp:stash:parse} inside the get_list tag pair? Also, ...


1

parse="inward" is the villain here. Switchee is being parsed before the exp:gwcode_categories. Since I believe you need the parameter, your option is to force exp:gwcode_categories to be parsed early. Let's try using embeds. {embed="group/template" categories="{exp:gwcode_categories channel="products" depth="1" style="linear" backspace="1"}{cat_name}|{/exp:...


1

You have still included your JavaScript in the wrong order, jQuery should come first. How it is now: <!-- More Foundation pannel --> <script src="http://niwot.colorado.edu/eejavascripts/jquery.foundation.tabs.js"></script <!-- END More Foundation pannel --> <script src="http://niwot.colorado.edu/eejavascripts/jquery.js"></...


1

As far as i'm aware this functionality is built in by default, if there is no template then it'll automatically 404 error. Please see the ExpressionEngine URL Schematic here: http://www.jamessmith.co.uk/images/ExpressionEngine_url_schematic.png


1

Your embed syntax is incorrect. {embed:LAST_ID} assumes that the template you're running has been embedded from within another template, and that the parent template's embed code had a parameter named LAST_ID, which has now been passed tot he template you're in. What I think you are wanting to do it use the value of an embedded template in your channel:...


1

You should never to nest exp:channel:entries, but, in this case, you have a fair reason. Let's use an embed! {exp:structure:entries channel="iconGroup" limit="1" sort="asc" paginate="bottom" disable="categories|member_data|member_data|pagination"} <h1>{title}</h1> <div class="icon-grid"> {embed="includes/.files-and-...


1

Give this script a try to edit the templates: http://buildwithstructure.com/documentation/how_can_i_batch_update_templates_for_existing_entries/


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