Welcome to FeinCMS 1.7!
The extensions mechanism has been refactored to remove the need to make models know about their related model admin classes. The new module feincms.extensions contains mixins and base classes - their purpose is as follows: Extensions.
Made views, content type and request / response processors reusable.
The legacy views at feincms.views.legacy were considered unhelpful and were removed.
Previously, the following page manager methods sometimes returned inactive objects or did not raise the appropriate (and asked for) Http404 exception:
The reason for that was that only the page itself was tested for activity in the manager method, and none of its ancestors. The check whether all ancestors are active was only conducted later in a request processor. This request processor was registered by default and was always run when Page.objects.for_request was called with setup=True.
However, request processors do not belong into the model layer. The necessity of running code belonging to a request-response cycle to get the correct answer from a manager method was undesirable. This has been rectified, those manager methods check the ancestry directly. The now redundant request processor require_path_active_request_processor has been removed.
The support for monkey-patching applicationcontent-awareness into Django’s django.core.urlresolvers.reverse() has been removed.
FeinCMS 1.7 requires Django 1.4 or better.