Thanks Michele,
It is really good to know that flexible layout could be a probable solution. But what I believe is, if there is a limitation in using maximum number of repeater within repeater, wouldn’t it be better to include it in the documentation? Or if there is a performance issue using repeater within repeater, wouldn’t it be better to add it to the documentation as well?
Reason for all the fields inside a repeater field is that all those fields might be used more than once. The way I have to arrange repeater fields in this case, because that is how I wanted to make it easier for client to handle content editing job. However, If I knew ‘repeater’ field has limitations, then I would have thought it differently.
I would really appreciate if you can add a note to the documentation saying that using repeater inside repeater would sometime not work, as it would help other developers planning their work.
Regards,
Tuhin