There are way too many limitations about what types of elements may be placed inside a repeater. Consider this highly reduced list of what the repeater cannot repeat:
-
Facebook Comments
-
Facebook Like
-
Facebook Page Like
-
Pin to Pinterest
-
Pinterest Follow
-
Share from Pinterest
-
Twitter Follow
-
Twitter Tweet
-
YouTube Subscribe
So you cannot allow users to like, follow, etc. individual items in a repeater, the way 99% of sites that interface with social media do? Come on, really? Is there any site out there that interfaces with social media that doesn’t do this? -
Most photo galleries (including full-width galleries, and certain layouts such as Masonry and Stacked)
-
Repeaters
-
The Pro Gallery
So you cannot have a repeater showing products, and a little gallery in each one showing product variations, the way a lot of online clothing stores do? -
The HTML component
So basically, you cannot interoperate with external sites within a repeater at all. This, in particular, is my use case, which prompted my “discovery” of these stringent limitations.
The above are very basic use cases, not some bizarre one-off need. And these are only the most egregious limitations. Other posts said that performance was the motivation behind the limitations. This is a very poor reason. Just because it is possible for a nested repeater to result in poor performance, does not mean that in Joe X’s site in particular it will. Someone whose site is truly dependent on performance would not use a platform like Wix. Compared with other options, like straight ASP.NET or PHP or similar platforms that use direct manipulation of raw html/javascript/DOM, Wix is not fast, it just isn’t. So to limit so many use cases out of guarding performance is a terrible option. Warn the users about performance, fine, but leave it up to them to decide what trade-offs to make. As it is now, I am forced to make the user go through extra steps due to these limitations.