Message of the day:
Release 4.5.0 is out. Changelog: https://docs.silverstripe.org/en/4/changelogs/4.5.0
SilverStripe 4 related information and questions.
it shouldn't do in theory - it's common practice if you want to customise a SiteTree instance you can extend it and tell it to hide the original from the CMS
ok mr averill I'll try it your way
will that screw up anything else though?
if you've extended it with a namespaced class, yeah
@robbieaverill hide the global Page class?
yeah, I can understand the irk-ness of the situation
You can hide the extended page with
private static $hide_ancestor
@flamerohr you know what? screw it. I think I'll leave Page/PageController un-namespaced for the time being 😛 the helper file irks me and then you need to deal with two pages appearing in the CMS