We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 3749
    • 24,544 Posts
    I doubt if this means anything, but I thought I’d mention it. WC3 Validation:

    Line 34, Column 15: reference to non-existent ID "ajaxSearch_submit".
    <label for="ajaxSearch_submit">

    Bob
      Did I help you? Buy me a beer
      Get my Book: MODX:The Official Guide
      MODX info for everyone: http://bobsguides.com/modx.html
      My MODX Extras
      Bob's Guides is now hosted at A2 MODX Hosting
      • 18646
      • 106 Posts
      Ok I think I know what’s causing the issue. Though process of elimination of most everything else I’ve tried, the issue might have to do with the fact that the last two buttons on the top menu are actually appended to the end of the &outerTpl wayfinder class. Everytime the nav breaks, those two buttons disappear. But, I can still see them in the HTML that’s being produced when I view the source!

      The reason I had to code the nav this way was because all of the other top buttons need special IE7 conditional tags; but if you apply those tags to the last two buttons "Test Drive" and "Contact", the nav breaks.

      So what I have, is an &outerTpl wrapper that looks like this:

      <div>
      	[+wf.wrapper+]
      <ul class="select">
                  <li><a href="index.php?id=21">Test Drive</a></li>
                </ul>
                <ul class="select">
                  <li class="contact"><a href="index.php?id=22">Contact</a></li>
                </ul>
      </div>


      Notice the last two buttons are hard coded at the end. Then, In the wayfinder call, I just exclude the page ID’s from the wayfinders regular output via &excludeDocs=`21,22`. This doesn’t seem to be an issue for any browser except Firefox. What should happen is the nav should build out, and then the last two nav items should be added to the back of the nav via the &outerTpl wrapper. If you load the page and look carefully, you can see that’s what happening very quickly. Firefox doesn’t want to play along with this plan.

      That’s what I think is happening :/

      Regards,
      Matt
        • 3749
        • 24,544 Posts
        Matt,

        It sounds like you’re making progress. I wonder, though, if you really need to nest your top menu items that deeply:

        topnav
        nav
        table
        div (no class or id)

        It looks like you’re down four levels before you get to anything that would be rendered. It might be easier to figure out what’s going wrong if it were less complex.

        I also don’t understand why you need to do anything special to the last two main items for IE7. I don’t see anything different about them that would prevent them from being handled like the others. Maybe I’m missing something.

        Bob
          Did I help you? Buy me a beer
          Get my Book: MODX:The Official Guide
          MODX info for everyone: http://bobsguides.com/modx.html
          My MODX Extras
          Bob's Guides is now hosted at A2 MODX Hosting
          • 18646
          • 106 Posts
          I tried cleaning out some of the nesting in my nav, but it’s still breaking, I don’t think that’s the issue. Does it matter the order that you call the chunks for the nav in wayfinder? What I mean is, on this site at the bottom:
          http://www.muddydogpaws.com/development/wayfinder/parameters.html

          Template Processing Order

          1. startItemTpl
          2. parentRowHereTpl
          3. innerHereTpl
          4. hereTpl
          5. activeParentRowTpl
          6. categoryFoldersTpl
          7. parentRowTpl
          8. innerRowTpl
          9. rowTpl

          It details the order which the wayfinder code processes the parts. Does my wayfinder call have to follow this exact order, or does that not matter?
          Also, I find it really odd that when i refresh the page with the broken nav, it fixes itself. This also happens when I disable my cache using the firefox web developer toolbar. Is there a way via the modx backend administration to force a cache cleaning each time the top nav is loaded?

          Regards,
          Matt
            • 3749
            • 24,544 Posts
            Quote from: matt6805 at Feb 22, 2008, 01:33 PM

            I tried cleaning out some of the nesting in my nav, but it’s still breaking, I don’t think that’s the issue. Does it matter the order that you call the chunks for the nav in wayfinder? What I mean is, on this site at the bottom:
            http://www.muddydogpaws.com/development/wayfinder/parameters.html

            Template Processing Order

            1. startItemTpl
            2. parentRowHereTpl
            3. innerHereTpl
            4. hereTpl
            5. activeParentRowTpl
            6. categoryFoldersTpl
            7. parentRowTpl
            8. innerRowTpl
            9. rowTpl

            It details the order which the wayfinder code processes the parts. Does my wayfinder call have to follow this exact order, or does that not matter?
            Also, I find it really odd that when i refresh the page with the broken nav, it fixes itself. This also happens when I disable my cache using the firefox web developer toolbar. Is there a way via the modx backend administration to force a cache cleaning each time the top nav is loaded?

            Wayfinder accesses the arguments in the snippet call by name rather than position, so they can be in any order.

            With respect to caching, whichever of the following you’re using, try the other one:

            [!Wayfinder? etc. etc. !]
            
            [[Wayfinder? etc. etc. ]]

            Bob
              Did I help you? Buy me a beer
              Get my Book: MODX:The Official Guide
              MODX info for everyone: http://bobsguides.com/modx.html
              My MODX Extras
              Bob's Guides is now hosted at A2 MODX Hosting
              • 18646
              • 106 Posts
              Issue solved! The issue was that the HTML coder who handed me the original code had display: table in the CSS. I took it out and like magic it works. Thanks for everyones help.

              Regards,
              Matt