We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 51696
    • 12 Posts
    We have a site that works correctly - i.e. viewing each page with chunks for headers etc. We tested each page before we introduced wayfinder. The menu gets generated almost correctly, but we need some help:

    Here is a snippet of our "Original HTML" along with the Wayfinder generated output:
    <ul class="sf-menu hidden-xs hidden-sm">
    <li class="active"><a href="index.html">Home</a></li>
    <li><a href="aboutus.html">About US</a></li>
    <li><a href="#">Galleries</a>
    <ul>
    <li><a href="awards.html">Awards</a></li>
    <li><a href="tombstones.html">Tombstones</a></li>
    <li><a href="allgalleries.html">All Galleries</a></li>
    </ul>
    </li>
    <li><a href="contact.html">Contact</a></li>
    </ul> -->>

    <ul class="sf-menu hidden-xs hidden-sm">
    <li class="first active"><a href="http://cmstest.lan/modx/" title="Home" >Home</a></li>
    <li><a href="index.php?id=4" title="About Us" >About Us</a></li>
    <li class="last"><a href="index.php?id=3" title="Contact" >Contact</a></li>

    </ul>

    Here is our Wayfinder Call: [[!Wayfinder? &startId=`0`]]

    We have switch installed (a post somewhere said to install it), but we have not used it.

    This site is based on bootstrap and the menu actually does display 100% correctly, and the Menu Option is styled correcyly (wow), for the active page.

    it is the link that goes back to the "Home" page, it drops us into the root of the site.

    We are all but ready to roll this out, but obviously not like this, so any/all help is greatly appreciated.

    Thnaks.
      • 51696
      • 12 Posts
      Really, no one?
      • Do you have an error_page (a not found resource) configured in your system settings? If you don't, MODX will use your home page as the not-found page. Having a dedicated not-found page can help you to understand if the links are not being generated as you expect.
          Studying MODX in the desert - http://sottwell.com
          Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
          Join the Slack Community - http://modx.org
        • It also helps if you enclose your posted code in the "code" tags, the <> button in the editor's toolbar.
            Studying MODX in the desert - http://sottwell.com
            Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
            Join the Slack Community - http://modx.org
            • 51696
            • 12 Posts
            Thanks for the replies. I wanted to make sure that we did everything right.

            We do have have an error page, but we never got sent to it. The page is registered in sys settings etc. and we tested it many times by faking page requests. So we are comfy that it works.

            The site worked fine on our Centos 6.6 box, so this suggested to us a PHP or Perms issue.

            We finally recreated the site from scratch. We had all TVs, snippets and chunks saved - so it didn't take long - kudo to ModX for this... On our Umbraco and C5 sites, this was a daunting task.

            The recreated site seems to works fine and without incident.

            The only thing we can think of is that it may have been an NTFS thing - maybe an Inheritance issue - who knows.

            I should have mentioned it was on a Winbox - sorry about that.

            As a NEW rule of thumb, we now test sites that run on a Winbox with out "ix" box. Should help in providing more specific details in future posts.

            Again - tx for the suggestions.

            We're having issues with Gallery and Galleriffic, but those are likely just a learning thing.