We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 28042 ☆ A M B ☆
    • 24,524 Posts
    If you want all pages to always have the same content, just use a chunk. TVs are for when you want different pages to have different content.
      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
      • 33440
      • 31 Posts
      In a real world scenario if I was building a site for a client that they were going to manage after handover...that wouldn’t be such a great option. As they would have to edit via the chunk to update the content.

      I’m trying to visualise the best methods to set up a website using MODx, where the completed website would be managed by the client, with as little interaction with initial designer (me) as possible.

      That is the scenario I am always up again. ’Hard’ clients, who barely want to spend money but want the world in return and always ask "will we be able to update the site". Even though on handover 97% don’t update the site!
        • 28042 ☆ A M B ☆
        • 24,524 Posts
        Then a TV with @DOCUMENT binding might be the answer. Have a container resource dedicated to holding your TV-feeding resources, with a Wayfinder or Ditto call, and link to it in the QuickManager menu.

        Usually, though, a "latest news" block is fed by a Ditto call with your news article container as the ’&parent’ parameter. That way it is automatically updated every time a new news article is added.
          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
          • 33440
          • 31 Posts
          Quote from: sottwell at Mar 30, 2010, 12:14 AM

          Then a TV with @DOCUMENT binding might be the answer. Have a container resource dedicated to holding your TV-feeding resources, with a Wayfinder or Ditto call, and link to it in the QuickManager menu.

          Usually, though, a "latest news" block is fed by a Ditto call with your news article container as the ’&parent’ parameter. That way it is automatically updated every time a new news article is added.

          Thanks Susan. I think I’ll slow down at this stage with the website, and read up a lot more about what it is I’m trying to set up. The second paragraph sounds like the preferable way. Just have to get my head around more stuff.
            • 33440
            • 31 Posts
            I’ve started using MODx again with MODx Revolution. But I’ve forgotten most of what I learnt using my first test/play site using Evolution.

            I’ve started a new site to play with and (again) am having problems with the navigation and wayfinder. I think I found it easier last time because a whole bunch of chunks and snippets installed by default in the package of MODx I was using.

            I have installed Wayfinder, and I think I need some snippets. I also think I am having real problems understanding wayfinder...I might just be a little bit too green. I can’t quite work out how to reference the CSS...among other stuff. I’m having problems progressing from HTML and CSS I guess. I’m having a more difficult time this time around...but not because of MODx.

            http://zelky.com.au/modx/

            But here is my code:

            HTML
            <html>
            <head>
            <title> [[*pagetitle*]] | [[++site_name]]</title>
            <meta http-equiv="Content-Language" content="English" />
            <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
            <link rel="stylesheet" type="text/css" href="[[++base_url]]manager/templates/Zelky/mainstyle.css" />
            <link rel="stylesheet" type="text/css" href="[[++base_url]]manager/templates/Zelky/chrometheme/chromestyle.css" />
            <script type="text/javascript" href="[[++base_url]]manager/templates/Zelky/chromejs/chrome.js"></script>
            <base href="[[++site_url]]"></base>
            </head>
            <body>
            <div id="wrap">
            <div id="header"></div>
            <div id="chromestyle">
            [[!Wayfinder? &startId=`0` &level=`1` &rowTpl=`rowTpl`!]]
            <!-- end of navigation -->
            </div>
            <div id="wrap">
              <div id="left">
            [[$leftcontent]]
            </div>
            <div id="content">
            		[[$content]]
            </div> <!-- end content-main -->
            
            <div style="clear:both;"> </div>
            
            </div>
            <div id="footer">
             	[[$footer]]
            </div> <!-- end of site-info -->
            </body>
            </html>
            


            CSS
            .chromestyle{
            	width: 894px;
            	font-family: verdana;
            	font-size: 10px;
            	font-weight: 400;
            	border-left: solid 3px #eee;
            	border-right: solid 3px #eee;
            	margin: 0 auto;
            	letter-spacing: .3em;
            }
            
            .chromestyle:after{ /*Add margin between menu and rest of content in Firefox*/
            	content: "."; 
            	display: block; 
            	height: 0; 
            	clear: both; 
            	visibility: hidden;
            }
            
            .chromestyle ul{
            	border-bottom: 1px solid #999999;
            	width: 894px;
            	background: url(chromebg.gif) center center repeat-x; /*THEME CHANGE HERE*/
            	padding: 4px 0;
            	margin: 0;
            	text-align: center; /*set value to "left", "center", or "right"*/
            }
            
            .chromestyle ul li{
            	display: inline;
            }
            
            .chromestyle ul li a{
            	color: #494949;
            	padding: 4px 7px;
            	margin: 0;
            	text-decoration: none;
            	border-right: 1px solid #DADADA;
            	border-left: 1px solid #DADADA;
            }
            
            .chromestyle ul li a:hover, .chromestyle ul li a.selected{ /*script dynamically adds a class of "selected" to the current active menu item*/
            	background: url(chromebg-over.gif) center center repeat-x; /*THEME CHANGE HERE*/
            }
            
            /* ######### Style for Drop Down Menu ######### */
            
            .dropmenudiv{
            	position:absolute;
            	top: 0;
            	border: 1px solid #BBB; /*THEME CHANGE HERE*/
            	border-bottom-width: 0;
            	font-family: verdana;
            	font-size: 10px;
            	font-weight: 400;
            	line-height:18px;
            	z-index:100;
            	background-color: white;
            	width: 200px;
            	visibility: hidden;
            	filter: progid:DXImageTransform.Microsoft.Shadow(color=#CACACA,direction=135,strength=4); /*Add Shadow in IE. Remove if desired*/
            }
            
            
            .dropmenudiv a{
            	width: auto;
            	display: block;
            	text-indent: 3px;
            	border-bottom: 1px solid #BBB; /*THEME CHANGE HERE*/
            	padding: 2px 0;
            	text-decoration: none;
            	color: black;
            }
            
            * html .dropmenudiv a{ /*IE only hack*/
            	width: 100%;
            }
            
            .dropmenudiv a:hover{ /*THEME CHANGE HERE*/
            	background-color: #F0F0F0;
            }
            
            


            Chuck - rowTpl
            <li[+wf.classes+]><a href="[+wf.link+]" title="[+wf.title+]">[+wf.linktext+]</a>[+wf.wrapper+]</li>


            Chuck - Navigation
            <li[+wf.classes+]><a href="[+wf.link+]"<[+wf.linktext+]></a>[+wf.wrapper+]</li>

              • 3109 ☆ A M B ☆
              • 894 Posts
              If your using Revolution (which I assume you are) you need to fix your chunks to use the proper syntax.

              [+wf.title+] is now [[+wf.title]] so on and so forth so once you fix those it should start working again.
                Benjamin Marte
                Interactive Media Developer
                Follow Me on Twitter | Visit my site | Learn MODX
                • 33440
                • 31 Posts
                That would be a great start! Thanks for kindly pointing that out benmarte.
                  • 3109 ☆ A M B ☆
                  • 894 Posts
                  It’s the small things that sometimes make us work the hardest, good luck.
                    Benjamin Marte
                    Interactive Media Developer
                    Follow Me on Twitter | Visit my site | Learn MODX
                    • 33440
                    • 31 Posts
                    Yeah that didn’t solve it but I also noticed I didn’t reference the javascript file for the nav in the header either...so I’ve got a bit of work ahead of me at my end.

                    Again...thanks.
                      • 33440
                      • 31 Posts
                      I’m back. I gave it a break as I was confused with the changes between releases.

                      I also started a new template - http://zelky.com.au/modx/, after going through this tutorial - http://jgulledge.wordpress.com/2010/06/26/learning-modx-tutorial-1-creating-a-template/.

                      My next challenge is to get the navigation working...

                      Thanks to everyone for your help in the past.

                      Update: This is so, so sweet. I’v managed to get the navigation up and running. Time to see if the second level works.
                      Update: The second level works with the default wayfinder code.

                      Sorry to keep adding to this original thread, but it’s a great way to track my progress. And now that I understand MODx better I can start to implement some of Susan’s great ideas which she suggested months ago, when I was still too green.