There is a setting in umbraco settings.config for

HideTopLevelNodeFromPath

This should be true, and you should see this go agaw

Dan

yeah, i found that property in web.config

   <add key="umbracoHideTopLevelNodeFromPath" value="true" />

I changed it to false and link to doc = "1079" which is the correct id. 

I then changed it back to true and link to doc = "home/films" which is incorrect.

@dan : maybe your thinking of another property in "umbracosettings.config?" 

I should prefix all this by saying that it was all working correctly until an editor accidentaly deleted home. Which is the cause of this mix up. 

OK, i see what happened. Somehow the "path" field in the umbracoNode table got out of sync. Easy fix

UPDATE umbracoNode

SET path = '-1,1044,1079'

WHERE id = 1079

Remember that umbraco re-calculates the node's url when you publish it (or move it via the ui). So rather than a database hack, perhaps you could have simply opened the page for editing and then published it again? Or perhaps right-click the home page and republish it and all its children?

An idea for the next person having a similar issue :)

cheers,
doug.

oh i spoke to soon. As doug saids usually "Link to document" issues are resolved by republishing. I've republished serveral times and am still having this issue

The content in bold is displaying the wrong address. 

content
- home
- films
- A ( /home/films/a )  // incorrect
- B ( /films/b )   // correct

I've look in the umbracoNode table and the path seems correct (-1,-20,1044,1079,1259)

wow, thanks doug. Made my day :)

All is working correctly. I suspect my app is throwing exceptions where i publish ( a job for monday )  

I was able to fix this when some like the following. Obviously try this out a test installation first. 

update umbracoNode set path = replace(path, '-1,-20,1044,1079,', '-1,1044,1079,') where path like '-1,-20,1044,1079,%'

is working on a reply...