Thread

Hello again.

Again and again I’ve a problems with a EE template parser. Now I can’t use custom field as a parameter on pair tag of another custom field.

I use Grid Lite fieldtype and try to pass another custom field to specify row_id of grid.
It looks like:

{grid_field row_id='{row_id_field}'}
<!--content-->
{/grid_field}

As a result I’ve got incorrect parsing of this tag. There is some prioritization of template tags parsing?
How can I use one custom field as a parameter of pair tag of another custom field? Why it’s so hard to drive?

Hi FiSt,

I’m sorry you’re frustrated with the order the Template Parsing Engine executes.

This is an odd expectation, give that each channel field would be replaced at the same time in the parsing order.

One way to work around the limitation is to pass one field’s value to another template with an embed variable:

{embed='templates/grid-field' my_row="{row_id_field}"}

then the child template
{grid_field row_id='{embed:my_row}'}
<!--content-->
{/grid_field}

Cheers,

Hi Dan. Thank you for reply.

Your solution is really expensive work around, because both fields belong to one channel entry. In your case, I expect that wide code will be something like this:

{!-- Main Template --}
{exp:channel:entries channel='my_channel'}
    {embed='templates/grid-field' entry_id='{entry_id}' row_id='{row_id_field}'}
{/exp:channel:entries}

{!-- Embed Template --}
{exp:channel:entries channel='my_channel' entry_id='{embed:entry_id}'}
    {grid_field row_id='{embed:row_id}'}
    <!--content-->
    {/grid_field} 
{/exp:channel:entries}

So, I’ll need to fetch each entry twice and it’s very expensive to me. I’ll try to find another solution.

Anyway, do you know that EE template parser is cause of most complications in all EE? Many many problems I’ve got just with it. Maybe your developers need take more care about this area? Or your guys should use some specialized open-source solution like Smarty, Twig etc. ?

Anyway, do you know that EE template parser is cause of most complications in all EE? Many many problems I’ve got just with it.

I’m sorry you feel that way and I can understand your frustrations. Have you ever read Low’s ExpressionEngine’s Parse Order?

It gives a great rundown on how EE handle tags and when they are processed.

But I’m not really sure of any other way to get the value on one channel field to work as a parameter on another field in the same channel.

This might a situation where the Query Module is a better fit for what you need, or perhaps a custom plug-in?

Cheers,