We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 37042
    • 384 Posts
    The subject of Chunks and Rich Text Editors was brought up at MODXpo Europe recently and Ryan mentioned that it shouldn't be a problem. Is there any movement on that for the next release?
      ...
      • 3186 ☆ A M B ☆
      • 279 Posts
      Chunks and RTE?? Chunks are pieces of HTML with some logic and RTE is a content editting thing.. so I think you've mixed up things..

      Why do you want Chunks to be a RTE?
        MODX Ambassador (NL) & Professional MODX developer
        Follow me on Twitter | Visit my page on Facebook | View my code on Github | View my script posts
        MODX e-commerce solution SimpleCart
        • 28042 ☆ A M B ☆
        • 24,524 Posts
        It is a common enough request. Chunks can be blocks of content that are used globally, such as a masthead or a footer, as well as blocks for sidebars. I personally don't like using an RTE for these, since they usually have a lot of HTML structure and I don't like to have that hidden; it's too easy to break a set of divs or other structural elements while editing content when you can't see them. ACE or CodeMirror is good, though.
          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
          • 3186 ☆ A M B ☆
          • 279 Posts
          Yeah that's what I mean Susan!
          Chunks should not be a RTE...

          If you want an extra RTE field you can create a TV for it
            MODX Ambassador (NL) & Professional MODX developer
            Follow me on Twitter | Visit my page on Facebook | View my code on Github | View my script posts
            MODX e-commerce solution SimpleCart
            • 10208 ☆ A M B ☆
            • 1,780 Posts
            Because content editors and users want RTE for editing chunks, which often actually contain content.
              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
              • 10208 ☆ A M B ☆
              • 1,780 Posts
              Quote from: bertoost at Dec 14, 2012, 02:55 PM
              Yeah that's what I mean Susan!
              Chunks should not be a RTE...

              If you want an extra RTE field you can create a TV for it

              Yes, but for those special times, let's say for example; a seasonal chunk that's used once a year with information that will change (an address, date, image, etc.) and need editing by "someone", leaving a TV in the template would be a bit of overkill and waste space. Especially for a chunk that might be used in the content area or within a RTE TV even, just once a year, or infrequently.
                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
                • 3186 ☆ A M B ☆
                • 279 Posts
                Quote from: frogabog at Dec 14, 2012, 03:10 PM
                Quote from: bertoost at Dec 14, 2012, 02:55 PM
                Yeah that's what I mean Susan!
                Chunks should not be a RTE...

                If you want an extra RTE field you can create a TV for it

                Yes, but for those special times, let's say for example; a seasonal chunk that's used once a year with information that will change (an address, date, image, etc.) and need editing by "someone", leaving a TV in the template would be a bit of overkill and waste space. Especially for a chunk that might be used in the content area or within a RTE TV even, just once a year, or infrequently.

                But it is the same processing for MODX to parse a chunk or a TV, so I do not get your point... Chunks are pieces of HTML, when you want to have an RTE you should place a TV somewhere on a page. When you want just 1 field for the client, you can use getResourceField snippet to retrieve that field on any place in your templates based on the ID of the resource where the field is on.

                I never had the idea I want a chunk to be RTE, so don't know why you do ;-)
                  MODX Ambassador (NL) & Professional MODX developer
                  Follow me on Twitter | Visit my page on Facebook | View my code on Github | View my script posts
                  MODX e-commerce solution SimpleCart
                  • 37042
                  • 384 Posts
                  Quote from: bertoost at Dec 14, 2012, 02:46 PM
                  Chunks and RTE?? Chunks are pieces of HTML with some logic and RTE is a content editting thing.. so I think you've mixed up things..

                  Why do you want Chunks to be a RTE?

                  It's not for my own requirements, it's for my clients. We use Chunks for footer elements, repeatable featured items in the side menu and sometimes site-wide in the header.
                  Clients see HTML tags and they loose confidence in their ability to update the site.

                  Also, it's much easier for clients to create and call their own Chunks than create TVs and assign them to templates.
                    ...
                    • 37042
                    • 384 Posts
                    Also, I'm not saying it should be mandatory or even good practice but it should be optional. smiley
                      ...
                      • 10208 ☆ A M B ☆
                      • 1,780 Posts
                      I'm not making a permanent request in the template for a TV that may or may not be used and injected into the content area, perhaps once a year. Even if it's to be used in say, a sidebar RTE TV, the chunk itself does not need a permanent TV. I'm also not making a whole resource to fetch a field from for said chunk.

                      There's no reason to request it all the time in the template if it's only needed for a few weeks a year. Why waste template requests that aren't used much? Better to make that content a chunk, and instruct an editor to plunk it into the content area after updating the chunk's information when they need to use it. They want RTE everywhere.

                      There's so many ways to do the same thing in MODX, we can pick and choose what works best for the end users. Personally, I do not want to be called every time an editor encounters html and hasn't a clue how to edit it. RTE makes them happy, html does not (although it does remind them that websites are not created with magic and spells, always a good thing).
                        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