mixin) and thus it is available in the view to provide the configuration for the current namespace. Namespaces can be created on the fly in the Page admin Advanced settings. When creating an application configuration are in fact defining a namespace, which is saved in the same field in the Page model as the plain namespaces. step-by-step implementation We’re going to create a new application called FAQ. It is a simple config.paginate_by except AttributeError: return 10 AppConfigMixin provides a complete support to namespaces, so the view is not required to set anything specific to support them; the following attributes

include('django.contrib.staticfiles.urls')), ) + urlpatterns Change your url and reverse calls to language namespaces. We now support the django way of calling other language urls either via {% language %} templatetag TEMPLATE_CONTEXT_PROCESSORS setting. All templates in CMS_TEMPLATES must at least contain the js and css sekizai namespaces. Please refer to the documentation on Handling media in custom CMS plugins and the django-sekizai django-sekizai [https://github.com/ojii/django-sekizai]. This requires you to define at least two sekizai namespaces in your templates: js and css. You can do so using the render_block template tag from the sekizai_tags

django-sekizai [https://github.com/ojii/django-sekizai]. This requires you to define at least two sekizai namespaces in your templates: js and css. You can do so using the render_block template tag from the sekizai_tags com/ojii/django- sekizai]. Your CMS templates are always enforced to have the css and js sekizai namespaces, therefore those should be used to include the respective files. For more information about django-sekizai namespaced URLs [https://docs.djangoproject.com/en/dev/topics/http/urls/#topics-http-defining-url-namespaces]? This is good practice, so it should! In that case you will need to ensure that your apphooks

include('django.contrib.staticfiles.urls')), ) + urlpatterns • Change your url and reverse calls to language namespaces. We now support the django way of calling other language urls either via {% language %} templatetag TEMPLATE_CONTEXT_PROCESSORS setting. All templates in CMS_TEMPLATES must at least contain the js and css sekizai namespaces. Please refer to the documentation on Handling media in custom CMS plugins and the django-sekizai required by CMS plugins using django- sekizai. This requires you to define at least two sekizai namespaces in your templates: js and css. You can do so using the render_block template tag from the sekizai_tags

required by CMS plugins using django-sekizai. This requires you to define at least two sekizai namespaces in your templates: js and css. You can do so using the render_block template tag from the sekizai_tags your namespace will change. The solution for this problem are application namespaces. If you’d like to use application namespaces to reverse the URLs related to your app, you can assign a value to the app_name application and instance namespaces, the current_app scope and the reversing of such URLs. You can look it up at https://docs.djangoproject.com/en/dev/topics/http/urls/#url-namespaces When using the reverse

com/ojii/django- sekizai]. Your CMS templates are always enforced to have the css and js sekizai namespaces, therefore those should be used to include the respective files. For more information about django-sekizai namespaced URLs [https://docs.djangoproject.com/en/1.10/topics/http/urls/#topics-http-defining-url-namespaces]? This is good practice, so it should! In that case you will need to ensure that your apphooks app_name if a match is found. This arrangement allows you to use multiple application instances and namespaces if that flexibility is required, while guaranteeing a simple way to make it work when it’s not

com/ojii/django- sekizai]. Your CMS templates are always enforced to have the css and js sekizai namespaces, therefore those should be used to include the respective files. For more information about django-sekizai namespaced URLs [https://docs.djangoproject.com/en/1.10/topics/http/urls/#topics-http-defining-url-namespaces]? This is good practice, so it should! In that case you will need to ensure that your apphooks app_name if a match is found. This arrangement allows you to use multiple application instances and namespaces if that flexibility is required, while guaranteeing a simple way to make it work when it’s not

com/ojii/django- sekizai]. Your CMS templates are always enforced to have the css and js sekizai namespaces, therefore those should be used to include the respective files. For more information about django-sekizai namespaced URLs [https://docs.djangoproject.com/en/2.2/topics/http/urls/#topics-http-defining-url-namespaces]. In the example above, the application uses the myapp namespace. Your CMSApp sub- class must app_name if a match is found. This arrangement allows you to use multiple application instances and namespaces if that flexibility is required, while guaranteeing a simple way to make it work when it’s not

com/ojii/django- sekizai]. Your CMS templates are always enforced to have the css and js sekizai namespaces, therefore those should be used to include the respective files. For more information about django-sekizai namespaced URLs [https://docs.djangoproject.com/en/2.2/topics/http/urls/#topics-http-defining-url-namespaces]. In the example above, the application uses the myapp namespace. Your CMSApp sub- class must reflect app_name if a match is found. This arrangement allows you to use multiple application instances and namespaces if that flexibility is required, while guaranteeing a simple way to make it work when it’s not

com/ojii/django- sekizai]. Your CMS templates are always enforced to have the css and js sekizai namespaces, therefore those should be used to include the respective files. For more information about django-sekizai namespaced URLs [https://docs.djangoproject.com/en/2.2/topics/http/urls/#topics-http-defining-url-namespaces]. In the example above, the application uses the myapp namespace. Your CMSApp sub- class must reflect app_name if a match is found. This arrangement allows you to use multiple application instances and namespaces if that flexibility is required, while guaranteeing a simple way to make it work when it’s not