I am now experiencing this probem with farcry 2.3 in nested_tree_objects, what in nLeft and nRight all about.
If I want to manual clean this up, what is the rule for working out the correct value? Is it a sequention this thing?? On Thu, 03 Mar 2005 10:59:57 -0500, Jeff Coughlin <[EMAIL PROTECTED]> wrote: > Daniel Niklasson wrote: > > When working with the locations of my navigation nodes, moving them up > > and down by right clicking on them and choosing "move up", "move down", > > everything, and I mean everything got totally **** up. > > This has happened to me a few times as well. If you move a dmNavigation > node it is best to wait for the tree (javascript) to finish updating > before moving another object. I have corrupted too many trees this way > in the past. I'm not sure if fixing this bug is on anyone's radar atm > for the tree code (javascript) is quite complex and could have > reprocussions for backwards compatability if the code is rewritten. > > When moving the nav nodes before the js has finished updating on the > client machine the nLeft and nRight values can get messed up (thus > causing your problems). I was able to fix my problem (once or twice) by > going to Admin/COAPI/ and repaired the tree in there. A warning though, > backup your DB first. A couple times this caused more damage to my tree > than fixing it. > > The only other way I was able to fix this problem (when the COAPI tree > fix didn't work) was to revert back to a DB backup from the night before. > > -Jeff C. > > --- > 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/ > --- 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/
