nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

nested interation in component templates

JeremyH

The high level structures of the DCT and PT are shown below. Is there a way to pass in the particular replicant location from parent template to included template so that it can process just the subsection that is included? Or is this something that can really onnly be done with perl?

<replicant>

<replicant/>

</replicant>

PT:
<iw_iterate>
<iw_include>

<iw_iterate/>

</iw_include>
</iw_iterate>

Find more posts tagged with

Comments

JeremyH

Well - I've found a somewhat convoluted way to do it.

In the main template, passing the references as CDATA seems to get the proper object reference across. (Trying to use the params ends up in different degrees of clobering.)


<iw_iterate var="tpl" list="dcr.Main" >
<iw_perl><![CDATA[
my $pt_path="/iwmnt/default/main/Admin/IW_Config/WORKAREA/Admin/templatedata/includes/pt/list_item.inc";
]]></iw_perl>
<iw_include pt="$pt_path" mode="ptlocal" >
        $iw_param{parent} = $tpl;
</iw_include>
</iw_iterate>

Then, in the component template, get the value, and manually implement the equivalent of iw_iterate. This seems to work well, while iw_iterate seems to clobber the values.

       
         <iw_perl><![CDATA[
                        my $parent = $iw_arg{parent};
                        ### Manual iw_iterate
                        my @dcr_ref = $parent->get_node_list('List Section.List');
                        my $iteration=-1;    # iteration count
                        foreach my $listblock ( ( @dcr_ref )  )
                        {
                        $iteration++;

        ]]></iw_perl>
<!-- Normal <iw_value>, etc. tags that go between iteration can go here -->
<iw_perl><![CDATA[ } ]]></iw_perl>

gzevin

you can always pass a reference to the list from the parent to a child.

something like this:

$iw_param{'properties'} = [iwpt_dcr_list('dcr.headerMethods.headerProperties')];

in the component template you do:

my $properties = $iw_arg{'properties'};

this is how iw_iterate will look like:

<iw_iterate var='prop' list='@{ $properties }'>

.....

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

JeremyH

Does that reference list capture a nested replicant structure?

The big problem I ran in to was trying to just capture the appropriate replicant iteration to pass to the component template. The built in functionality did seem to work well for dcr-root structures.

gzevin

I can see no reason why it does not. You simply climb down (or up if you wish) a tree...

Give it a try.

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

JeremyH

I could not seem to find a clean way of determining the current position to 'climb to'. After all, the whole dcr structure is available in the component, so the other alternative was to determine the current reference location and just pass that.

gzevin

Frankly, I see no difference in relative/absolute paths... But if you feel comfortable with what you have designed, that's fine. I just wanted to show one more way.

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

JeremyH

Ok. Relative vs. absolute paths was the big problem that I needed to solve.

As far as I was able to tell, I couldn't use relative paths in dcr_list function, though perhaps I was encountering some other sort of bug at the time. Have you had luck with a relative dcr path in the list function?

gzevin

is this what you mean or I am missing something?


<iw_iterate var='prop' list='@{ $properties }'>
    <iw_perl><![CDATA[
     $pageTitle = iwpt_dcr_value('prop.pageTitle');
     $pageLevel = iwpt_dcr_value('prop.pageLevel');
     $custMenuShown = iwpt_dcr_value('prop.custMenuShown');
     $supportMenuShown = iwpt_dcr_value('prop.supportMenuShown');
    ]]></iw_perl>

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

JeremyH

Here is an example. There is a second pt that will be called from the main pt. This pt may be called from a number of different pts that will have different structures. The component pt just needs to worry about its component. However, it needs to know the correct instance of the component. The main pt may have something like that below. Each time the component template is called it needs to know which instance to output (i.e. the 4th instance of 1st replicant, or the 3rd instance of 2nd replicant.)

Template:


<iw_iterate var='prop' list='dcr.stuff.prop'>
      <iw_include pt="proppt" mode="ptlocal">
          $iw_arg{blah} = $prop;
      </iw_include>
</iw_iterate>
<iw_iterate var='second' list='dcr.body.text.props'>
     <iw_include pt="prop2" mode="ptlocal">
          $iw_arg{blah} = $prop2;
      </iw_include>
</iw_iterate>

gzevin

I still cannot get the exact problem that you are facing. If your component PT does know how to treat a set of replicants, why can't you pass them from the main PT?

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

Johnny

so something like this does not work?


main tpl
<iw_iterate var='component' list='dcr.stuff.prop'>
      <iw_include pt="some.tpl" mode="ptlocal">
             $iw_param{'comp'}= $component;
      </iw_include>
</iw_iterate>


include tpl
<iwperl><![CDATA[
   my $comp = $iw_arg{'comp'};
]]></iwperl>

<iw_value name="comp.some.field" />

John Cuiuli

JeremyH

It does not seem to like that approach either.
It ends up resolving comp as a perl variable and thus the whole thing ends up beeing semething like $DCRValueArray05464565.some.field.

I did discover an alternative - nesting everything in an iw_iterate. The outer iw_iterate iterates through just one item, but it transforms the variable in to a way to that can be used by other items.

<iw_include pt="$feature_path" mode="ptlocal">
$iw_param{parent}=[ iwpt_dcr_list("dcr.Column1.Feature") ];
</iw_include>
Then in the component:
<iw_iterate var="root" list='(@{$iw_arg{parent}})'>
<iw_value name="root.Head"/> <br/>
<iw_iterate list="root.ContentType" var="contype" >