- Added translations for `Add contacts` icons. [gbastien]
2.2
----------------
- Fixed failing migration because unexisting attribute `exclude_from_nav` was migrated with the parent's value that is an instancemethod and it crashed the transaction during commit because it can not be serialized. [gbastien] - Completelly removed ActionsColumn as it was moved to `collective.eeafaceted.z3ctable` previously. [gbastien] - Moved CachedCollectionVocabulary to collective.eeafaceted.collectionwidget, now named `collective.eeafaceted.collectionwidget.cachedcollectionvocabulary`. Moved also dashboard collection related events. [sgeulette] - Migration: secure attribute get in DashboardPODTemplateMigrator. Include portal portlet migration. [sgeulette] - Added `setuphandlers.add_orgs_searches` that adds dashboards for `collective.contact.core` on the `/contacts directory`. [gbastien]
2.1
----------------
- Added back imio.dashboard.js file to remove faceted spinner and speed up faceted fade speed. [gbastien] - Added migrator `DashboardPODTemplateMigratorWithDashboardPODTemplateMetaType` as due to missing migration to 0.28 where `DashboardPODTemplate meta_type` was changed from `DashboardPODTemplate` to `Dexterity Item`, we may have `DashboardPODTemplate` created with different meta_types that is still cataloged. This way we manage both cases. [gbastien] - The `actions` column was moved to `collective.eeafaceted.z3ctable`. [gbastien]
2.0
----------------
- Change JS `Faceted` options in the `ready` function so we are sure that Faceted exists. [gbastien] - Rely on `collective.eeafaceted.dashboard` to move to Plone5. Dashboard functionnalities working on Plone5 are now moved to this package we are relying on. Needs `eea.facetednavigation` >= 10.0. [gbastien]
1.7
----------------
- Moved some methods to collective.eeafaceted.collectionwidget: _get_criterion, getCollectionLinkCriterion, getCurrentCollection [sgeulette] - Consider other view than "facetednavigation_view" as outside faceted. [sgeulette]
1.6
----------------
- Do not rely on the `context.REQUEST` to get the `REQUEST` because context is a `ram.cached DashboardCollection` and `REQUEST` is not reliable. Use `getRequest` from `zope.globalrequest` to get the `REQUEST`. The `REQUEST` is set in `term.request` so it is directly available. [gbastien]