Message of the day:
Welcome to SilverStripe | Current stable: https://goo.gl/C4F1T9 | Feature requests: https://goo.gl/EcQ34L | Community Forum: https://forum.silverstripe.org | StripeCon EU 2019! https://stripecon.eu
If you have any SilverStripe related questions, please supply the version of Framework you're using.
Did you flush? 🚽 =
we're just theorising at this point
But, I didn't write this, I have no context on why it's there. you're right - it needs more substantial documentation :)
Which indicates it shouldn't be static - so your issue is still valid. It highlights this :)
and ideally re-set afterwards.
If you want to disable it for a page type, you need to use the setters.
No, having it set on config allows you to disable it for every page in existence for a project
That is the very reason snake case is used - to differentiate config keys from class variables.
fair enough 😉, but having it set to a proper config allows you to disable it on a Vendor owned Page
the concept of config isn't PSR at all.