Hot answers tagged

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'; ...


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(...


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