Package: collective.portletmetadata
collective.portletmetadataAboutcollective.portletmetadata is a collection of patches that makes it possible edit
settings for each portlet assignment. We denote these settings for metadata thereby
the name of the product.Out of the box the product provides the following features:Possibility for creating local portlets, i.e. portlets that will not be inherited
even though child settings imply so.Possibility for adding a CSS class for a portlet assignment. These are defined
in the controlpanel (stored in registry).
Since version 1.6 you can add any CSS classes (for example from Bootstrap) in a portlet, without first defining it in the control panel.
This is restricted by a permission, so if you do not like this, you can take this permission away from some roles.
The field for choosing a pre-defined class is always available.Possibility for excluding a portlet from being indexed by Google.Plone version compatibilityVersion 2.0: Plone 6 only.Version 1.5: Plone 5 and 6Version 1.3: Plone 5Version 1.2: Plone 4.3UsageWhenever the product is installed a “*” will be visible in the@@manage-portletsview for each assignment. Whenever the user selects this option, he/she can edit
the metadata as described above.See a short guidehere.Related workIdeally, these features should be built intoplone.app.portlets.
Seeissue 13.AuthorBo Simonsen <bo@headnet.dk>MaintainerMaurits van Rees <m.van.rees@zestsoftware.nl>Changes2.0.0 (2023-12-14)Drop support for Plone 5.1.6.0 (2023-12-14)Add field “Custom CSS classes”.
You can use this to freely add any (Bootstrap) classes, on top of the CSS classes made available in the control panel.
The new field and the existing control panel are now only available when you have the new “Portlets: Manage metadata” permission.
By default Manager and Site Administrator have this.
Previously only a Manager could access the control panel and make CSS classes available.
[maurits]1.5.0 (2022-09-08)Make our patches have no effect when the product is not activated.
Until now, when a portlet was marked as local, it was still invisible elsewhere when the product was deactivated,
and you could no longer change the setting.
[maurits]Fix uninstall to remove our registry settings.  [maurits]Have a different template override for edit manager macros on Plone 6.
This uses Bootstrap 5 classes.
[maurits]Fix ImportError on Plone 6, for isDefaultPage.
[maurits]1.4.1 (2022-03-14)Fix Plone 5.0 support by downgrading the minimumplone.app.portletsversion to be 3.0.0.
The 3.x series of plone.app.portlets is the version used by Plone 5.0.
[JeffersonBledsoe]1.4 (2022-01-05)Fix for Plone 5.2 and Python 3 compatibility.
Should still work on Plone 5.0 and between as well.
[maurits]1.3 (2018-01-17)Fix case in managing groups-and contenttype-portlets when the query-string
is no longer in the request.
[kroman0, pbauer]Plone 5 compatibility - this release requires plone 5 (p.a.portlets >= 4.0.0)
[sunew]uninstall profile
[sunew]1.2 (2014-04-22)Allowclass|descriptive titleas format in the control panel.
When this format is used, we show the title in de portlet metadata
edit form.  A simpleclassis of course still supported.
[maurits]Support the local portlet checkbox for ContentWellPortlets.
[mauritsvanrees]1.1 (2014-03-13)Backported local portlets functionality
[bosim]Override Products/ContentWellPortlets/browser/templates/renderer.pt
[mauritsvanrees]1.0 (2013-12-29)Initial release