> DUH! > > I'm not sure I agree. > Marking an existing page as 404 'cos its been taken out of service, > perhaps for legal reasons, seems reasonable, and its also reasonable > that its children need not be taken out of service. > > This is no different, logically, from a parent page that is taken out of > service with a redirect to a replacement, and whose children are not > affected. The only difference is whether or not there *is* a replacement. > > So I see this as a parsing problem. > The parser hits a 404 page and stops. > > This is a confusion between a 404 page and a "missing" page. The 404/"File Not Found" page type is what will be displayed when any requested URL does not correspond to a published page. If you don't want a page to be navigable, use the "Hidden" or "Draft" status instead.
Sean _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
