Hi René

What does your full code look like where you experience this issue?

If you don't attach a template to the date elements then they should not be populated with a URL either if I remember correctly.

But it would be nice to see the full code that is causing the issue - I have used a similar approach as the one you illustrate on the image above and not had any trouble with changes in navigation even though I loaded content from the "Data/Elements" section...so need to see the issue in action :)

/Jan

Hi René,

That actually makes sense, because .Site() goes all the way up to level 1, so when you're in the "Forside" section it'll return Forside, and in the Data section, the Data node will be hit. What you really want is to go all the way to the root node and then pick the Forside node below that - something like this:

var home = @CurrentPage.Root().Down("ForsideAlias");

This should work if I understand this page correct.

"ForsideAlias" should of course be replaced with the actual nodeTypeAlias of your "Forside" node

/Chriztian

Hi Jan and Chriztian

Chriztian:
I did not manage to get it working with your example.

Jan:
See my code below:

@inherits Umbraco.Web.Mvc.UmbracoTemplatePage

@{ var selection = CurrentPage.Site().Children.Where("Visible"); }

<nav class="navbar navbar-custom navbar-fixed-top" role="navigation">
  <div class="container">
    <div class="collapse navbar-collapse" id="custom-collapse">
      <ul class="nav navbar-nav navbar-right">
      @foreach (var item in selection)
      {
        <li class="@(item.IsAncestorOrSelf(CurrentPage) ? "current" : null)">
          <a href="@item.Url">@item.Name</a>
        </li>
      }
      </ul>
    </div>
  </div>
</nav>

On this project it is very important that almost all data / content is stored in the data folder, because it should be very easy to change the frontpage to another layout / template without deleting all the children below the frontpage.

// René

Hi René

Ok, I understand your issue now.

But wondering what did not work when you tried using Chriztians example? Did you get a yellow screen of dead? If so what did the error message say? And what did the error message in the /app_data/logs file say?

It should be fairly easy to achieve what you want using CurrentPage.AncestorOrSelf(1).Children.Where("Visiable") otherwise though - But since .Site() should do that for you according to what Chriztian writes above it might be more conventional to use that approach :)

Looking forward to hearing from you.

/Jan

Hi Jan

No the navigation just disappears on every page.

// René

I am following Chriztian's example. Try to see this code, am I doing something wrong?

@{ var home = @CurrentPage.Root().Down("HomeSlider"); }

<nav class="navbar navbar-custom navbar-fixed-top" role="navigation">
    <div class="container">
        <div class="collapse navbar-collapse" id="custom-collapse">
            <ul class="nav navbar-nav navbar-right">
                <li><a href="/">Forside</a></li>
                @foreach (var item in home)
                {
                    <li>
                        <a href="@item.Url">@item.Name</a>
                    </li>
                }
            </ul>
        </div>
    </div>
</nav>

// René

Hi Chriztian

That's perfect now it is working.

Thanks!

// René

is working on a reply...