We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 19369
    • 1,098 Posts
    As einsteinsboi said, you can use Resources or Template Variables. However, when you create a Resource you are basically creating a page so it will appear for example in the sitemap and it will have a URL, whereas a Template Variable won’t create any additional page.

    Of course you can hide these resources from the sitemap if needed. The question here is whether or not use Resources for three short boxes.

    By the way, another cool feature of MODx you might be interested in is ManagerManager. ManagerManger allow you to personalize the Manager, so you can create or rename tabs, reorder Template Variables and much more.
    The documentation can be found in every MODx folder on assets/plugins/managermanager/docs/index.htm
      • 24074
      • 81 Posts
      @einsteinsboi
      I meant that pulling boxes content from separate resources was generally good idea for clients’ convenience and ease of access.

      Using Ditto for that seemed like a reasonable solution but as microcipcip said, making it that way, it would add those pages to Sitemap and create URL’s to them so its not best solution for this case in terms of SEO i believe.

      Is there a solution which could allow client to edit content of those boxes easily, without even knowing what TV’s are, but not to create separate pages for them?

      How would you do it @einsteinsboi and @microcipcip?

      Thanks!
        Radio sucks!
        • 8609
        • 607 Posts
        Yes, you as the site builder would create the TVs, one for each box, set them to have a Rich Text input type, and then position them where you want on the template for that specific page, just as microcipcip demonstrated above.

        The client doesn’t need to know what a TV is, or even that you’re using TVs. When they go in to edit the page, they’re presented with the main content areas as well as these three boxes as editable areas and they can edit away to their hearts content. TVs allow you to have multiple editable areas on one page, which is exactly what you’re after smiley .
          • 24074
          • 81 Posts
          Hi @einsteinsboi,

          Umm.. i think I’m doing something wrong or i didn’t quite understood you..

          So you’re telling that when I port my HTML to Revo template, make boxes TV’s and place those TV’s in appropriate place in template, content of boxes should appear in RichText editor (TinyMCE) automatically?

          What i thought is when that has been done, only way to alter content of those boxes is to edit the TV’s directly from Elements menu.

          I’m so close to figure this out, please don’t leave me now smiley

          Thanks for helping!
            Radio sucks!
            • 19369
            • 1,098 Posts
            I have thought that you were using MODx Evolution. The syntax for MODx Revolution is different.
            [[*box-01]] instead of [*box-01*]

            So you’re telling that when I port my HTML to Revo template, make boxes TV’s and place those TV’s in appropriate place in template, content of boxes should appear in RichText editor (TinyMCE) automatically?
            Yes, but with Revolution you have to install the RichText Editor first because it is not included in the default installation.

            What i thought is when that has been done, only way to alter content of those boxes is to edit the TV’s directly from Elements menu.
            No, the only thing that the client needs to do is open the Home page and under the "Template Variables" tab he’ll see all custom fields.
              • 24074
              • 81 Posts
              Yep, it worked..
              Now I see that some local characters are missing even though charset is set to UTF-8.
              http://a.imageshack.us/img651/5058/screenier.png

              Plenty of ? signs.

              Should new topic be opened for this new issue?

              Thanks
                Radio sucks!
                • 27708 MODX Staff
                • 2,502 Posts
                What is the database charset set to? It needs to be match your document charset otherwise there will be issues with higher level chars or mismatches.
                  Author of zero books. Formerly of many strange things. Pairs well with meats. Conversations are magical experiences. He's dangerous around code but a markup magician. Blog ✦ Twitter ✦ LinkedIn ✦ GitHub
                  • 24074
                  • 81 Posts
                  DB collation is set to latin1_general_ci, that is probably the issue, right?
                    Radio sucks!
                    • 27708 MODX Staff
                    • 2,502 Posts
                    I am not 100% certain but I would think that your characters need to be consistent. I would expect the collation would need to be also UTF_General_ci
                      Author of zero books. Formerly of many strange things. Pairs well with meats. Conversations are magical experiences. He's dangerous around code but a markup magician. Blog ✦ Twitter ✦ LinkedIn ✦ GitHub
                      • 24074
                      • 81 Posts
                      set to unicode wherever possible, problem solved, thanks!
                        Radio sucks!