We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 24007
    • 38 Posts
    Have just recently switched to Revolution and begun to experiment with it.

    I have created a simple 1 level navigation with wayfinder with items being called.

    HOME | BLOG | PORTFOLIO | CONTACT

    The BLOG page is a container



    Wayfinder chunk "topNav"
    <li><a href="[[+wf.link]]" title="[[+wf.title]]">[[+wf.linktext]]</a>[[+wf.wrapper]]</li>
    


    Template wayfinder call
    [[Wayfinder? &startId=`0` &level=`1` &colTpl=`topNav`]]
    


    All the links work on the menu, however when I am on the blog page (document) and then click on another link in the top menu there is a problem.

    In the browser URL box i will get something like >>> http://www.mysite.com/myblog/contact.html
    Naturally contact.html is a root document and therefore cannot be found.

    I know I can turn off the browser suffix ’/’ or at least make it blank and then it works.
    For my blog purposes I would like to retain the container/document.html URL for blog posts.

    Therefore the question is can someone help me with an amendment to the code above to make this work.

    Regards,

    Psypha


      • 33968
      • 863 Posts
      First, you could check that you are using the <base href="[[++site_url]]" /> in the <head></head> section of your template.

      If that doesn’t do it, you could force Wayfinder to use absolute paths by adding [[++site_url]] to the link in your ’topNav’ chunk:
      <li><a href="[[++site_url]][[+wf.link]]" title="[[+wf.title]]">[[+wf.linktext]]</a>[[+wf.wrapper]]</li>
      
        • 24007
        • 38 Posts
        Yes thanks for the pointer there, timely response sir.

        I checked my template code and I had used the base href, however the syntax I used was Evolution and not Revolution.

        Doh!

        Many thanks

        Psypha
          • 33968
          • 863 Posts
          There should be a ’head-smack’ smiley tongue

          You wouldn’t be the first to be caught out there though. Note also that it’s been suggested to use the uncached version:
          [[!++site_url]]
          

          to prevent errors if you end up using ssl on some parts of your site (with the https:// prefix).