Putting PortfolioA as Child of PortfolioA is possible
In the complex builder and through the repoviewer I can add a portfolio as a child of itself.
This creates an endless loop when trying to retrieve the object and breaks the portfolio-publication when the portfolio was published.
I think for now the portfolio is the only content-object that can contain a child of the same type, but when I create the handbook content-object I will run into the same problem.
Updated by Nathalie Blocry over 12 years ago
- Status changed from Assigned to Needs more info
- Assignee changed from Nathalie Blocry to Sven Vanpoucke
fixed when adding a child in the portfolio application
but you can still create infinite loops in the repository for these types of co's (portfolio's, handbooks, learning paths, ????)
by first creating item1, adding item2 to it in the complex builder. then going back to the repository and to the complex builder of item2: you can now add item1 as a child. I don't see a way to fix this in the builder.
Updated by Hans De Bisschop over 12 years ago
Already working on fixing this (and more) by adding a new level of functionality. Basically, every complex object will be aware of it's complete structure (always downwards considering reuseability). This has the advantage that we will always know whether an object has already been used "somewhere" in the entire complex structure. In time this should avoid creating circular loops with complex content objects.
Stay tuned for more details (read: digital version of assorted ravings on paper)