Forums / General / "Add locations" USELESS for parent objects

"Add locations" USELESS for parent objects

Next topic

Author	Message
Stephen Paschall	Wednesday 22 October 2003 11:49:23 am Adding locations for objects that have children (e.g., folders) simply doesn't work properly. The subtree is lost at the new location. Really, what's the point of allowing it if the subtree doesn't follow the parent? You've got to go through it node by node, manually, to recreate the subtree if you want to post such an object in multiple locations. I've noticed several posts to this effect, going back for some time now. It's hard to believe this hasn't been addressed yet. Granted, I know this is an open source product and we can't exactly demand action on this from eZ, but you have commercial clients using this tool, too, and I think this is a major flaw that needs attention, fast. I'm trying to familiarize myself with system layout so I can figure out how to fix it myself, but this is a complex project and it's going to take me some time to get to that point. Will this be resolved in eZP 3.3?
Alex Jones	Wednesday 22 October 2003 11:59:30 am While I would like this functionality, I think it is important to keep in mind that automatically adding children is not always desired. The system should provide an option as to whether the children of an item should also be added to the location. Alex Alex [ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ] <i>When in doubt, clear the cache.</i>
Stephen Paschall	Thursday 23 October 2003 6:45:24 am Granted, for many content classes, that's true. For certain classes, however (most especially the built-in "folder" class), you almost always want to carry over the subtree. It would also be nice if you had the option of creating a true "copy" at the new location or just a "link". I'd simply like to be able to maintain any content element at multiple locations without having to update multiple copies. It's neither intuitive nor particularly useful the way it works now.
Jan Borsodi	Thursday 23 October 2003 10:55:54 pm There's no need to link in all subchildren to both locations. If you want a folder to show the same children in all locations you only need to change the template listing. Instead of fetching children from the current node you should fetch them from the main node of the object, if you then make sure that new subchildren are always placed at the main node you will not have any problems. It is not a flaw but a design decision to not make things more complex than they need to be. -- Amos Documentation: http://ez.no/ez_publish/documentation FAQ: http://ez.no/ez_publish/documentation/faq
Jonny Bergkvist	Monday 27 October 2003 1:39:56 am Jan, I can't see that you could get full functionality just with templates for carrying the subtree with you at the added location. It will work fine at the first level when you open the object from the added location, the template could view a tree view or list view of the main locations children. But when you want to go deeper into the sub-tree you will then jump to the sub-tree at the original location. If you ie. want a folder and its subtree to be viewed also at another section that has another design, then you should be able to let this object carry the whole subtree/all children into that added location. Please consider making this feature in a future eZ publish-version :-) Jonny
Jaroslav Satkevic	Tuesday 11 November 2003 12:58:33 pm Thanx to Jan Borsodi. I just replace "hash(parent_node_id,$:item.node_id..." with "hash(parent_node_id,$:item.main_node_id" in folder.tpl file :) If you need se in add lovation's children in site's submenu, just replace one line in menu script ( pagelayout.tpl ... ).