And even this is inconvenient, in Webflow there are already a bunch of small and big inconveniences that force the developer to act strangely, uncomfortably, routinely.
I have used this practice more than once, but itâs terrible, itâs a crutch.
For example, right now I canât just create a copy of the page-wrapper because I have a nested collection inside, oh surprise! Nested collections have also been an unsolvable problem for more than 5 years.
I donât understand Webflow, such strange shortcomings need to be fixed first. Copying div blocks and then detaching everything from them, considering that the new page and collections have the same field names and variables, creates a strange feeling and makes me think that this is a circus and they are mocking me.
There are a lot of pain points in Webflow that burn with a red flame, but they have been ignored for several years. These shortcomings do not look like minuses for which you can pay extra and solve on a more expensive plan, they are not fixed at all, in essence, it looks like a bug called a feature.
âoh sorry, You cannot have more than 1 nested Collection List on a single page.â
but what it really means
âoh sorry, WE cannot have more than 1 nested Collection List on a single page.â
webflow, youâre awesome, Iâm grateful for your years of work and the opportunity to use your tools, but please show concern for the developers who work on your platform, who take weird positions to solve simple problems like duplicate collection pages, limiting nested collections, number of collection sheets per page and much, much more.