A flatpages/flatblock application using generic relations to content models.
If you want to add tiny snippets of text to your site, manageable by the admin backend, you would use either django-chunks or django-flatblocks. However, both of them have one problem: you are limited to a predefined content field; a “text” field in chunks and a “title” and “text” field in flatblocks.
django-generic-flatblocks solves this problem as it knows nothing about the content itself. You attach your hand made content node (a simple model) where you can define any fields you want.
Documenation is available online under:
- Django 1.11 compatibility and tests.
- Django 1.10 compatibility and tests.
- Python 3.6 compatibility.
TEMPLATE_DEBUGsetting is no longer honored to raise individual errors, in favor of standard
- Code cleanup and update for Django 1.8+. Python3 Support. Better test integration. Better docs.
- Django 1.2 compatibility! Fixed a bug where tests did not pass under Django 1.2. Thanks to Brian Rosner for this.
- Fixed a bug where an integer was not allowed as a part of a slug.
- Added Danish translation.
- Added better documentation.
- Added unittests.
- If you fetch a not existing “primary key” object the templatetag will fail silently if settings.TEMPLATE_DEBUG is False.
- Added the into argument. You can now display any instance directly without creating and rendering a template.
- You can now pass a context variable with a integer to fetch a specific object.
- Added the ability to pass an integer as slug. This will cause that the templatetag fetches the specific for model with the primary key named in slug.
- Switched from distutils to setuptools. Fixed whitespace.
- Fixed wrong upload path of a contributed, generic block
- Initial release