Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow to hide / deregister plugins from configuration #5000

Closed
yakky opened this issue Feb 12, 2016 · 4 comments
Closed

Allow to hide / deregister plugins from configuration #5000

yakky opened this issue Feb 12, 2016 · 4 comments

Comments

@yakky
Copy link
Member

yakky commented Feb 12, 2016

Sometimes, even if a plugin is available in the codebase, you don't want it to be available in any place.
Currently CMS_PLACEHOLDER_CONF only allow to whitelist plugins in specific placeholders.
Blacklisting plugins should be available too (either globally or per-placeholder)

See also http://stackoverflow.com/questions/35044928/django-cms-placeholder-plugin-avaliable-only-to-a-specific-placeholder

@yakky yakky added this to the 3.3 milestone Feb 12, 2016
@yakky
Copy link
Member Author

yakky commented Feb 12, 2016

Linked to #4979

@yakky
Copy link
Member Author

yakky commented Jun 18, 2016

Fixed by #5412
To implement blacklist, add the plugin to be blacklisted in CMS_PLACEHOLDER_CONF[None]['excluded_plugins'] list

@marcosguedes
Copy link

Started from #5000, now we here :) Updated stackoverflow answer above

@yakky
Copy link
Member Author

yakky commented Jun 20, 2016

@marcosguedes awesome!

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

No branches or pull requests

3 participants