djangocms-redirect 0.6.0

A django CMS enabled application to handle redirects

A django CMS enabled application to handle redirects

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

• Selection of django CMS pages

• Selection of redirect status code

• Middleware can processed in the request or response phase

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.

Installation

See https://djangocms-redirect.readthedocs.io/en/latest/installation.html

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

Credits

Tools used in rendering this package:

• Cookiecutter

• cookiecutter-djangopackage-helper

History

0.6.0 (2020-11-15)

Features

• Drop Python 2, Django < 2.2 - Update toolchain (#39)

• Fix Handling of trailing slashes in redirects (#31)

Unreleased

• Nothing yet

0.5.0 (2019-12-27)

• Add compatibility with Django 2.2

• Drop compatibility with Django < 1.11

• Drop compatibility with django CMS < 3.6

• Move to django-app-helper

• Add support to match unquoted strings as redirect old path

0.4.0 (2019-08-22)

• Add subpath matching

0.3.1 (2019-07-13)

• Ignore querystring when matching redirect objects

0.3.0 (2019-03-11)

• Added compatibility to Django 2.0, 2.1

0.2.3 (unreleased)

• Add support to match unquoted strings as redirect old path

0.2.2 (2019-06-02)

• Ignore querystring when matching redirect objects

0.2.1 (2019-04-22)

• Fixed compatibility issue with Django 1.8

0.2.0 (2018-11-03)

• Updated for Django 1.11

• Added configurable cache timeout

• Added configuration option to check redirect on 404 only

0.1.1 (2017-11-19)

• Added missing migration.

• Fixed compatibility issue with Django 1.8

0.1.0 (2016-02-01)

• First release on PyPI.