We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 4078
    • 31 Posts
    Hi guys/girls

    I am having some difficulties here, and my problem is I have a sidebar on all the pages with some news inside it. So I made a TV for the client so he can update and put som more news inside it. But the problem is that, if he changes og inserts some news in the TV on, let’s say "home", it doesnt change on "about" aswell. He have to manually type or copy/paste all the news to every site on that single TV.

    How can I make a TV that the client can update from one place and it changes on all pages?

    By the way he is using MODX 1.0.4

    Best regards, Brian
      • 26931
      • 2,314 Posts
      anonymized-26931 Reply #2, 16 years ago
      use a Chunk instead, or create an "config"-resource with that TV in it and use the GefField Snippet to pull that value into the Template

      related: http://www.gregorysmart.com/2010/01/08/create-a-user-config-page-in-modx/
        • 4078
        • 31 Posts
        I dont think you understand then..

        My problem is I want to update one single area on my page, and the it should change the same place on every page. But if you did understand, I dont want to mess with some configs.

        But still, Im wondering how to achieve this with a chunk?
          • 28042 ☆ A M B ☆
          • 24,524 Posts
          You might want to use a resource for this; the client will probably be happier editing a resource’s content. Then in your template use a TV; the TV would be of text type with a default of @DOCUMENT id, where the id is the actual ID of the resource you’re using. You can even hide the TV using ManagerManger (or assigning it to a resource group that only admin manager users belong to) so it won’t accidentally get edited.

          I would put the resource in an unpublished container resource called "tools", and add a link to it in the QuickManager configuration so the user can get to it quickly from the front-end. If you have a bunch of custom stuff like this for the client to work with, create a front-end "admin" resource with links to the resources he’ll be commonly editing, and put a link to that "admin" resource in the QM configuration. It can be all prettied up into fancy buttons with CSS, if you like.
            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
            • 4078
            • 31 Posts
            Quote from: sottwell at Oct 12, 2010, 09:40 AM

            You might want to use a resource for this; the client will probably be happier editing a resource’s content. Then in your template use a TV; the TV would be of text type with a default of @DOCUMENT id, where the id is the actual ID of the resource you’re using

            Sorry... But I really dont get that up there.. Is there way for you to explain a bit better? Or reference me to a site that shows how to do what I want?
              • 4078
              • 31 Posts
              Thanks, you gave me a good hint.. I think I got it know..