[MAGNOLIA-449] activated contennodes in the config tree stays red Created: 14/Jun/05  Updated: 17/Mar/09  Resolved: 24/Aug/05

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 2.1 Final
Fix Version/s: 2.1 Final

Type: Bug Priority: Minor
Reporter: Philipp Bärfuss Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   
  • select templates
  • activate it

all nodes of type content (folders) are gree
all nodes of type contentnode (subnodes) are still red
all the content is properly activated



 Comments   
Comment by Philipp Bracher [ 23/Aug/05 ]

this is a bigger issue. the activation was originally written for the webpages, which have node-type CONTENT. The paragraphs are of type CONTENNODE

1) If one selects in the menu 'activate only this node' does this mean that you wanna activate this node and all subnodes of type CONTENTNODE. But this is only true in the website tree because all paragraphs belonging to the selected page are of type CONTENTNODE and should get activated. This is not true in the config tree, where only the selected node should get activated.

2) The code does only update the metadata of the subnodes of type CONTENT (subpages) and not those with type CONTENTNODE. If one selects in the tree a node of type CONTENTNODE then the selected node is updated correctly but not its childs.

Solution: the activation is depending on the tree. we must implement different methods. unlikely this code is in the general Tree control and not in the tree-handler.

This solution is ok but brings us a performance problem since more than one activation process is done --> a connect per node!

Comment by Philipp Bracher [ 23/Aug/05 ]

the method makeSerializable(Content content) of the class SerializableContent class adds always all contentnodes. the recurse parameter is only relevant for the including ot the nodes of type CONTENT.

Should we introduce a new parameter like includeContent with default value true?

Comment by Philipp Bracher [ 24/Aug/05 ]

introduced a includeContentNodes flag. this is only relevant if the recursive flag is false. the default value is true since older system use this sematic.

Generated at Mon Feb 12 03:17:32 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.