Sorry for double posting, but I posted this in "Upgrading Silverstripe" and got no response. I was hoping someone here could help me.....
Okay, I have run into the following predicament and I'm not sure if this is a bug or intended behaviour, but it affects quite a bit of a project I'm upgrading.
In a template I have the following code:
<% if Results %>
<table class="records items">
<% loop Results %>
<% include ResultsTable %>
<% end_loop %>
Which grabs the results from a search and plops them into a template. But the table part I reuse in other areas, so it is included. The table include looks like this:
<% if First %>
<% control ColHeadings %>
<% end_control %>
<% end_if %>
<tr<% if Even %> class="zebra"<% end_if %>>
<% control RowValues %>
<% end_control %>
All the code works except I'm getting an unintended result: Every time the include runs, the "if first" evaluates to true... every time. The previous (2.*) versions of Silverstripe would first include the resultstable and THEN loop over it, with the "if first" only being true one time. The new (3.0.3) version seems to include that template every time it loops, which sets the iterator back to one every time.
Notice the $Pos vars in the templates: LOOP $Post evaluates to the correct number (LOOP 1, LOOP 2, LOOP 3, etc). But the INCLUDE $Pos is always 1.
Is this a bug or intended behaviour? If it is intended, then how am I supposed to order the includes/loop in order to have "if first" evaluate true only once?
Don't know if it's relevant, but the table is populated by the following code:
$query = $context->getQuery($searchCriteria, $Sort, array('start'=>$start,'limit'=>$limit));
$records = $context->getResults($searchCriteria, $Sort);
$records = new PaginatedList($records, $request);