Propagate down published setting

[laszlokorte]

Currently if a parent page has published set to false but a child has published set to true (or not set at all).

It would be nice if the published: false state of a parent would also set all it's (grand) children to not being published in.

My use case is the following:
I have multiple "gallery" pages with "images" as children. While setting up a new gallery to be published in a few weeks I set it to be not published yet but I already add all of the images I already prepared. Having many images it's tiresome to set each image to published: false.
But without doing so those images are reachable via URL and show up in the sitemap even though the gallery itself is not published yet.

It would be fine to have a propagatePublished setting on the parent page page. Or maybe that if a page has not published value set at all it inherits the value from the parent (transitively) but if it has a value set the parent's setting is ignored.

[laszlokorte]

I think the same would make sense for the "routable" option. If a parent page is not routable how could a child be routable?

[rhukster]

It's actually quite possible that a parent be not-routable but a chid is.

For example

/foo/bar is not routable, ie 404 page
/foo/bar/child is routable and returns a valid page

but an option to trickle down routable could be useful too.. its sort of similar to publish in that regard.

[laszlokorte]

Oh, you are right :)