We have a Component - attached to a Dynamic Component and want to publish it for content changes.
We have this same Component in a container which we use to control the order of the Components in this particular view (it can't be meta on the Component as it's used in different containers / in different orders).
The Container is a Component Presentation on more than one page.
So, the intention is
- publish page(2) = changed order
- publish DCP = changed content
This model allows the editorial team to continue updating content when a page is locked (say because a disclosure is being check and the intro isn't signed off).
Now technically this is working correctly in that when we publish with the DCP all the pages are published alongside the DCP itself.
- a custom resolver could catch the DCP and stop the page publish
- or we could remove the Container CP from the pages and have the page grab and render the necessary (java tag with a 'order array') rather it than being manually linked
The custom resolver would require code releases (multiple) with changes as we add more items to this pattern (although we may be able to abstract out a generic solution)
The removal of a CP will upset editors as they, rightly, Where Used.
Am I making it up or did there used to be a setting that would allow the depth of a component publish to a page to be limited ... e.g. if you don't find me directly on a CP then don't look any further?
If I am making it up ... any thoughts on other strategies for this challenge?