Studying your case for a new feature, I'm discovering that there is a risk to provide a new parameter that allows multi block.
The risk is to use the feature to merge a large number of blocks that where previously multiplied by a MergBlock.
Example:
Let's say that TBS has a new parameter "newblock" which allows to define several blocks merged with the same name.
<tr>
[article.name;block=tr]
<select name="sel-country">
<option> [country.name;block=option;newblock] </option>
</select>
</tr>
|
In this configuration, the following code works but is very slow:
$TBS->MergeBlock('article',$article);
$TBS->MergeBlock('country',$country); |
The good one is to chnage the order of the merges:
$TBS->MergeBlock('country',$country);
$TBS->MergeBlock('article',$article);
|