You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 16, 2021. It is now read-only.
I would like to challange the current "enabling strategy". Currently we enable each admin domain (core, content, ...) by configuration. Doing so its admin services are enabled/visible and its extensions. As the admins are for example purpose only, but the extensions are really helpful for custom admins, i would like to suggest to enable all extensions by default.
The text was updated successfully, but these errors were encountered:
i can get behind that idea. so extensions are always loaded if their respective bundle is available, but the actual admins must be enabled as before so that they don't just show up in the admin interface?
that was your proposal, right? i think its fine. its just extensions that become available. while the actual admins will show up on the default dashboard, which might not be wanted, as you say.
I would like to challange the current "enabling strategy". Currently we enable each admin domain (core, content, ...) by configuration. Doing so its admin services are enabled/visible and its extensions. As the admins are for example purpose only, but the extensions are really helpful for custom admins, i would like to suggest to enable all extensions by default.
The text was updated successfully, but these errors were encountered: