A enhanced permission system which enable logical permissionsystems to complex permissions
- Alisue <firstname.lastname@example.org>
- Supported python versions
- Python 2.6, 2.7, 3.2, 3.3, 3.4
- Supported django versions
- Django 1.2 - 1.6 and 1.7 rc1
An template based the flatpages like app. Not like django’s flatpages app, django-roughpages render a template file which determined from the accessed URL. It is quite combinient when you want to render simple static page. You do not need to prepare urls.py or views.py anymore for that kind of simple static page.
django-roughpages call roughpages.views.roughpage view with the accessed URL when django raise Http404 exception. The view automatically find the corresponding template file from roughpages directory in one of your template directories. Assume if the user accessed http://localhost/foo/bar/hoge/. If there is no urls pattern patched with the URL, django-roughpages try to find corresponding template file such as templates/roughpages/foo/bar/hoge.html. If django-roughpages find the corresponding template file, it will render the template and return the HttpResponse, otherwise it re-raise Http404 exception.
You can complicatedly select the corresponding template file. django-roughpages determine the filename with a backend system. The default backend is roughpages.backends.AuthTemplateFilenameBackend and it prefer hoge_anonymous.html or hoge_authenticated.html than hoge.html depends on the accessed user authentication state. Thus you can simply prepare the page for authenticated user as <something>_authenticated.html and for anonymous user as <something>_anonymous.html.
You can control the backend behavior with making a custom backend. To make a custom backend, you need to inherit roughpages.backends.TemplateFilenameBackendBase and override prepare_filenames(self, filename, request) method. The method receive an original filename and HttpRequest instance and must return a filename list. The django-roughpages then try to load template file from the beginning of the list, thus the order of the appearance is the matter.
Use pip like:
$ pip install django-roughpages
Add roughpages to the INSTALLED_APPS in your settings module
INSTALLED_APPS = ( # ... 'roughpages', )
Add our extra fallback middleware
MIDDLEWARE_CLASSES = ( # ... 'roughpages.middleware.RoughpageFallbackMiddleware', )
Create roughpages directory in one of your template directories specified with settings.TEMPLATE_DIRS
Create roughpages/foo/bar/hoge.html as follow
<html> <body> This is Hoge </body> </html>
Run syncdb and Start development server with python manage.py syncdb; python manage.py runserver 8000
Access http://localhost:8000/foo/bar/hoge/ and you will see “This is Hoge”
Create roughpages/foo/bar/piyo.anonymous.html as follow
<html> <body> This is Piyo Anonymous </body> </html>
Create roughpages/foo/bar/piyo.authenticated.html as follow
<html> <body> This is Piyo Authenticated </body> </html>
Access http://localhost:8000/foo/bar/piyo/ and you will see “This is Piyo Anonymous”
Access http://localhost:8000/admin/ and login as admin user.
Access http://localhost:8000/foo/bar/piyo/ and you will see “This is Piyo Authenticated”
Any dots (‘.’) in a last part of URL is replaced to underscore (‘_’) to prevent a security risk. See https://github.com/lambdalisue/django-roughpages/issues/3