Updated syndication framework porting notes.
This is based on some experience porting older code and trying to work out why my feed content was empty. git-svn-id: http://code.djangoproject.com/svn/django/trunk@12742 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
ff2d0ebdb8
commit
70037f80ac
|
@ -508,9 +508,14 @@ Using the new Feed class, these feeds can be deployed directly as views::
|
||||||
# ...
|
# ...
|
||||||
)
|
)
|
||||||
|
|
||||||
If you currently use the ``feed()`` view, the ``LatestEntries`` class
|
If you currently use the ``feed()`` view, the ``LatestEntries`` class would
|
||||||
would not need to be modified apart from subclassing the new
|
often not need to be modified apart from subclassing the new
|
||||||
:class:`~django.contrib.syndication.views.Feed` class.
|
:class:`~django.contrib.syndication.views.Feed` class. The exception is if
|
||||||
|
Django was automatically working out the name of the template to use to render
|
||||||
|
the feed's description and title elements (if you were not specifying the
|
||||||
|
``title_template`` and ``description_template`` attributes). You should ensure
|
||||||
|
that you always specify ``title_template`` and ``description_template``
|
||||||
|
attributes, or provide ``item_title()`` and ``item_description()`` methods.
|
||||||
|
|
||||||
However, ``LatestEntriesByCategory`` uses the ``get_object()`` method
|
However, ``LatestEntriesByCategory`` uses the ``get_object()`` method
|
||||||
with the ``bits`` argument to specify a specific category to show. In
|
with the ``bits`` argument to specify a specific category to show. In
|
||||||
|
|
Loading…
Reference in New Issue