Project

General

Profile

Bug #2118

Putting PortfolioA as Child of PortfolioA is possible

Added by Nathalie Blocry almost 9 years ago. Updated over 7 years ago.

Status:
Bug resolved
Priority:
Normal
Start date:
07/10/2010
Due date:
% Done:

0%

Estimated time:
Complexity:
Normal

Description

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.

History

#1

Updated by Nathalie Blocry almost 9 years ago

fixed, it was just a typo

#2

Updated by Nathalie Blocry almost 9 years ago

  • Status changed from New to Needs testing
#3

Updated by Nathalie Blocry almost 9 years ago

this is still a problem because only the direct parent and used children are excluded.
I can still create loops that break everything

#4

Updated by Stefaan Vanbillemont over 8 years ago

  • Status changed from Needs testing to Assigned
  • Assignee set to Nathalie Blocry

Any update on this matter?

#5

Updated by Nathalie Blocry over 8 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
http://code.google.com/p/chamilo/source/detail?r=7a1c09d64c&repo=chamilo

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.

#6

Updated by Stefaan Vanbillemont over 8 years ago

  • Target version set to 21
#7

Updated by Hans De Bisschop over 8 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)

#8

Updated by Stefaan Vanbillemont over 8 years ago

  • Project changed from Chamilo LCMS Connect to Repository
  • Category deleted (4)
#9

Updated by Stefaan Vanbillemont over 8 years ago

  • Target version changed from 21 to 2.1.0
#10

Updated by Stefaan Vanbillemont over 7 years ago

  • Target version changed from 2.1.0 to Backlog (default)
#11

Updated by Michael Hosdez over 7 years ago

  • Status changed from Needs more info to Bug resolved

Seems to be fixed.

Also available in: Atom PDF