We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 19872
    • 1,078 Posts
    I'm looking at the actual paths that are generated in the source code. The 3 document are not being obtained from the same folder.
    The pound symbol really has be baffled.

    Typically, # is a null link. Having it be the same on all 3 simply does not make sense.

    In order for page links to be generated dynamically, there has to be a call to either a chunk, a snippet, or a template variable on the template rather than that string of html code, there would merely be [[$quicklinks]] or something to that effect.
      • 19872
      • 1,078 Posts
      I'm looking at the actual paths that are generated in the source code. The 3 document are not being obtained from the same folder.
      The pound symbol really has be baffled.

      Typically, # is a null link. Having it be the same on all 3 simply does not make sense.

      In order for page links to be generated dynamically, there has to be a call to either a chunk, a snippet, or a template variable on the template rather than that string of html code, there would merely be [[$quicklinks]] or something to that effect.
        • 49393
        • 13 Posts
        Does viewing the source code from the actual web page provide any insight?

        http://www.nelsondiocese.org/

        Totally has me baffled. I really appreciate your input though. Thanks for trying.
          • 19872
          • 1,078 Posts
          One other thing to maybe check.

          Do you see one of these pages in the Resource Tree. Like Prayer Requests for instance?
          If yes, go ahead and click on that resource so you can view it. Then click on the tab for template variables. See if perhaps there is some type of check box option that might seem like "Check Box to add this page to QuickLinks"

          There may be categories of template variables — tabs on the left. Basically groups of different template variables. Putting them in groups just makes them more organized. But if there are tabs, you can click on each and a few more template variable options may be displayed.
            • 19872
            • 1,078 Posts
            Viewing the source code tells me there are paths in there and they are simple a tags.

            Are you sure that you have the correct template? Sometimes I will hard code stuff or mock it up on one template that I use for developement, But then I will duplicate it, and erase much of the code and replace that code with snippets, chunks and template variables.

            Double check to see what the name of the template is that is associated with any of those 3 pages.
              • 19872
              • 1,078 Posts
              I see you confirmed: MODx 2.0.3 Revolution

              It's hard to get into the head of whoever created the site. Sorry if I'm running you all over the place. I'm just trying to think if it were me, how many different ways could I get links to appear down there.

              One way would be a chunk. I would create a chunk and give it an obvious name like "QuickLinks" or "FooterLinks". In that chunk I would just hard code the few items that I wanted people to be able to link to. Much like what you sent with the <div id="quicklinks....> But instead of "#", I would actually put the number of the resource in there. Then I would call that chunk on all the templates I was using. A chunk call in a template would look like this: [[$QuickLinks]] or [[$myChunksName]] Then every time a page loads on the internet that uses a template with that chunk call in it, would have all of the quick links in it.

              Another way would be with some type of menu snippet. Wayfinder is one, but wayfinder uses list style. I am not aware of it being able to generate standard a tags. But there could be a custom snippet or maybe another add-on that I am not familiar with, but even then, there would still have to be a call to the snippet on the template.

              That's why I was wanting you to look at one of those 3 resources again. And find the actual name of the template. Then go load that template in the manager and review the code again down near the bottom where the quicklinks menu would be.

                • 19872
                • 1,078 Posts
                Below is the quicklinks code. All this does is style that section. So any link in that section gets text that is kind of orange yellow. The region is 42px high. The font size is 1.3em which equates about 20 pixels high, and so on.

                I don't think your quicklinks is dynamically generated. My best guess is that you were looking at a practice or developement template or a template that is not being used in the site. There must be another template in which you will see something like [[~17]] instead of "#" for the links.

                You said you made a change to the code in that one template and nothing happened. That's probably because you made that change to the wrong template or a template that is not being used.

                Does that make sense?

                #quickLinks {
                	height: 42px;
                	background-color: #136597;
                	font-size: 1.3em;
                	color: #FFFFFF;
                	padding-left: 40px;
                	background-image: url(../images/shared/quicklinks_divider.png);
                	background-repeat: no-repeat;
                	background-position: center bottom;
                }
                #quickLinks a {
                	color: #eab831;
                	text-decoration: none;
                	padding-right: 8px;
                	padding-left: 8px;
                }
                  • 19872
                  • 1,078 Posts
                  Below is the quicklinks code. All this does is style that section. So any link in that section gets text that is kind of orange yellow. The region is 42px high. The font size is 1.3em which equates about 20 pixels high, and so on.

                  I don't think your quicklinks is dynamically generated. My best guess is that you were looking at a practice or development template or a template that is not being used in the site. There must be another template in which you will see something like [[~17]] instead of "#" for the links.

                  You said you made a change to the code in that one template and nothing happened. That's probably because you made that change to the wrong template or a template that is not being used.

                  Does that make sense?

                  #quickLinks {
                  	height: 42px;
                  	background-color: #136597;
                  	font-size: 1.3em;
                  	color: #FFFFFF;
                  	padding-left: 40px;
                  	background-image: url(../images/shared/quicklinks_divider.png);
                  	background-repeat: no-repeat;
                  	background-position: center bottom;
                  }
                  #quickLinks a {
                  	color: #eab831;
                  	text-decoration: none;
                  	padding-right: 8px;
                  	padding-left: 8px;
                  }
                    • 19872
                    • 1,078 Posts
                    One point — you mentioned you found a template in assets/templates.

                    Ah ha! That's not a modx template. Sorry. You were in the Files portion of the tree.

                    There are 3 tabs for the Tree. Resources. Elements. Files. You were looking at an html template file. Probably the working draft the design build or mockup up, which was then converted to work in MODx.

                    Do this:
                    1. Click on Resources
                    2. Click on the Resource name of one of the 3 quicklink names Prayers or one of the other two.
                    3. That resource will load. Make sure the first tab is clicked on. (sometimes they open with the last tab selected open). The first tab has the resource Name, the Alias. A whole bunch of fields, one of which is template. In that field will be the name of the template that that resource uses.
                    4. Remember that name.
                    5. Click on the tab "Elements" over in the tree.
                    6. Click on Templates if it is not toggled open. Usually they are all listed them. Might be 2 or 3 could be more.
                    7. Find the template you were supposed to be remembering smiley
                    8. Click on in and scroll down toward the end and see what you can find. Anything related to the code you sent me earlier... but with numbers in there within brackets and a tilde symbol? (i.e. [[~15]]

                    [ed. note: mmcgee last edited this post 11 years, 10 months ago.]
                      • 49393
                      • 13 Posts
                      So, I'm just trying to absorb all of this. One last question for tonight, sorry if this is dumb. Where should the active template be that I should be editing?

                      Files > ??

                      Thanks again