A quick overview of the available settings:
FLUENT_PAGES_BASE_TEMPLATE = "fluent_pages/base.html" FLUENT_PAGES_TEMPLATE_DIR = TEMPLATE_DIRS FLUENT_PAGES_RELATIVE_TEMPLATE_DIR = True FLUENT_PAGES_DEFAULT_IN_NAVIGATION = True FLUENT_PAGES_KEY_CHOICES = () # Advanced FLUENT_PAGES_PREFETCH_TRANSLATIONS = False FLUENT_PAGES_FILTER_SITE_ID = True FLUENT_PAGES_PARENT_ADMIN_MIXIN = None FLUENT_PAGES_CHILD_ADMIN_MIXIN = None ROBOTS_TXT_DISALLOW_ALL = DEBUG
The name of the base template. This setting can be overwritten to point all templates to another base template. This can be used for the Flat page page type.
The template directory where the “Layouts” model can find templates.
By default, this is the first path in
TEMPLATE_DIRS. It can also be set explicitly, for example:
FLUENT_PAGES_TEMPLATE_DIR = os.path.join(SRC_DIR, 'frontend', 'templates')
Whether template paths are stored as absolute or relative paths. This defaults to relative paths:
FLUENT_PAGES_RELATIVE_TEMPLATE_DIR = True
Preferences for the admin¶
Pages can be “tagged” to be easily found in the page tree. Example value:
FLUENT_PAGES_KEY_CHOICES = ( # Allow to tag some pages, so they can be easily found by templates. ('search', _("Search")), ('contact', _("Contact")), ('terms', _("Terms and Conditions")), ('faq', _("FAQ page")), ('impactmap', _("Impact map")), )
When this value is defined, a “Page identifier” option appears in the “Publication settings” fieldset.
Pages which are marked with an identifier can be found
Enable this to prefetch all translations at a regular page. This is useful to display a language choice menu:
FLUENT_PAGES_PREFETCH_TRANSLATIONS = True
RobotsTxtView, enable this setting for beta websites.
This makes sure such site won’t be indexed by search engines.
Off course, it’s recommended to add HTTP authentication to such site,
to prevent accessing the site at all.
Advanced admin settings¶
By default, each
Site model has it’s own page tree.
This enables the multi-site support, where you can run multiple instances with different sites.
To run a single Django instance with multiple sites, use a module such as django-multisite.
You can disable it using this by using:
FLUENT_PAGES_FILTER_SITE_ID = False
FLUENT_PAGES_PARENT_ADMIN_MIXIN / FLUENT_PAGES_CHILD_ADMIN_MIXIN¶
By setting this value, this module will insert your class in the admin. This can be used to override methods, or provide integration other third party applications such as django-guardian.
- The “parent admin” handles the list display for pages.
- The “child admin” handles the edit and delete views for pages.
FLUENT_PAGES_PARENT_ADMIN_MIXIN = 'apps.auth_utils.page_admin.FluentPagesParentAdminMixin' FLUENT_PAGES_CHILD_ADMIN_MIXIN = 'apps.auth_utils.page_admin.FluentPagesChildAdminMixin'
Your project needs to provide those classes, and can implement or override admin methods there.
Advanced language settings¶
The language settings are copied by default from the django-parler variables. If you have to provide special settings (basically fork the settings), you can provide the following values:
FLUENT_DEFAULT_LANGUAGE_CODE = PARLER_DEFAULT_LANGUAGE_CODE = LANGUAGE_CODE FLUENT_PAGES_DEFAULT_LANGUAGE_CODE = FLUENT_DEFAULT_LANGUAGE_CODE FLUENT_PAGES_LANGUAGES = PARLER_LANGUAGES