nephila/dev/: djangocms-redirect-0.1.1.post3 metadata and description

Homepage | Simple index

A django CMS enabled application to handle redirects

author Paolo Romolini
author_email p.romolini@nephila.it
classifiers
  • Development Status :: 3 - Alpha
  • Framework :: Django
  • Framework :: Django :: 1.8
  • Framework :: Django :: 1.9
  • Intended Audience :: Developers
  • License :: OSI Approved :: BSD License
  • Natural Language :: English
  • Programming Language :: Python :: 2
  • Programming Language :: Python :: 2.7
  • Programming Language :: Python :: 3
  • Programming Language :: Python :: 3.3
  • Programming Language :: Python :: 3.4
  • Programming Language :: Python :: 3.5
keywords djangocms-redirect
license BSD
platform
  • UNKNOWN
File Tox results History
djangocms-redirect-0.1.1.post3.tar.gz
Size
8 KB
Type
Source
djangocms_redirect-0.1.1.post3-py2.py3-none-any.whl
Size
10 KB
Type
Python Wheel
Python
2.7

A django CMS enabled application to handle redirects

This is heavily borrowed from django.contrib.redirects with three major changes:

Why using process_request?

Doing database queries in the middleware process_request is heavily discouraged as it’s a performance hit, especially when doing redirects which are just a tiny part of the processed requests. Except that sometimes it’s just what you need (for example to “hide” content without deleting / unpublishing it) By caching both existing and non existing redirects for a given URL the performance hit is minimized for the use cases that requires process_request.

Documentation

The full documentation is at https://djangocms-redirect.readthedocs.io.

Features

  • Set old and new path, by selection existing django CMS pages or writing down the complete address
  • Select the redirect status code (301, 302)
  • Support for status code 410

Running Tests

Does the code actually work?

source <YOURVIRTUALENV>/bin/activate
(myenv) $ pip install -r requirements-test.txt
(myenv) $ python setup.py test

Credits

Tools used in rendering this package:

History

0.1.1 (unreleased)

  • Added missing migration.
  • Fix compatibility issue with Django 1.8

0.1.0 (2016-02-01)

  • First release on PyPI.