Charlie, thanks for the response. Can you clarify how the parent
page affects the data definition page chooser results?In this case,
there is no index block involved, but a page with a data definition
applied at DEFAULT, which contains a page chooser. Page -chooser
selected XML returned does not return any System Metadata. Are you
suggesting that I apply a current page index block and enable
System Metadata on that?
From my own testing, it seems that page chooser output doesn't
contain the corresponding elements you would see in an index block
with System Metadata enabled, such as is-published or
last-published-on. My main concern is how to find a
way using Cascade's available XML generated by a page chooser, to
prevent potential broken links created to pages based on their
publishing status. Any suggestions?
Support Staff8 Posted by Tim on 23 Aug, 2012 08:36 PM
Apologies for the delayed response on this discussion.
Unfortunately it is not possible to get this particular data (or
other Index Block options) returned via a Page chooser.
One possible workaround would be to have all of your Pages in
question contain a hidden Block chooser (you can restrict it to
admins only, for example). Using this Block chooser (with a
render-content-depth set to higher than 1), you could select an
Index Block that was configured to return information for the
current Page. This way, once attached to every Page, you would be
able to see the contents of this Index Block in the context of the
current Page (which would include the system metadata that you are
I know this may sound complicated so let me know if you have any
Thanks, Tim - that's an interesting idea! I may also put in a
request on the Idea Exchange to synchronize the XML returned
between a page chooser and index block, since there are some other
disparities like how a Start Date is rendered between the two.