When using SaveAction.SkipValidation when saving/editing pagesprogrammatically, you're basically saying "Out of the way rules, let me handle this!". It would be practical if this, in addition to skipping validation on properties, could skip validating what page types are allowed where too.
This would, for example, allow me to auto generate a content structure by nesting ListPages below each other (lets say in a month/year structure, department structure, category structure, whatever), while only allowing editors to create ArticlePages below each auto generated node.
Could possibly be done with a separate flag, like SaveAction.IgnoreAllowedPageTypes.
When using SaveAction.SkipValidation when saving/editing pages programmatically, you're basically saying "Out of the way rules, let me handle this!". It would be practical if this, in addition to skipping validation on properties, could skip validating what page types are allowed where too.
This would, for example, allow me to auto generate a content structure by nesting ListPages below each other (lets say in a month/year structure, department structure, category structure, whatever), while only allowing editors to create ArticlePages below each auto generated node.
Could possibly be done with a separate flag, like SaveAction.IgnoreAllowedPageTypes.