/docs/releases/1.4.rst

http://github.com/feincms/feincms · ReStructuredText · 75 lines · 59 code · 16 blank · 0 comment · 0 complexity · f9ec2fde67f3d48cc702f2b422797a02 MD5 · raw file

  1. =========================
  2. FeinCMS 1.4 release notes
  3. =========================
  4. * FeinCMS supports more than one site from the same database with
  5. ``django.contrib.sites`` now. Thanks to Bojan Mihelac and Stephen Tyler
  6. for the work and insistence on this issue.
  7. * It is possible to customize the administration model inline used for
  8. content types. This means that it's possible to customize more aspects
  9. of content type editing and to reuse more behaviors from Django itself,
  10. such as ``raw_id_fields``.
  11. * FeinCMS has gained support for ``django-reversion``.
  12. * Reusing the media library in your own content types has become much
  13. easier than before. When using a
  14. ``feincms.module.medialibrary.fields.MediaFileForeignKey`` instead of
  15. the standard ``django.db.models.ForeignKey`` and adding the media file
  16. foreign key to ``raw_id_fields``, you get the standard Django behavior
  17. supplemented with a thumbnail if the media file is an image. This requires
  18. the next feature too, which is...
  19. * Custom ``InlineModelAdmin`` classes may be used for the content types now
  20. by adding a ``feincms_item_editor_inline`` attribute to the content type
  21. specifying the inline class to be used.
  22. * New projects should use ``feincms.content.medialibrary.v2.MediaFileContent``
  23. instead of ``feincms.content.medialibrary.models.MediaFileContent``. The
  24. argument ``POSITION_CHOICES`` and the corresponding field have been
  25. renamed to ``TYPE_CHOICES`` and ``type`` because that's a more fitting
  26. description of the intended use. The old and the new media file content
  27. should not be mixed; the hand-woven ``raw_id_fields`` support of the
  28. old media file content was not specific enough and interferes with
  29. Django's own ``raw_id_fields`` support.
  30. * FeinCMS has gained a preview feature for pages which shouldn't be
  31. accessible to the general public yet. Just add the following line
  32. above the standard FeinCMS handler::
  33. url(r'', include('feincms.contrib.preview.urls')),
  34. Another button will be automatically added in the page item editor.
  35. Apart from all these new features a few cleanups have been made:
  36. * FeinCMS 1.2 removed the CKEditor-specific rich text content in favor of a
  37. generalized rich text content supporting different rich text editors.
  38. Unfortunately the documentation and the available settings only reflected
  39. this partially. This has been rectified. Support for ``TINYMCE_JS_URL``,
  40. ``FEINCMS_TINYMCE_INIT_TEMPLATE`` and ``FEINCMS_TINYMCE_INIT_CONTEXT`` has
  41. been completely removed. The two settings ``FEINCMS_RICHTEXT_INIT_CONTEXT``
  42. and ``FEINCMS_RICHTEXT_INIT_TEMPLATE`` should be used instead. See the
  43. :ref:`contenttypes` documentation for more details.
  44. * The two settings ``FEINCMS_MEDIALIBRARY_ROOT`` and
  45. ``FEINCMS_MEDIALIBRARY_URL`` have been removed. Their values always
  46. defaulted to ``MEDIA_ROOT`` and ``MEDIA_URL``. The way they were used
  47. made it hard to support other storage backends in the media library.
  48. If you still need to customize the storage class used in the media
  49. library have a look at ``MediaFile.reconfigure``.
  50. * Support for the ``show_on_top`` option for the ``ItemEditor`` has been
  51. completely removed. This functionality has been deprecated since 1.2.
  52. * A few one-line Page manager methods which were too similar to each other
  53. have been deprecated. They will be removed in the next release of FeinCMS.
  54. This concerns ``page_for_path_or_404``, ``for_request_or_404``,
  55. ``best_match_for_request`` and ``from_request``. The improved
  56. ``for_request`` method should cover all bases.
  57. * A few page methods have been deprecated. This concerns ``active_children``,
  58. ``active_children_in_navigation`` and ``get_siblings_and_self``. The useful
  59. bits are already available through Django's own related managers.