django-new-preferences 0.2

Django app allowing users to set app specific preferences through the admin interface.

Django Preferences

Django app allowing users to set app specific preferences through the admin interface.

Provides singleton admin views for Preferences objects and a simple interface to preference values. Singleton views ensure only one preference intance per site is available for each Preferences class.

Note

django-new-preferences requires and supports Django’s “sites” framework, which means you can have multiple preferences, each associated with a particular site.

Note

django-new-preferences version 0.0.5 and higher requires Django 1.3 and higher for correct operation. If you are getting the super vague Error: cannot import name receiver error on startup either update to Django 1.3 or use django-new-preferences version 0.0.4 or earlier.

Contents

• Django Preferences

  • Installation

  • Usage

• Authors

• Changelog

  • next

  • 0.2

  • 0.1

  • 0.0.6

  • 0.0.5 (2011-08-17)

  • 0.0.4 (2011-08-11)

  • 0.0.3

  • 0.0.2

  • 0.0.1

Installation

1. Install or add django-new-preferences to your Python path.

2. Add preferences to your INSTALLED APPS setting.

3. Add django.contrib.sites to your INSTALLED APPS setting. django-new-preferences associates preferences to specific sites and thus requires Django’s “sites” framework to be installed.

4. Optionally, add preferences.context_processors.preferences_cp to your template context processors settings. This will automatically add a preferences variable to your template context:

   TEMPLATE_CONTEXT_PROCESSORS = (
       ...other context processors...,
       "preferences.context_processors.preferences_cp",
   )

Usage

To create preferences for your app create a Django ORM model as usual, with the model inheriting from preferences.models.Preferences. Also specify preferences.models as your model’s module:

from django.db import models
from preferences.models import Preferences

class MyPreferences(Preferences):
    portal_contact_email = models.EmailField()

Admin classes are specified as per usual, except that they have to inherit from or be registered with preferences.admin.PreferencesAdmin, i.e.:

from django.contrib import admin

from preferences.admin import PreferencesAdmin
from <my_app>.models import MyPreferences

admin.site.register(MyPreferences, PreferencesAdmin)

When your model is registered with admin it will show up under the Preferences app label in Django admin.

Preferences can be accessed in Python by importing the preferences module and traversing to your required preference in the form preferences.<ModelName>.<field>, i.e.:

from preferences import preferences

portal_contact_email = preferences.MyPreferences.portal_contact_email

If you’ve specified the preferences.context_processors.preferences_cp as a TEMPLATE_CONTEXT_PROCESSORS you can similarly access your preferences within templates through the preferences variable, i.e.:

{{ preferences.MyPreferences.portal_contact_email }}

Authors

Praekelt Consulting

• Shaun Sephton

• Euan Jonker

• Hedley Roos

Changelog

next

1. Django 2 and Python 3.5 compatibility. Django 1.9 is no longer supported.

0.2

1. Move to tox for tests.

2. Django 1.9 to 1.11 support. The official minimum supported version is 1.9.

0.1

1. Cleanup and fixing of tests courtesy of senyor.

2. Rewrite distinct query so it works with Oracle backend.

0.0.6

1. Better packaging.

0.0.5 (2011-08-17)

1. Added sites support.

2. Added unittests.

0.0.4 (2011-08-11)

1. Cleanup. Docs polish.

0.0.3

1. Spelling correction, thanks tiktuk.

0.0.2

1. Doc update to indicate importance of placing url include before admin url include.

0.0.1

1. First super alpha release.