We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 37272
    • 216 Posts
    I have a side block. Sandwiched between the opening and closing DIVs for the block within the template is a tempate variable for the side block content. I’ve created a chunk of HTML that closes and reopens this block - in effect, it turns one block in to two. I can continue inserting these breaks for as many side blocks I wish to create. This is great, except I don’t want to add all the content to this one TV. I can create other chunks containing content, and call these chunks to these psuedo blocks (the space beween each block-break), but I’d like some way of calling documents for this purpose (I am trying to set up an easy way for members to have their own customizable home page). I can create @DOCUMENT bindings, but this involves creating TVs again. Is there some simple way of calling documents directly into the TV, so all the member need do is something like this:

    {{navigation-block}}
    {{side-page-break}}
    {{my-profile}}
    {{side-page-break}}
    {{links}}

    Except, I don’t want to use chunks for the content, just block breaks.

    I did try @DOCUMENT ID, and it worked, but only for the first document.

    Thanks.
      • 37272
      • 216 Posts
      I’ve edited my above post and title - I hope it is a little clearer.
        • 37272
        • 216 Posts
        Hi,

        If I understand correctly, members will still need to create TVs for this to work. I need a system that allows many users to use the same template, and are able to easily import the content of one document to another (their side bar). I’d just like it to be modular for them. If all else fails, then they will just have to use one document for the side bar, calling the html chunks to divide it up into several blocks, but placing all their content for the side bar within this one side bar document.

        I was also hoping to use this myself though, able to reuse documents for side blocks without the hassle of using individual @DOCUMENT binding TVs for each content block for content.

        I’m sure I’m being less than clear. How do I easily import the content of one document to another without having to create new TVs for each new document? I’m trying to work up system that anyone can use, with nothing more than documents and a few chunk calls.

        Thanks.
          • 18830
          • 161 Posts
          Maybe DropDownTree is the right solution for you?

          http://modxcms.com/DropDownTree-1669.html
            • 7231
            • 4,205 Posts
            If I understand correctly, members will still need to create TVs for this to work.
            From my understanding the solution would only call for one pre-defined TV where the users could list the block by id separated by commas 12,14,15 and a snippet to do the logic.

            What I have always thought would be cool would be a WP widget-like content block manager where the user could drag-n-drop and sort determined blocks with either chunks or snippets. This would be a cool module. Maybe if we ask Santa grin
              [font=Verdana]Shane Sponagle | [wiki] Snippet Call Anatomy | MODx Developer Blog | [nettuts] Working With a Content Management Framework: MODx

              Something is happening here, but you don't know what it is.
              Do you, Mr. Jones? - [bob dylan]
              • 37272
              • 216 Posts
              Quote from: dev_cw at Dec 21, 2007, 10:40 AM

              If I understand correctly, members will still need to create TVs for this to work.
              From my understanding the solution would only call for one pre-defined TV where the users could list the block by id separated by commas 12,14,15 and a snippet to do the logic.

              What I have always thought would be cool would be a WP widget-like content block manager where the user could drag-n-drop and sort determined blocks with either chunks or snippets. This would be a cool module. Maybe if we ask Santa grin

              Ah, so ganeshXL’s suggestion is the way to go then? I will give it a try. If it isn’t already painfully obvious, I cannot code, but I think there is enough there for me try it out at least.

              Thanks dev_cw, and thank you ganeshXL.

              Edit: no, I misunderstood. Hmmm, a ’snippet to do the logic’ - that’s beyond anything I could even attempt. sad
                • 37272
                • 216 Posts
                Quote from: Mazso at Dec 21, 2007, 10:02 AM

                Maybe DropDownTree is the right solution for you?

                http://modxcms.com/DropDownTree-1669.html

                Hi,

                If I understand its function, it simply to add a drop down of available TVs. My members would need their own TVs and that’s what I’m trying to avoid. I just need some simple way for them to add the content of one of their documents to another of their documents. It would be nice for me too, but at the end of that day I have multitude of other options available to me.
                  • 37272
                  • 216 Posts
                  Is this what I need?

                  Thanks.
                    • 7231
                    • 4,205 Posts
                    DynContent and DetField are two snippets for getting content from one page to another. GetField is much more flexible. If I remember correctly the difference is that GetField will get pre-parsed content while DynContent will get parsed content.
                      [font=Verdana]Shane Sponagle | [wiki] Snippet Call Anatomy | MODx Developer Blog | [nettuts] Working With a Content Management Framework: MODx

                      Something is happening here, but you don't know what it is.
                      Do you, Mr. Jones? - [bob dylan]
                      • 37272
                      • 216 Posts
                      Quote from: dev_cw at Dec 21, 2007, 12:02 PM

                      DynContent and DetField are two snippets for getting content from one page to another. GetField is much more flexible. If I remember correctly the difference is that GetField will get pre-parsed content while DynContent will get parsed content.

                      Thanks. I’ve just finished upgrading, so will give a go. wink I’m sure there is no reason what I need fetch the parsed content, so I’ll go with your suggestion.