We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
MODX Community Forums Archive

Answered Wayfinder - Two separate menus. Help please

    • 41653
    • 18 Posts
    keithbrook Reply #41, 14 years ago

    Well, it seems that someone has put [Solved] on the thread title which I assume means that you've lost patience with me.

    That's a shame because I've only been using Modx for a week which explains why I know so little.

    Considering it's only a week I thought I was doing quite well, actually.

    I'll battle on for a while and see how I do.

    Keith

      • 10208 ☆ A M B ☆
      • 1,780 Posts
      Frogabog Reply #42, 14 years ago
      Haven't lost patience. I suppose technically it is solved, since the solution is within. It doesn't mean you can't still post for help to get it working.

      You don't want to know how long I've been working to get to the limited understanding that I have now of MODX, you're getting it rather quick IMO.
        Frogabog- MODX Websites in Portland Oregon
        "Do yourself a favor and get a copy of "MODX - The Official Guide" by Bob Ray. Read it.
        Having server issues? These guys have MODX Hosting perfected - SkyToaster
        • 41653
        • 18 Posts
        keithbrook Reply #43, 14 years ago

        I wasn't complaining about the service, which was wonderful.

        It just left me with the feeling that you'd have enough of me.

        It's ok, I'm going to stick with what I've got because although the solution may have been within, it was sometimes not explained where this stuff goes. The last one being the example that triggered Susan removing her post and the topic being marked [Solved].

        It's because I've only been doing it for a week that prompted me to seek wise council from experts.

        Keith
          • 10208 ☆ A M B ☆
          • 1,780 Posts
          Frogabog Reply #44, 14 years ago
          I think she did that because we posted at the same time, the same thing.

          So at what step did we lose you there? Is your parent clickable still?
            Frogabog- MODX Websites in Portland Oregon
            "Do yourself a favor and get a copy of "MODX - The Official Guide" by Bob Ray. Read it.
            Having server issues? These guys have MODX Hosting perfected - SkyToaster
            • 22427
            • 793 Posts
            ottogal Reply #45, 14 years ago
            @Frogabog
            In the categoryFolderTpl (reply #40) you forgot the <a>:
            <li[+wf.classes+]><a>[+wf.linktext+]</a>
             [+wf.wrapper+]
</li>
            Or you omit both <a> and </a>, with the same result: The linktext is not clickable. [ed. note: ottogal last edited this post 14 years ago.]
              • 10208 ☆ A M B ☆
              • 1,780 Posts
              Frogabog Reply #46, 14 years ago
              I copied Susan's post :~}

              (admitting that I didn't read it!)
                Frogabog- MODX Websites in Portland Oregon
                "Do yourself a favor and get a copy of "MODX - The Official Guide" by Bob Ray. Read it.
                Having server issues? These guys have MODX Hosting perfected - SkyToaster
                • 22427
                • 793 Posts
                ottogal Reply #47, 14 years ago
                Yes, I saw it afterwards.
                I'm not sure if it makes a difference with or withour the "a" tag. Presumable it is necessary to let the submenu fly out? Don't know how this is done here.
                • discuss.answer
                  • 22427
                  • 793 Posts
                  ottogal Reply #48, 14 years ago
                  To the @INHERIT problem, Susan wrote:
                  I think you could use an output snippet instead, fetching the parsed output value of the TV using one of the API functions.
                  This snippet would do it (referring to my TV "in_menu" from above):
                  <?php
$output = '';
$v = $modx->resource->getTVValue('in_menu');
if ( $v == '' ) {
    &output = 'empty';
} else {
    &output = 'not empty';
};
return $output:

                  • discuss.answer
                    • 10208 ☆ A M B ☆
                    • 1,780 Posts
                    Frogabog Reply #49, 14 years ago
                    Now my brain hurts... So I'm switching an If not empty snippet in the template, for a new checkbox not empty snippet... ok. I can go with that.

                    Although isn't this what If does? omy, now I'm thoroughly confused.
                      Frogabog- MODX Websites in Portland Oregon
                      "Do yourself a favor and get a copy of "MODX - The Official Guide" by Bob Ray. Read it.
                      Having server issues? These guys have MODX Hosting perfected - SkyToaster
                    • discuss.answer
                      • 22427
                      • 793 Posts
                      ottogal Reply #50, 14 years ago
                      @keithbrook

                      No, we won't you get lost here...

                      Certainly it is confusing that the thread was a bit splitting up in different subjects - tree structure, template variables and the non clickable items problem.

                      To sort it out: Having two containers ('Top Menu Documents' and 'Left Menu Documents') in the tree is indeed the adequate structure for Wayfinder's way to fetch the wanted resources for a menu. In that sense the subject of the thread title was solved.

                      My proposal with the TV was a side step, may be interesting, but leading to other questions like the @INHERIT binding and perhaps not really helpful for you. You can ignore this part of the discussion, of course.

                      Remains the non clickable items question. As far as I see, it is enough to set the link attribute
                      rel="category". Setting the template to (empty) instead is no solution if you want to use TVs. (No, I won't sidestep again... And ignore my other sidestep to FirstChildRedirect - it may irritate a visitor of the site who doesn't expect this reaction to his click.)

                      So, with this setting, Frogabog's WF call (in reply #40) with the corrected &categoryFoldersTpl
                      <li[+wf.classes+]><a>[+wf.linktext+]</a>
             [+wf.wrapper+]
</li>
                      should output your wanted result.
                      If it does not, we will have a nearer look again.