Feature/cms 660 show read-only settings when allowAdminChanges is disabled

[i-just]

Description

Shows read-only settings when allowAdminChanges is disabled.

• switched .revision-notice to a generic .content-notice class so that the styles can be reused for other purposes too
• when admin changes are disallowed, the “Settings” main nav item and all the subpages (except for the plugin settings) are shown, with all the fields and forms being disabled and with a notice at the top of every page
• plugins can opt into having their settings shown when allowAdminChanges is disabled; to do so, they need to ensure none of the settings are editable in such case and set public bool $hasReadOnlyCpSettings to true

Further info are in Brandon's comment below.

Related issues

cms-660

[linear]

CMS-660 Show read-only settings when allowAdminChanges == false

[Mosnar]

Love this! It might be worth adding a "Learn More" button to a KB article explaining why settings can't/shouldn't be changed in production. Newer Craft developers or over-confident clients might read the current disclaimer as instructions to simply turn on "allowAdminChanges" and potentially get themselves in a mess.

[gcamacho079]

@i-just awesome! I pinged you on the Notion page for this feature as I had some follow-up questions.

[brandonkelly]

@i-just What’s the reason for this?

[i-just]

It was adding a disabled attribute to the fields inside the field layout designer’s .fld-field-library. But with the changes from #16374, it’s no longer needed (plus, it looks like I forgot to make it dynamic). I took that out.

[brandonkelly]

I changed things up a bit so now all configurable components have a getReadOnlySettingsHtml() method, which by default will return the same thing as getSettingsHtml() except with all inputs disabled (similar to Field::getStaticHtml()).

Fields, filesystems, and mail transport adapters now override getReadOnlySettingsHtml() whenever possible, with the exception of BaseOptionsField and BaseRelationField (since in those cases, there’s no way to explicitly override getReadOnlySettingsHtml() without leaving 3rd party subclasses in the dust, so it’s better to wait until v6 before updating those).

Plugins similarly now have a getReadOnlySettingsResponse() method, and a $hasReadOnlyCpSettings property. craft\base\Plugin::getReadOnlySettingsResponse() will return $this->getSettingsResponse() with inputs in the settings HTML disabled (like ConfigurableComponent::getReadOnlySettingsHtml() and Field::getStaticHtml()), and its init() method will automatically set $this->hasReadOnlyCpSettings = true if getSettingsResponse() hasn’t been overridden.

The point of these changes is to limit the need to check allowAdminChanges, in case there’s a reason to render any of these settings without taking allowAdminChanges into effect. For example, a form plugin might have a need to render a Plain Text field’s settings even when allowAdminChanges is disabled (because maybe the field isn’t getting saved to the project config), and should still be able to call $field->getSettingsHtml() and get the normal non-disabled response.