related_name for a PlaceholderField may not be suppressed using '+'; this allows the cms to check permissions properly. Attempting to do so will raise a ValueError [https://docs.python.org/3/library/exceptions company_name). Permissions To be able to edit a placeholder user must be a staff member and needs either edit permissions on the model that contains the PlaceholderField, or permissions for that specific specific instance of that model. Required permissions for edit actions are: to add: require add or change permission on related Model or instance. to change: require add or change permission on related Model

related_name for a PlaceholderField may not be suppressed using '+'; this allows the cms to check permissions properly. Attempting to do so will raise a ValueError [https://docs.python.org/3/library/exceptions company_name). Permissions To be able to edit a placeholder user must be a staff member and needs either edit permissions on the model that contains the PlaceholderField, or permissions for that specific specific instance of that model. Required permissions for edit actions are: to add: require add or change permission on related Model or instance. to change: require add or change permission on related Model

related_name for a PlaceholderField may not be suppressed using '+'; this allows the cms to check permissions properly. Attempting to do so will raise a ValueError. Note: If you add a PlaceholderField to an Release 3.9.0 Permissions To be able to edit a placeholder user must be a staff member and needs either edit permissions on the model that contains the PlaceholderField, or permissions for that specific specific instance of that model. Required permissions for edit actions are: • to add: require add or change permission on related Model or instance. • to change: require add or change permission on related

related_name for a PlaceholderField may not be suppressed using '+'; this allows the cms to check permissions properly. Attempting to do so will raise a ValueError. Note: If you add a PlaceholderField to an company_name). Permissions To be able to edit a placeholder user must be a staff member and needs either edit permissions on the model that contains the PlaceholderField, or permissions for that specific specific instance of that model. Required permissions for edit actions are: • to add: require add or change permission on related Model or instance. • to change: require add or change permission on related

Application hooks (“apphooks”) Publishing Serving content in multiple languages Internationalisation Permissions Search and django CMS Using touch-screen devices with django CMS Color schemes (light/dark) with menus. The application’s pages won’t be able to take advantage of the CMS’s publishing workflow, permissions or other functionality. Apphooks offer a more complete way of integrating other applications, by ow-django- discovers-language-preference Permissions The django CMS permissions system is flexible, granular and multi-layered. Permission modes Permissions operate in two different modes, depending on

Application hooks (“apphooks”) Publishing Serving content in multiple languages Internationalisation Permissions Using touch-screen devices with django CMS Color schemes (light/dark) with django CMS How the menu menus. The application’s pages won’t be able to take advantage of the CMS’s publishing workflow, permissions or other functionality. Apphooks offer a more complete way of integrating other applications, by ow-django- discovers-language-preference Permissions The django CMS permissions system is flexible, granular and multi-layered. Permission modes Permissions operate in two different modes, depending on

arguments: request A Django request instance. You want to modify based on sessions, or user or permissions? nodes All the nodes. Normally you want to return them again. namespace A Menu Namespace. Only reverse('myapp_namespace:app_main', current_app=current_app) # ... Apphook permissions By default all apphooks have the same permissions set as the page they are assigned to. So if you set login required on requirements. To disable this behavior set permissions = False on your apphook: class SampleApp(CMSApp): name = _("Sample App") urls = ["project.sampleapp.urls"] permissions = False If you still want some of your

fix resolve this, as the whole context is now saved in cache along with the rendered templates. Permissions cache performance issue fix backported When a page is saved and cache is enabled, an explicit cache do so will lead to a ValueError. This change was done to allow the django CMS to properly check permissions on Placeholder Fields. 1.4. 2.3.4 release notes 5 django cms Documentation, Release 2.3.8 Two 3 support The django CMS 2.2 supports both Django 1.2.5 and Django 1.3. View permissions You can now give view permissions for django CMS pages to groups and users. 1.8.2 Backwards incompatible changes

fix resolve this, as the whole context is now saved in cache along with the rendered templates. Permissions cache performance issue fix backported When a page is saved and cache is enabled, an explicit cache do so will lead to a ValueError. This change was done to allow the django CMS to properly check permissions on Placeholder Fields. Two fixes to page change form The change form for pages would throw errors 3 support The django CMS 2.2 supports both Django 1.2.5 and Django 1.3. View permissions You can now give view permissions for django CMS pages to groups and users. 1.10. 2.2 release notes 15 django cms

management commands 4.3. Moderation commands 4.4. MPTT repair command 5. Permissions 5.1. View restrictions 5.2. Page permissions Extending the CMS 1. Extending the CMS: Examples 1.1. My First Plugin 1 fix resolve this, as the whole context is now saved in cache along with the rendered templates. Permissions cache performance issue fix backported When a page is saved and cache is enabled, an explicit cache do so will lead to a ValueError. This change was done to allow the django CMS to properly check permissions on Placeholder Fields. Two fixes to page change form The change form for pages would throw errors