-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Please explain settings in CMS_PLACEHOLDER_CONF #830
Comments
In section 19.2.2. Django-CMS and Cascade settings, explanation of default settings: The The default placeholders and their settings are provided in the Django CMS Installer-generated projects. The default CMS_PLACEHOLDER_CONF = {
'Breadcrumb': {
'plugins': ['BreadcrumbPlugin'],
'parent_classes': {'BreadcrumbPlugin': None},
},
'Commodity Details': {
'plugins': ['BootstrapContainerPlugin', 'BootstrapJumbotronPlugin'],
'parent_classes': {
'BootstrapContainerPlugin': None,
'BootstrapJumbotronPlugin': None,
},
},
'Main Content': {
'plugins': ['BootstrapContainerPlugin', 'BootstrapJumbotronPlugin'],
'parent_classes': {
'BootstrapContainerPlugin': None,
'BootstrapJumbotronPlugin': None,
'TextLinkPlugin': ['TextPlugin', 'AcceptConditionPlugin'],
},
},
'Static Footer': {
'plugins': ['BootstrapContainerPlugin', 'BootstrapJumbotronPlugin'],
'parent_classes': {
'BootstrapContainerPlugin': None,
'BootstrapJumbotronPlugin': None,
},
},
} These settings define available plugins for each placeholder, the parent classes of those plugins, and optionally a glossary configuration. However, depending on the project's needs and structure, some variations may occur. The documentation might show an example with an additional In summary, the Please note: Be sure to replace |
I was wondering why I didn't see most of the placeholders I'm used to seeing in the menu in Django CMS when I clicked
+
forMain Content
. After some digging, I founf it's restricted by CMS_PLACEHOLDER_CONF (which defaults to{}
for Django CMS Installer-generated projects). My Shop project is from the shop cookie cutter.If it's not too much trouble, could someone add a short explanation in 19.2.2. Django-CMS and Cascade settings as to why the default is:
and why the docs show something else:
The text was updated successfully, but these errors were encountered: