Skip to content
This repository has been archived by the owner on Sep 16, 2021. It is now read-only.

Make Admin extensions available without enabling each admin #134

Open
ElectricMaxxx opened this issue Feb 3, 2018 · 5 comments
Open

Make Admin extensions available without enabling each admin #134

ElectricMaxxx opened this issue Feb 3, 2018 · 5 comments

Comments

@ElectricMaxxx
Copy link
Member

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.

@dbu
Copy link
Member

dbu commented Feb 5, 2018

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?

@ElectricMaxxx
Copy link
Member Author

So the extensions are available even when their bundles arn't "activated" in our configuration here?

@dbu
Copy link
Member

dbu commented Feb 5, 2018

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.

@ElectricMaxxx
Copy link
Member Author

I want to also use this bundle to use the admin extensions without the admin we propose as an example here.

So i want to use the core extension (publish workflow) without doing a

sonata_admin:
    bundles:
         core: ~

(btw: core does not have own admins, extensions only). I want them available when core-bundle and sonata-admin-integration is available.

@dbu
Copy link
Member

dbu commented Feb 5, 2018

cool, then i think we agree. this totally makes sense to me.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants