#40 Disable CMS-based creation of menusets by default

[jakxnz]

#40

[stecman]

Would it make sense to do this with permissions instead of a custom config option?

[jakxnz]

I did consider using provisioned permissions @stecman, but the only use case(s) I can think of is if your front-end
a) supports menu sets created by CMS authors, or
b) expects predefined (default) menu sets only.

So I figured a Config based switch was more in line with those cases.

(I'm assuming you meant permissions as in permission provider and custom config as in the Config API (not permissions as in canCreate() logic and custom config as in GridFieldConfig))

[jakxnz]

I did consider using provisioned permissions @stecman, but the only use case(s) I can think of is if your front-end
a) supports menu sets created by CMS authors, or
b) expects predefined (default) menu sets only.

So I figured a Config based switch was more in line with those cases.

(I'm assuming you meant permissions as in permission provider and custom config as in the Config API (not permissions as in canCreate() logic and custom config as in GridFieldConfig))

@stecman, Any word on this?