We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 23235
    • 40 Posts
    I am building a blog using Ditto. I wanted to add tags to the blog articles so I can then categorize the articles by their tags. I found a nice screencast at the Ditto support site http://ditto.modxcms.com/screencast/tagging.html Using this I was able to add tags to my articles, but the tag links go nowhere. They don’t filter the results within that page which is supposed to be the default behaviour, and they don’t go to the landing page I tried to implement. I can’t find anything in the screencast that I didn’t do. I am using the newest stable release of MODX and whatever version of Ditto that comes with that. If it helps, the blog I am working on can be found at the following address http://www.yoursivet.com/pageblog.php Any help would be greatly appreciated.
      • 3749
      • 24,544 Posts
      Is there a snippet on the pageblog.php page that’s supposed to interpret the "tags" and "start" arguments in the URL and redirect to another page? It could be that that snippet is either not working, missing, or has its name misspelled.
        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
        • 23235
        • 40 Posts
        No there is other snippet call other than Ditto on that page. The screen cast didn’t call for one. Here is what the tagLinks is generating for one of the tags, if that helps: <a href="/pageblog.php?tags=general%2C&amp;start=0" class="ditto_tag" rel="tag">general,</a. The tag being general.
          • 23235
          • 40 Posts
          Okay, I’m making progress. I’ve got the landing page working. I wasn’t capitalizing the letter D in &tagDocumentID. However, it is still not filtering right. No matter which tag I click, it filters to the general tag. I think it is related to that really long query string that the link is generating. Let me know if you have any ideas.
            • 3749
            • 24,544 Posts
            It’s only getting one post for me, no matter what I select -- general should get two (unless there’s a limit parameter that’s set to 1). I’m afraid I don’t have anything helpful to suggest.
              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
              • 16278
              • 928 Posts
              The %2C in the URL should not be there - it’s a comma, where there should just be the tag followed by & and the next parameter.

              I haven’t looked at the screencast, so I don’t know what it advises, but I’d guess there’s a problem somewhere with your tag delimiters. What do your Ditto call and tag TV definition look like?
              smiley KP
              http://www.pogwatch.com/ditto/ditto-extenders/ditto-tagging.html
                • 23235
                • 40 Posts
                Here is my Ditto call for the blog page
                [[Ditto? &parents=`9` &tpl=`blogDisplay` &tagData=`myTags` &tagDelimeter=`, ` &tagDocumentID=`12` ]]
                Here is my DItto call for the Tag Landing Page
                [[Ditto? &parents=`9` &tpl=`blogDisplay` &tagData=`myTags` &tagDelimeter=`, ` ]]
                There’s nothing special about my TV, it’s got a name, caption and description. It’s input type is text. It has been assigned a template and category. Hope this helps.
                  • 16278
                  • 928 Posts
                  Try &tagDelimiter rather than &tagDelimeter huh
                  wink KP
                    • 23235
                    • 40 Posts
                    Oh man, I had great hope that this was it, but it’s still not filtering right. Thanks for catching that error though. Back to the drawing board.
                      • 16278
                      • 928 Posts
                      It’s still probably a matter of the delimiters. Your call specifies the delimiter as comma+space; the default delimiter is space; and you get a comma showing up in the URL query string. I haven’t checked whether multiple-character delimiters are OK, but I suggest you try just a space or just a comma as the actual delimiter, and use &tagDisplayDelimiter=`, ` to format the output.
                      laugh KP