i'm trying to recover all orphaned nodes to one specific Folder 'LostFound'. Is it sufficient to just do --- use farcry_jura; update nested_tree_objects set ParentID = '<ID_of_Lost_and_Found>' where ObjectID = '<ID_of_orphaned_node>' --- or is it important to adapt other column values of the orphaned object to recover it in fact ?
Additionally, we have LOTS of problems suddenly with the tree levels getting confused and after Fixing Tree the objects are orphaned at best. (milestone 2.3.1, CF6.1) Is there any possibility to have a log of changes for tree changes to look after that ? regards, Jens Seipenbusch Geoff Bowers schrieb: > Jens Seipenbusch wrote: > >> i have some orphaned nodes from a user who moved navnodes. >> When i try to attach them to a Node with the COAPI function for Orphaned >> Nodes i always get the message below, even when i am the only one who is >> logged in (i prevented login completely except for myself and restarted >> the CF service and refreshed the tree). >> How can i fix them nevertheless ? >> can i fix them directly in the DB ? >> >> --- >> Diagnostics :: Orphaned Nodes >> moveBranch Lockout >> Another editor is currently modifying the hierarchy. Please refresh the >> site overview tree and try again. >> --- > > > Orphaned nodes utility is broken I believe. The error you are seeing is > nothing to do with the moveBranch lockout -- its just the default > try/catch error. > > You can recover these manually. Orphans are effectively dmNavigation > objects that have no parent in the nested_tree_model -- query to find > these. You want to reattach them to a node in the tree to recover them > -- use the tree.cfc component methods to attach the node. > --- You are currently subscribed to farcry-dev as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
