Prevent data definition page chooser-generated links to pages set to not publish from being rendered

eporter's Avatar

eporter

10 Oct, 2011 06:48 PM

I'm trying to find a way to prevent links to pages which are set to not publish, which may have been inadvertently selected via a data definition page chooser, from being rendered. According to the Knowledge Base, <is-published> is present when an asset has "Include when Publishing" checked, which would be exactly what I need for my XSLT to select against, but I can't seem to get that particular metadata element from a page chooser context. Is this element available to a page chooser's XML or does it only appear for index blocks?

  1. Support Staff 2 Posted by Charlie Holder on 27 Mar, 2012 04:45 AM

    Charlie Holder's Avatar

    Hey eporter -- I saw this post while looking through some of the open threads. Are you still needing help? If so..

    The <is-published> node should be available for pages selected through a Page Chooser if the parent page has the System Metadata being rendered. Are you finding that this is not the case?

  2. Support Staff 3 Posted by Charlie Holder on 11 Apr, 2012 08:21 PM

    Charlie Holder's Avatar

    Hi eporter --

    Let us know if you're still needing help with this. You can reopen this thread. Hopefully my comments about the specific Metadata options are helpful.

    THanks!

  3. Charlie Holder closed this discussion on 11 Apr, 2012 08:21 PM.

  4. eporter re-opened this discussion on 24 May, 2012 09:01 PM

  5. 4 Posted by eporter on 24 May, 2012 09:04 PM

    eporter's Avatar

    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?

  6. 5 Posted by eporter on 25 May, 2012 01:16 PM

    eporter's Avatar

    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?

  7. Support Staff 6 Posted by Charlie Holder on 25 May, 2012 06:30 PM

    Charlie Holder's Avatar

    Hey eporter -- I am seeing the same behavior. I will update you with some more information after I look at this a little more.

  8. 7 Posted by eporter on 20 Aug, 2012 08:13 PM

    eporter's Avatar

    Have there been any updates on this? In general, it seems that the XML nodes returned from a data definition page asset chooser are different from those returned by an index block of pages.

  9. Support Staff 8 Posted by Tim on 23 Aug, 2012 08:36 PM

    Tim's Avatar

    Hi,

    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 looking for).

    I know this may sound complicated so let me know if you have any further questions.

    Thanks

  10. 9 Posted by eporter on 24 Aug, 2012 08:46 PM

    eporter's Avatar

    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.

  11. Support Staff 10 Posted by Tim on 24 Aug, 2012 08:49 PM

    Tim's Avatar

    Yes, please feel free to add that idea to the Idea Exchange. Have a great weekend!

  12. Tim closed this discussion on 24 Aug, 2012 08:49 PM.

Comments are currently closed for this discussion. You can start a new one.