Package: emencia-cmsplugin-zinnia
Cmsplugin-zinnia is a bridge betweendjango-blog-zinniaanddjango-cms.This package provides plugins, menus and apphook to integrate your Zinnia
powered Weblog into your django-cms Web site.The code bundled in this application is a copy of the originalzinnia.pluginsmodule, made for forward compatibility with
django-blog-zinnia > 0.11.NoteThis is a fork of originalcmsplugin-zinniato be able to release an alternative package to fix compatibility issues
withDjangoCMS>=3.4.ContentsInstallationEntries with pluginsTips for using the apphookSettingsCMSPLUGIN_ZINNIA_APP_URLSCMSPLUGIN_ZINNIA_APP_MENUSCMSPLUGIN_ZINNIA_HIDE_ENTRY_MENUCMSPLUGIN_ZINNIA_TEMPLATESCMSPLUGIN_ZINNIA_BASE_TEMPLATESCMSPLUGIN_ZINNIA_DEFAULT_TEMPLATEChangelog0.8.2.40.8.2.30.8.2.20.8.2.10.8.20.8.10.80.70.60.5.10.50.4.10.40.30.20.1InstallationOnce Zinnia and the CMS are installed, you simply have to registercmsplugin_zinnia, in theINSTALLED_APPSsection of your
project’s settings.Entries with pluginsIf you want to use the plugin system of django-cms in your entries, an
extendedEntrywith aPlaceholderFieldis provided in this package.Just add this line in your project’s settings to use it.ZINNIA_ENTRY_BASE_MODEL = 'cmsplugin_zinnia.placeholder.EntryPlaceholder'NoteYou have to keep in mind that the default migrations bundled with Zinnia
do not reflect the addition made by theEntryPlaceholdermodel.A solution to initialize correctly the database can be:$ python manage.py makemigrations
$ python manage.py migrateTips for using the apphookIf you want to use the apphook to provide the blog functionnalities under a
specific URL handled by the CMS, remember this tip:Once the apphook is registered, you can remove the inclusion of'zinnia.urls'inurls.pyand then restart the server to see it in
full effect.SettingsCMSPLUGIN_ZINNIA_APP_URLSDefault value:['zinnia.urls']The URLsets used for by the Zinnia AppHook.CMSPLUGIN_ZINNIA_APP_MENUSDefault value:['cmsplugin_zinnia.menu.EntryMenu',
 'cmsplugin_zinnia.menu.CategoryMenu',
 'cmsplugin_zinnia.menu.TagMenu',
 'cmsplugin_zinnia.menu.AuthorMenu']List of strings representing the path to theMenuclass provided by the
Zinnia AppHook.CMSPLUGIN_ZINNIA_HIDE_ENTRY_MENUDefault value:TrueBoolean used for displaying or not the entries in theEntryMenuobject.CMSPLUGIN_ZINNIA_TEMPLATESDefault value:[](Empty list)List of tuple for extending the plugins rendering templates.Example:CMSPLUGIN_ZINNIA_TEMPLATES = [
  ('entry_custom.html', 'Entry custom'),
  ('entry_custom_bis.html', 'Entry custom bis')
  ]CMSPLUGIN_ZINNIA_BASE_TEMPLATESDefault value:[('cmsplugin_zinnia/entry_list.html', _('Entry list (default)')),
 ('cmsplugin_zinnia/entry_detail.html', _('Entry detailed')),
 ('cmsplugin_zinnia/entry_slider.html', _('Entry slider'))]Available base templates, these are the shipped template from this application.
Commonly you will prefer to useCMSPLUGIN_ZINNIA_TEMPLATESto add new
templates.CMSPLUGIN_ZINNIA_DEFAULT_TEMPLATEDefault value:NoneInitial value fortemplate_to_renderfield. If empty or undefined, initial
value will be the first item of available template choices.Changelog0.8.2.4Fixed compatibility withDjango>=2.0. Validated as working withDjango==2.1.8,django-cms==3.6.0anddjango-blog-zinnia==0.20.0.8.2.3Fixedtemplate_to_renderfield missing a default value that could result
to broken page when no template was selected at plugin creation.Past migrations have been modified to clean them from any hardcoded
choices that triggered warning message about changed model needing new
migration when you added new template choices;Added data migration to fix plugins entries with empty value fortemplate_to_renderfields, they will be filled with defaut template;template_to_renderfields can no longer be empty, select input do not
show anymore option for empty value;Everything is backward compatible. After updating you will just need to
perform migration forcmsplugin_zinniaapp.0.8.2.2FixedCMSLatestEntriesPluginandCMSSelectedEntriesPluginto use
selected template to render instead of default plugin one.0.8.2.1Renamedcms_toolbar.pytocms_toolbars.pyso Zinnia application appear again in CMS toolbar.0.8.2Fixed compatibility withDjangoCMS>=3.4:Mergedpull request #64;Mergedpull request #65;0.8.1Remove warnings with Django 1.90.8Compatibility with Django 1.80.7PlaceholderEntry mixinCompatibility with Django 1.7 and Zinnia 0.150.6Compatibility with Django-CMS 3.00.5.1Python 3 compatibility fixBetter help texts and legends0.5Archives pluginTag cloud pluginAuthor list pluginCategories pluginsFeatured entries filterOffset for latest entriesDocumentation improvementsConfigurable apphook’s urlsSupport custom auth.User modelFix translations of the pluginsFix HTML rendering without contextCompatibility with Django v1.5Compatibility with Zinnia v0.13Updating the buildout installation0.4.1Compatibility fix for Django-CMS 2.2+0.4Fix issues with Entry.content rendering.Compatibility with latest version of Zinnia.0.3Calendar plugin.QueryEntries plugin.Slider template for plugins.Documentation improvements.Fix breadcrumbs with month abbrev.Compatibility with Django 1.4 and Django-CMS 2.3.0.2Better demo.Renaming modules.Fix dependancies with mptt.FixEntryPlaceholder’s Meta.0means all the entries on plugins.Set menu Nodes to invisible instead of removing.0.1Initial release based onzinnia.plugins.