I cannot believe that I have gotten this far and just encountered this, but I have started to use the @INHERIT Binding for default TV images throughout the site and then replacing those that will have different headers. Which is a really nice feature! Since my "resource parent" was "0" on a number of "top level" documents a default Image TV for the site cannot be set on document "0". And yet @INHERIT just by itself is looking to document "0" ultimately. On the other hand much coding, i.e. Wayfinder, is written with a "&startId=`0`"
Is there a way with the @INHERIT binding to point to say Document (Resource) "1" which is my home page and be the Ultimate parent for purposes of this TV?
Thank you.
"Remember what Bilbo used to say: It's a dangerous business, Frodo, going out your door. You step onto the road, and if you don't keep your feet, there's no knowing where you might be swept off to."
-J.R.R. Tolkien from The Lord of the Rings
"Remember what Bilbo used to say: It's a dangerous business, Frodo, going out your door. You step onto the road, and if you don't keep your feet, there's no knowing where you might be swept off to."
-J.R.R. Tolkien from The Lord of the Rings
How about using this?
@INHERIT http://path_to_image
-
☆ A M B ☆
- 24,524 Posts
@INHERIT can only work for documents that are children. Document #0 doesn’t really exist; it’s just a virtual designation to indicate that those with a parent of 0 are in the top level and they really don’t have a parent.
As BobRay said, give it a default value as well as the @INHERIT and your top-level documents will have it.
Thank you Bob & Susan,
I worked this last night, and Bob’s suggestions works to a degree.
If my site is
Container 1 (Home Page)
Container 2
Container 3
Child 1
Child 2
Child 3
If in the TV HeaderPicture I put as Default @INHERIT
http://site/assets/images/image1.jpg
The whole site takes "image1.jpg"
If I change Container 3 TV variable to "image2.jpg, child 1, child 2 and child 3 still take "image1.jpg" with the above default in the TV
So it is a trade off setting the image, in this case HeaderPicture, for each container and using @INHERIT or Setting a site image and then when changing a container having to change each child as well. Since I have many more "children" than "parents" it is better to set on the Container even though some children will take the sites main header picture. That is why it would be nice in the future to be able to set things on Container 0 for the site. That flexibility opens up a whole range of possibilities.
In my case, on a textile site, different header pictures apply to the type of container. Such that fashion has models and technical textiles have pictures with Fireman in their gear. Of course, unless the latest fashion in fire gear is your thing.
"Remember what Bilbo used to say: It's a dangerous business, Frodo, going out your door. You step onto the road, and if you don't keep your feet, there's no knowing where you might be swept off to."
-J.R.R. Tolkien from The Lord of the Rings
What you tried should work, but you should clear the MODx cache and your browser’s cache before checking. It also won’t work if you’ve given explicit values to the TV in the sub docs and saved them, because then their TV is no longer set to @INHERIT.
The default setting is mainly for new documents as you create them. It will definitely work for them.
