4
To be on the safe side, I'd check for numerical values only, like 201308. Something like this:
{if {event_dates:start_date format="%Y%m"} == {event_dates:end_date format="%Y%m"}}
same month
{if:else}
not same month
{/if}
When debugging the advanced conditionals, try to remove them and add them one at a time to see which actual one is causing the ...
3
The :set tags are not wrong, per se, as you are using the shorthand syntax. However, due to parse order, your 'get' tags are parsing before your 'set' tags since the sets are within the channel entries module tag.
Stephen's answer does fix things, because it moves the channel loop within the set module tags. (However, that is not always convenient.) You ...
3
The quotes around {fn_zone} mean it's an advanced conditional which may be the problem.
Can you do:
{if fn_zone == ""}
...
{/if}
Or you may have to use the if:else plugin:
{exp:ifelse parse="inward"}
{if "{fn_zone}"!=""}
{redirect="/store"}
{if:else}
{exp:stash:destroy name="delivery_day"}
{/if}
{/exp:ifelse}
3
put exp:channel:entries inside embeded template
{embed="site/channel" my_plugin_ids="{exp:plugin entry_id="{segment_3}"}
site/channel
{exp:channel:entries channel='{embed:my_plugin_ids}' …
-or-
put exp:channel:entries inside your plugin tag's
{exp:plugin entry_id="{segment_3}" parse="inward"}
{exp:channel:entries channel='{my_plugin_ids}' …
{/...
3
Good news, it should be a quick fix. All you need is to prefix your Playa variables with var_prefix parameter to differentiate the namespace from the Channel Entry variables, although you might have to use the full module tag:
{exp:playa:children field="item_colors" var_prefix="pl"}
"{pl:title}": "{title}",
{/exp:playa:children}
3
Stash 2.4.3 corrected a long-standing inconsistency with embeds set to process at the start of template parsing. At the other stages of parsing (inline and end) embeds are parsed by default - that is to say, parse="yes" is the default parameter value if not specified, and 2.4.3 added this as the default for start too.
To make your embed behave as it did ...
3
Turns out the problem wasn't a parse issue after all. Playa disables categories by default so by placing a blank disable="" parameter on the {cf_feed_videos} tag it overrides this and re-enables categories for the related entries.
3
You didn't say which version of EECMS you're using. Some versions have parsing issues on conditionals with single quotation marks. Or, maybe, your version of Matrix have one of this issues.
So, first of all, try to replace them.
{if "{placement}" == "sidebar"}
{exp:mx_jumper:put name="standard_image_width"}226{/exp:mx_jumper:put}
{exp:mx_jumper:put ...
3
Do this right way - do not follow the dark side.
Put all your php code into plugin. Your code is not good even from optimization way - not good solution to loop the channel entry. Just make function which will return list of
$item['some_key']|$item['some_key']|$item['some_key']|$item['some_key']
In this case you will do only one request of channel:entry. ...
2
Using embeds to ensure they are parsed after advanced conditional eventually worked for me.
2
I saw you already find a solution, but I think you should know the reason your code wasn't working.
Your conditional will never work... Ooops! Please, forgive me. Your conditional will always work because "product1" != "product2".
This code will always evaluate:
{if segment_3!="product1" OR segment_3!="product2"}
<img src="/images/styles/madeinusa....
2
Have you tried adding parse_conditionals="yes" to the set parameters? Alternatively, reversing the wrapping to put the conditional on the outside of the set tags?
2
OK, So I had to wrap the entire call in a {exp:stash:parse process='end'} tag and then call the values with just {stash:market_ids}.
Now seems to be working.
2
I haven't tested this (it's a bit tricky to setup!) but try promoting your Stash tags to the top level of the nesting hierarchy like this... Also with exp:stash:parse you should omit the exp part when you get variables (I think you can get away without parse="inward" with this method too).
{exp:stash:set name="groups" trim="yes" parse_tags="yes"}
{exp:...
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
Yes, that is because the conditional is an advanced one, and will be parsed after plugin tags (ie Stash) (ref LOW's parse order PDF).
If the conditional was a simple one, this could work, but that depends on what {fn_zone} is. Only segment, embed, global variables are parsed as simple, and you have to write the left hand part of the conditional witout curly ...
2
I'm not sure why you're using an embed for this, you're not passing anything to it so I'd use a snippet for sure.
Also may as well use set_list, open the tags above the exp:channel call
{exp:stash:set_list name="resources" parse_tags="yes"}
{exp:channel:entries channel="white_paper|c_study|video|webinar|data_sheet" limit="8"}
{snippet:get_data}
{/...
2
The easiest solution would be to use Mo Variables which provides an early parsed {logged_in_member_id} which will allow you to use it as a dynamic value in your URL path.
{exp:rest url="/api/get-default-profile-image/{logged_in_member_id}/" format="json" parse="inward"}
{default_profile_image}
{/exp:rest}
2
If it's two plugin tags that you are needing to nest, see changing parse order for nested tags using the parse="inward" parameter.
2
One really simple way to get around parse order is just to use an embed.
{embed="embeds/_rest" ip_address="{ip_address}"}
Then in your embedded template (embeds/_rest):
{exp:rest url="http://domain.com/{embed:ip_address}" verb="get" format="json"}
{/exp:rest}
Embeds get a bad rap performance-wise, but as long as you aren't using them excessively or ...
2
Wow! This looks so complex...
Please, try using this first party add-on:
{exp:channel:entries channel="Pages" disable="member_data|pagination|categories|category_fields"}
{exp:playa:children var="page_sidebar_items" parse="inward"}
{exp:allow_eecode}
{code_snippet}
{/exp:allow_eecode}
{/exp:playa:children}
{/exp:channel:entries}
I ...
2
Stash parses any known {stash:variable} style markers at the beginning of each pass of the tagdata it wraps (working from the top layers of tags inwards). However {stash:entry_{entry_id}_category} does not resolve to a known stash variable until after {entry_id} has been parsed by the channel entries tag. By which point the channel entries tag has completed ...
2
For EE3, it appears that Freeform 5.x is a bit fussier about the conditional. Try this code instead:
<p>
{composer:field_output}
{!-- composer:field_name will parse first to the field's name --}
{if "{freeform:error:{composer:field_name}}"}
<strong>{freeform:error:{composer:field_name}}</strong>
{/if}
</p>
2
Stash embeds can be parsed at three different stages in the parse order of their parent template:
process="start" - embed the template before any other variables and tags in your template are parsed. The tags in the embed will be fully parsed before being included in the parent template, unless you set parse="no". If you do set parse="no", the embed behaves ...
1
Your :set tags are wrong. See docs here.
{!-- STASH SET --}
{exp:stash:set parse_tags="yes"}
{exp:channel:entries
channel="site_settings"
limit="1"
disable="categories|member_data|pagination"
}
{stash:logo}{company_logo}{/stash:logo}
{stash:style}{site_appearance_style}{/stash:style}
{stash:color}{site_color_theme}{/stash:color}...
1
Actually, maybe you should consider just extending the Channel Entries tag. Might be the most elegant and lease parse-order-hoop-jumping way:
http://dmlogic.com/blog/extending-the-expression-engine-channel-module/
1
it should be work , but it doesn't I think it is a bug.
anyway u can work around this problem with exp:member:custom_profile_data
{exp:member:custom_profile_data}
{exp:channel:entries
author_id="1|{member_id}"
channel="foo"
disable="categories|category_fields|member_data|pagination"
dynamic="no"
orderby="entry_id"
...
1
What about just using the related_categories_mode="" parameter on the channel:entries tag?
1
You could just do this to check the delivery_day value.
{if "{exp:stash:delivery_day}" != ""}
... your code ...
{/if}
1
Is the stash {exp:stash:market_ids} rendering outside of your low_search? Thats probably a good place to start.
I would also try putting
{exp:stash:set name="market_ids" parse_tags="yes"}
{exp:query sql="select GROUP_CONCAT(entry_id SEPARATOR '|') as market_ids from exp_channel_data where channel_id=3 AND field_id_12 LIKE CONCAT('%', DAYNAME(...
Only top voted, non community-wiki answers of a minimum length are eligible