Maybe try removing everything from the nested_tree_objects table.  The
rebuild function might be getting messed up because of data still in there.
Of course back your database up before you do that:P 

-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On
Behalf Of Duncan
Sent: Monday, 16 April 2007 11:20 PM
To: farcry-dev
Subject: [farcry-dev] Re: Urgent Navigation tree problem


Yes - we had tried the rebuild tree function but unfortunately this made no
difference :(

On Apr 16, 1:52 pm, Scott Talsma <[EMAIL PROTECTED]> wrote:
> Alternatively, you can go into Admin/COAPI and run "rebuild tree".
> Usually that works, although the instructions suggest having a DB 
> backup just in case.  It has never been a problem for me.
>
> Duncan wrote:
> > Hello all - i have an urgent navigation tree issue.
>
> > We have a site of about 1400 pages running on farcry 3.0.1 with MSSQL.
>
> > We currently have a problem where loads of navigation nodes have 
> > disappeared from the site (i think about 700!).  I have looked at 
> > the dmNavigation table and all the data still appears to be there.
> > However there are about half the number of entries in the 
> > nested_tree_objects table.  I have read in a few posts that this can 
> > occur when multiple tree operations are being carried out at the 
> > same time.  Is there any way to recover the structure from this
situation?
>
> > I have been thinking about attempting to restore the 
> > nested_tree_objects table from a previous days backup but am a 
> > little worried that this will just introduce new problems?
>
> > Any help would be appreciated!
>
> > Thanks,
> > Duncan





--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"farcry-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/farcry-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to