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 **kwargs): return [MyAppMenu, CategoryMenu] Apphook permissions By default the content represented by an apphook has the same permissions set as the page it is assigned to. So if for example a page To disable this behaviour set permissions = False on your apphook: class SampleApp(CMSApp): name = _("Sample App") _urls = ["project.sampleapp.urls"] permissions = False If you still want some

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 **kwargs): return [MyAppMenu, CategoryMenu] Apphook permissions By default the content represented by an apphook has the same permissions set as the page it is assigned to. So if for example a page To disable this behaviour set permissions = False on your apphook: class SampleApp(CMSApp): name = _("Sample App") _urls = ["project.sampleapp.urls"] permissions = False If you still want some

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 [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 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

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 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

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