Global template variables

Hi all, is there a way i can create some tvs in one resource that are then used on all resources, for example footer links and logos. It seems silly to expect a client to have to update them on every page.

sorry if its been posted before which i'm sure it will have, but unable to find any info on this issue.

many thanks
James

- You can create global system settings for this!
https://rtfm.modx.com/revolution/2.x/administering-your-site/settings/system-settings/
https://www.youtube.com/watch?v=HDlL-YGpALQ

- Or you can create MODX placeholders (in a plugin or snippet) that can easily be used in the content [[+myPlaceholder]]

- Or you can use something like pdoField to grab a value stored in a resource
http://docs.modx.pro/en/components/pdotools/snippets/pdofield

BUT

What you want to learn about is MODX Chunks!! Which are global html "chunks" perfect for header, footer etc.

@mrhaw: What if you don't want to give your clients a possibility to edit chunks.

@biffyn: I use ClientConfig for this. It creates a sort of global system settings in a separate CMP. Ideally for frequent changes of i.e. opening times in the footer, mail address for the contact form etc.

For footer links the 'selections' part from Collections is quite usable.

thanks Jako will check it out

We set up an Admin document using an Admin template for global Template Variables.
Then we setup a context setting we call (you can call it whatever you want): admin_page_id
We input the page ID into the Context Setting and then save it.

This allows the client to go into the Admin page and change any TVs you've made accessible to them. We usually heavily modify this page using Manager Customization (formerly Forms Customzation and still called that in the docs) so they only see the Template Variables tab (which we also rename using Manager Customization).

Then in chunks that reference those values (such as a [[$footer]] we use fastField (fastField Docs)to grab the value, i.e.



Where the TV is facebookAddress and the value would be their Facebook URL. So we'd have something like this within the footer chunk:



Other options are of course those mentioned above but keep in mind that ClientConfig is not context sensitive (the last I checked) so if you use multiple contexts (we do all the time but we realize not everyone does) then it's not as useful.

You could also use context settings themselves but it's usually not a good idea to give clients access to such sensitive settings.

Another method you can use is to install PDOTools and reference the admin page for a context:



So for a Facebook link you might do this:



The reason I mention PDOTools is it supposed to be great for performance (i.e. speed).

You can also just use chunks and use the permission system to hide them from low-level Manager users.