7
For any variable that needs extra processing, like the Wygwam variable type, use the tag syntax rather than the variable syntax:
{exp:low_variables:single var="my_wygwam_var"}
Note that having early parsing on or off is irrelevant for the tag syntax, so you can leave it off.
6
While you can't actually parse the tag using your custom module, you can pass parameters to the channel module and run it. Here's a code sample:
function your_module_method()
{
// Set the parameters for the channel:entries tag
$this->EE->TMPL->tagparams['entry_id'] = $entry_ids;
$this->EE->TMPL->tagparams['dynamic'] = 'no';
...
4
You can wrap your code in [code]{ee_tag_here}[/code] and that should output <code>{ee_tag_here}</code> into your template.
2
You can fetch that global variable like:
$address = ee()->db->select('variable_data')->where('variable_name', 'address')->get('global_variables')->row('variable_data');
echo trim(str_replace(array("\r\n","\n","\r"), ', ', $address));
It would work for you.
2
the following template will generate an error because neither the "foo" or "bar" module or plugin exist.
Nested simple conditionals
The "foo" error will not show up, because the two nested conditionals are both simple conditionals.
Advanced conditional
The second block has a nested advanced conditional (it tests for two conditionals, last_segment AND ...
2
uri_page="{last_segment}" is not a valid parameter for channel entries. You're looking for url_title I imagine :)
{exp:channel:entries url_title="{last_segment}"}
{exp:stash:set_list name="related_articles"}
{related_articles}
{stash:rel_title}{related_articles:title}{/stash:rel_title}
{stash:rel_excerpt}{related_articles:excerpt}{/stash:...
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
You can try Allow EE Code
{exp:channel:entries channel="my_channel"}
{exp:allow_eecode}
{my_field}
{/exp:allow_eecode}
{/exp:channel:entries}
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
The position of pagination is defined by the parameter paginate:
if it is set as top, the pagination code will be removed before parsing and added back at the top of the parsing results;
if it's set as bottom, the pagination code will be added to the bottom of the results;
set it as bothand it will be... Well, I got the idea;
hidden doesn't show the ...
1
Quick update - having looked at what causes this error, I found that if I call
ee()->TMPL->fetch_addons();
in my extension before I call stash->parse, it works fine without an issue. Hope this helps someone.
1
This is likely due to parse order, where the {csrf_token} variable wouldn't be parsed yet until the {exp:freeform:form} tag has fully rendered, which would be after the parameters have been parsed.
1
Stash will not parse EE embeds, only it's own embeds.
1
huge thanks to ellis labs support, they pointed me to increasing the pcre.backtrack_limit beyond the default 100000 and it now processes all the tags. in retrospect i should have checked that sooner, but run into issues with it so infrequently it never crossed my mind.
edit system/expressionengine/config/config.php and add this just after the initial line (...
1
The array that you're passing to parse_variables is incorrectly structured - it needs to be one level deeper.
You can fix this either by wrapping it in an array:
return $this->EE->TMPL->parse_variables($this->EE->TMPL->tagdata, array($data));
Or using parse_variables_row instead:
return $this->EE->TMPL->parse_variables_row($...
1
This has been fixed in Wygwam version 4.0.8!
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(...
1
In your Stash tag, you probably need to add the parse_tags="yes" parameter.
{exp:channel:entries uri_page="{last_segment}"}
<!--Set some stash variables here, then:-->
{exp:stash:set name="content" parse_tags="yes"}
....
UPDATE
Separate your queries from your markup.
{exp:channel:entries uri_page="{last_segment}"}
{exp:stash:set}
{...
1
This is because user-defined global variables are parsed very late - after PHP on input, after all module and plugin tags, and even after PHP on output (see parse order).
Your best bet here is to write a simple plugin which fetches the global variable directly from the database, does its work, then returns it.
1
It's my personal advice not to mix up the EE tags with PHP code. There may cause issue because of "PHP Parsing Stage" sometime.
In your case, you can use PHP code like:
EDITED:
$this->EE =& get_instance();
$res = $this->EE->db->select('cat_name')->where('group_id', 4)->get('categories')->result_array();
foreach ($res as $...
1
I just saw your question, and decided to release an add-on I wrote a few years ago for my own documentation: CE Highlight.
The add-on has the ability to optionally style the output, use line numbers, highlight specific lines, and a few other things. It leverages Geshi for the heavy lifting. I hope that helps!
1
I think you can try Template Code from Rob Sanchez for this. Not sure if it still works with latest EE versions, but you might be able to update it.
https://github.com/rsanchez/template_code
Only top voted, non community-wiki answers of a minimum length are eligible
