Note
In any template name <tree_path> stands for the value of Category.path, not it’s actual tree_path. This is because of empty tree_path for root categories which would make it impossible to override a template for anything in the root category and the root category itself.
List objects’ listings according to the parameters. If no filtering is applied (including pagination), the category’s title page is rendered:
Otherwise an archive template gets rendered:
The context contains:
Parameters: |
|
---|
All parameters are optional, filtering is done on those supplied
Raises Http404: | if the specified category or content_type does not exist or if the given date is malformed. |
---|
Renders a page for placement. If url_remainder is specified, tries to locate custom view via DetailDispatcher.call_view(). If DetailDispatcher.has_custom_detail() returns True, calls DetailDispatcher.call_custom_detail(). Otherwise renders a template with context containing:
The template is chosen based on the object in question (the first one that matches is used):
Note
The category being used in selecting a template is taken from the object’s Placement, thus one object published in many categories (even sites) can have a different template every time.
Parameters: |
|
---|---|
Raises Http404: | if the URL is not valid and/or doesn’t correspond to any valid Placement |