Saravanan666/pypi-org huggingface dataset:
Package: collective.notices
IntroductionThis package adds Site-Wide Notification/Status Messages for Plone CMS.This package addscontrol panel where site administrator could add new notice, edit/delete
existing noticesviewlet which will insert notices, or multiple notices into plone pageNotice FieldsRequired: rich html ‘Body’ text (with TinyMCE editor)Optional: ‘Display To’ field where admin could pick list of users and/or
groups to display notice to, if not set then notice is displayed to everybodyOptional: ‘Period’ field which includes: Effective and Expiration datetimes
with nice calendar/time widgets; if left empty, then notice is displayed to a
user until he/she closes itNotices ViewletThis viewlet displays each notice with close button, so user can close it. This
action is remembered in a cookie so after page reload notice doesn’t show up.
Also we can have multiple notices for the same user. If notice has set period
field, then notice disappears automatically after Expiration date.ContributorsVladimir Iliev, Original AuthorVitaliy Podoba, Contributor (contact@softformance.com)Changelog1.2 (2016-11-10)Add Timezone-Information via property setter-method instead of overwriting the data converter
for all collective.z3cform.datetimewidget widgets (this fixes#4) [fRiSi]Plone 4.3 compatibility improved [fRiSi]Improved markup for hide link: Added a descriptive text and allow to define
an icon via CSS [fRiSI]Indicate inactive notices in the management view [fRiSi]Add i18n infrastructure and provide German translations [fRiSi]Allow to use css3 animations when hiding notices [fRiSi]1.1 (2015-03-14)Plone 4.3 compatibility [sureshvv, fRiSi]1.0 - April 9, 2014Made calendar widget icon show up.
[Vitaliy Podoba]Styled control panel.
[Vitaliy Podoba]Styled Notice Viewlet.
[Vitaliy Podoba]Ajaxified hide notice action.
[Vitaliy Podoba]Added more docs.
[Vitaliy Podoba]Added Period field to notices listing.
[Vitaliy Podoba]Added initial functionality
[Vladimir Iliev]Package created using zopeskel.
[Vladimir Iliev]
Package: collective.novate
IntroductionThis package provides a link on the sharing page to change the ownership of
a content item. The link goes to a form with an auto-complete widget for
finding the new owner.InstallationThis product depends on five.grok, plone.directives.form,
plone.formwidget.autocomplete and plone.principalsource. The latter three in
turn depend on plone.autoform, plone.z3cform and z3c.form. On Plone 3.x,
this means you need to add a few lines to your buildout to correctly
configure dependencies. (You should also check that these packages have been
released. At the time of writing, they have not, and as such must be run from
a development checkout. However, they should be released shortly.)Firstly, in the [zope2] section of your buildout.cfg, enable fake eggs, but skip some:[zope2]
recipe = plone.recipe.zope2install
...
fake-zope-eggs = true
additional-fake-eggs =
    ZConfig
    pytz
skip-fake-eggs =
    zope.component
    zope.testing
    zope.i18n
    zope.securitypolicy
    zope.app.zcmlfiles
...Then, add some version pins to your [versions] block. Create this if it does
not exist already:[buildout]
...
versions = versions
...

[versions]
...
zope.i18n = 3.4.0
zope.testing = 3.4.0
zope.component = 3.4.0
zope.securitypolicy = 3.4.0
zope.app.zcmlfiles = 3.4.3Changelog1.0b4 - 2009-09-18Fix broken release.1.0b3 - 2009-09-17Redirect to /view to be clear about what we’ve changed the ownership of
(for folders) and avoid weird behaviour when changing the ownership of
files and images.
[optilude]1.0b2 - 2009-09-07Work around dodgy code in PloneUtils and AccessControl. If you want
something done right, you might as well do it yourself.
[optilude]1.0b1 - 2009-04-17Initial release
Package: collective.oaiintercom
Introductioncollective.oaiintercom is a product that extends a Plone site to
enable it to provide OAI-PMH metadata harvesting capabilites
(http://www.openarchives.org/pmh). It provides metadtata information in
service requests to a Service Provider via the OAI-PMH v2.0 protocol
specification.Metadata requests are provided through a top level view (/oai) and must
follow the conventions listed in the specification (http://www.openarchives.org/OAI/openarchivesprotocol.html).Once you have enabled this product you can test your Plone site using the
Repository Explorer (http://re.cs.uct.ac.za/).Changelog2.1.1Added MANIFEST.in file [blambert555]2.1Added properties page and “provideMetadataFor” field to allow configuration
over what gets shown in search results [blambert555]2.0Refactored product to use page templates and export them in XML format
instead of using canned strings. [blambert555]Fixed numerous bugs that would keep the OAI output from displaying. [blambert555]Updated for 4.0.x [blambert555]1.0Initial release
Package: collective.object
IntroductionInformation about an object typically collected by museumsChangelog0.6 (2015-04-13)Refactor object schema.Add @@edit custom template.Add custom adapter for object creation.0.5 (2015-04-10)Add object identification fields.Add NL translation to identification fields.0.4 (2015-04-09)Add main fields.Add dexterity indexer behavior.Change view template to get meta tags.Add translations for fields.0.3 (2015-04-09)Add collection fieldset0.2 (2015-04-09)Transform object in schema driven type. Add DataGridField support0.1 (2015-04-09)Initial release
Package: collective.odoo.pas
This product adds a Plone Ahthentication Service Plugin that will allow you to share authentication between Plone and Odoo.
Opening a Plone session will automatically open an Odoo session by adding the two cookies.
The Odoo users (not partners) will be listed in the plone group and users formFeaturesCreate a user through the standard Plone join form and get the users in OdooAuthenticate in Plone unsing Odoo login / pwdList Odoo users in PloneInstallationInstall collective.odoo.pas by adding it to your buildout:[buildout]

...

eggs =
    collective.odoo.pasand then runningbin/buildoutContributeIssue Tracker:https://github.com/collective/collective.odoo.pas/issuesSource Code:https://github.com/collective/collective.odoo.pasDocumentation:https://docs.plone.org/foo/barSupportIf you are having issues, please let us know.
We have a mailing list located at:project@example.comLicenseThe project is licensed under the GPLv2.ContributorsMartronic-SA,martronic@martronic.chChangelog1.0a1 (unreleased)Initial release.
[Martronic-SA]
Package: collective.opengraph
collective.opengraphThis package is a part of the Plone’s collective.fg bundle. It adds the opengraph metadata to your HTML head section.Supported metadata:og:site_name name of the siteog:url url of the webpageog:title title of the webpageog:description description of the webpageog:image your webpage image (either ‘image’ field of your context or collective.contentleadimage one)from the control panel you can manage following settings:
- the default og:type
- which content types should be opengraph metadata awareCustomizationOne of the goals of this package is to allow developers extend the default metadata definition.
It’s availabe threw IOpengrapMetatags adapter:from collective.opengraph.interfaces IOpengraphMetatags
from collective.opengraph.viewlets import ATMetatags

class MyATMetatags(ATMetatags):

    implements(IOpengrapMetatags)

    @property
    def metatags(self):
        tags = super(MyATMetatags, self).metatags
        tags.update({'og:newtype': 'custom value'})
        return tagsYou can also customize existing og values:from collective.opengraph.interfaces IOpengraphMetatags
from collective.opengraph.viewlets import ATMetatags

class AnotherMetatags(ATMetatags):

    implements(IOpengrapMetatags)

    @property
    def title(self):
        return '%s - Lorem ipsum' % self.context.Title()Changelog1.0.1 (2012-10-16)Docs update and fixed manifest file [amleczko]1.0 (2012-10-15)refactored and release during PloneConf2012 sprint [amleczko]0.1dev (unreleased)added action to (un)mark ‘IOpengraphable’ content typesadded translationsregistered viewlet for ‘IOpengraphable’ content typesadded og:type meta tagadded default configurations in IRegistryfirst release
Package: collective.ordereddict
IntroductionImplementshttp://docs.python.org/dev/library/collections.html#ordereddict-objectsfor Python 2.4 or up
Code fromhttp://code.activestate.com/recipes/576693/by Raymond Hettinger
Native OrderedDict implementation available from Python >= 2.7 and Python >= 3.1Changelog0.1 - UnreleasedInitial release
Package: collective.orderedmultiselectwidget
Introduction:This package fixes a Plone/Zope2 Acquisition bug for the
OrderedMultiSelectWidget that appears in zope.app.form.browser.itemswidgets.py line 556.Note: The itemswidgets.py module has been moved to zope.formlib in newer versions of
zope/ztk.The OrderedMultiSelectWidget is used automatically for zope.schema.List type
fields.How do I know if this bug affects me?If you get errors in your traceback or error_log similar to the one below,
you might have be affected: (XXX is variable)Line 166, Column 8Expression: <PathExpr standard:u’view/selected’>Names:{‘args’: (),‘context’: <zope.schema._field.List object at 0x2aaab329f110>,‘usage’: <zope.pagetemplate.pagetemplate.TemplateUsage object at 0x2aaab1800090>,‘view’: <zope.app.form.browser.itemswidgets.OrderedMultiSelectWidget object at 0x2aaaae5684d0>,‘views’: <zope.app.pagetemplate.viewpagetemplatefile.ViewMapper object at 0x2aaab1800650>}Module zope.tales.expressions, line 217, in __call__Module zope.tales.expressions, line 211, in _evalModule zope.app.form.browser.itemswidgets, line 562, in selectedModule zope.schema.vocabulary, line 124, in getTermLookupError: XXXXInstallation:Just make sure that collective.orderedmultiselectwidget is installed via the
plone control panel or the portal_quickinstaller tool in the ZMI.Afterwards it should just work.Why not fix the bug in zope.app.form and zope.formlib?zope.app.form and zope.formlib are Plone/Zope2/Acquisition agnostic. They do not
depend on Acquisition and no one will want them to.A bug might however be contributed to plone.app.form. I’ll contact the
dev-list, but for now, this is a bug-fix package for people being affected on
in-production systems.Change History:0.1 (unreleased)Initial release [jcbrand]
Package: collective.ots
Project Description===================The summary may not be perfect but it is a good starting point for adescription. Mostly the summary is pretty good though.The description is only auto generated when you ADD a new Archetypescontent item WITHOUT a description. You may edit this description at anytime. You can invoke the summarizer on existing content items byselecting 'Summarize' from the 'Actions' menuInstall using buildout=======================Just add collective.ots (and optionally ots) to the egges section of you buildout ::eggs:...otscollective.otsRun buildout, restart your server and activate the product in your add ons section.You do not have to use the ots egg (http://pypi.python.org/pypi/ots)if you have problems installing it. Any ots found in your system will do,so you may install it with: ::sudo apt-get install libots0or the package manager of your distribution, or install it from source.check that ots is installed and working with: ::ots -?which will give you the output: ::Usage:ots [OPTION...] [file.txt | stdin]  - Open Text SummarizerHelp Options:-?, --help                Show help optionsApplication Options:-r, --ratio=<int>         summarization % [default = 20%]-d, --dic=<string>        dictionary to use-o, --out=<string>        output file [default = stdout]-h, --html                output as html-k, --keywords            only output keywords-a, --about               only output the summary-v, --version             show version information- Code repository: https://svn.plone.org/svn/collective/collective.ots/- Questions and comments to product-developers@lists.plone.org- Report bugs at http://plone.org/products/collective.ots/issuesChange history**************Changelog=========0.3 (2011/11/16)----------------- remove id and title from SearchableText0.2 (2011/09/28)----------------- catch exceptions if ots is not found0.1 (2011/02/22)----------------- added 'Summarize' view to 'Actions' menu- Created recipe with ZopeSkel["nan"]Download********
Package: collective.overridemailrecipients
Introductioncollective.overridemailrecipients forwards all mails sent from Plone. Use this package on testing and development environments where you want to test emails sent thru Plone, but not want to use the real addresses.This package is always active by patching MailHost. The recipient(s) in the ‘To’ header are replaced by‘plone@localhost’ or a configurable mail address.FeaturesAll emails sent thru the Plone mailer are forwarded to one mail addressBcc and Cc headers are strippedInstallationTo yourbuildout.cfg, add:eggs =
    ...
    collective.overridemailrecipientsAfter that, just install via the “Add-on” controlpanel.UsageAfter installation this packages is configurable thru the site setupEmail address, this address is used to forward mails toEnabled or disable or disable mail forwardindTODOAdd to, cc and bcc in forwarded mailContributorsPawel Lewicki <lewicki@gw20e.com>Kim Chee Leong <leong@gw20e.com>Changelog1.0.2 (2013-03-08)Re-added missing tests.1.0.1 (2013-03-08)Added test module,  accidentally removed it from version control1.0 (2013-03-08)Initial release
Package: collective.package
Introductioncollective.packageis a sample add-on package for Plone developers.MotivationBoilerplate code fromZopeSkelis nice; but not quite as nice as example code.InstallationYou may install this add-on via Buildout, like so:virtualenv-2.7 .
bin/pip install zc.buildout
bin/buildout init
cat << EOF > buildout.cfg
[buildout]
extends = http://build.pythonpackages.com/buildout/plone/latest
[plone]
eggs += collective.package
EOF
bin/buildout
bin/plone fgExamplesThis package contains code examples for common add-on package tasks in Plone.
For example, creating a Python package that “shows up” as an installable
add-on in the Plone control panel. Or installing an authentication plugin.Here is a list of examples:How do I make my package “show up” in Plone?Use theQuick Installer.How do I create an authentication plugin?Use thePluggable Auth Service.Changelog0.3.1 (2012-04-07)Clean up package
[aclark]0.3.0 (2012-04-07)Clean up package
[aclark]0.2 (12/01/2010)Add PAS exampleRename Products.product to collective.package0.1 - UnreleasedInitial release
Package: collective.pageheader
ContentsIntroductionScreencastContributorsTODOChangelog1.0.11.0IntroductionA Plone package for adding an image header to your contents.It adds a new image field called ‘Page header’ to all your content types.If an header is found on the context this will be used as header image, otherwise the machinery will look up into parents to find one.In this way we can have a section header and override it per-content.The image field is injected using archetypes.schemaextender, of course.The image is showed within the viewletpageheaderthat by default is assigned to the managerbelowcontenttitle.There’s no custom CSS so at first it appears a bit ‘raw’. It’s upon you to provide the better style for your header ;).ScreencastHere you find a shortscreencaston how it works. Enjoy.ContributorsSimone Orsi [simahawk]TODOmake enabled portal types configurable via control panelChangelog1.0.1improved docs, add screencast1.0first release
Package: collective.pamfixes
collective.pamfixesThis Plone add-on patches theAlternateLanguagesViewletfrom plone.app.multilingual.
The fix addressesIssue #153which can generate broken or inccorect links for therel="alternate"links of multilingual pages.
This add-on registers an overriding viewlet with a fix to now generate the correct links.ContributorsZach Cashero,zach@propertyshelf.comThomas Massmann,thomas.massmann@it-spir.itChangelog1.1 (2016-06-16)Add post path info to the alternate link urls.
[zcashero]1.0 (2016-05-19)Initial release.
[zcashero]Add support for Plone 4.1.x (p.a.m. 1.x), 4.2.x (p.a.m. 1.x), 4.3.x (p.a.m. 2.x) and Plone 5.x (p.a.m. 3.x).
[tmassman]
Package: collective.pantry
collective.pantryThe main objective of this product is to make it easy for integrators to enable
TinyMCE templates (user addable HTML snippets) in your RichText fields and
tiles. These HTML snippets can be added using two approaches. You can define
theme defined snippets, idealy defined by the themer or designer. In addition,
you can also enable the users to be able to define their own HTML snippets
using the content type provided.The snippets are available from the template button on TinyMCE, ready to be
used.It also enables the “Pantry”. It’s a summary view of Plone style elements along
with the theme and user snippets. It’s an update of the good oldtest_renderingview.Theme SnippetsThey are defined as HTML files in a directory calledpantry. The format is
plain HTML. At a later point, you can also override them or add more theme
snippets if you customize the theme using the Plone Theme editor.User SnippetsThis product makes available a content type calledsnippet. Each snippet is a
page-like object that defines a single snippet. They are meant to be
user-defined. As any other content type, you can give the users permissions
over them, or disable them completely, depending on your use case.InstallationInstall collective.pantry by adding it to your buildout:[buildout]

...

eggs =
    collective.pantryand then runningbin/buildoutContributeIssue Tracker:https://github.com/collective/collective.pantry/issuesSource Code:https://github.com/collective/collective.pantryDocumentation:https://docs.plone.org/foo/barSupportIf you are having issues, please let us know.
We have a mailing list located at:project@example.comLicenseThe project is licensed under the GPLv2.ContributorsVictor Fernandez de Alba,sneridagh@gmail.comChangelog1.0a1 (unreleased)Initial release.
[sneridagh]
Package: collective.passwordwall
# PasswordwallThis puts your Plone site behind a login, without actually logging in a Plone user.## Use caseThis is intended for use on public websites, so “Published” in Plone workflow
terminology, where you want to restrict access because the site isn’t meant to
be open to the public yet.It enables people to view the site as as an anonymous user (in the Plone
sense), so without having to log in into Plone.It is not intended for intranets, and other sites where login is required
anyway. In that case, this product is either not necessary, or you’re better
off using iw.rejectanonymous.### Plain textThe site password is stored internally as plain text. Do not use your personal
super secure password here, because we intended it to be used by several
people.The password should be easy to look up and communicate, which is why we store
it in plain text.If you have a different use case for this product where you want a different
behaviour: Wedowelcome pull requests!## AlternativesYou might also achieve this with:
- web server Basic Auth
- IP restrictionBut if your hosting setup is such that that isn’t an option,
this package might help.## How to useGo to the Plone control panel, to the “Security” tab.You will see a checkbox “Site behind password”. Check it to activate the passwordwall.
This means users will need to supply credentials before they can use the site.Users that are already logged in as Plone users are not asked for credentials.The password can be set by the “Password” field.
This is what people have to type in the “password” box in the dialog to get access.### Picking a passwordIt’s recommended to not use dictionary words as is, nor should you use other
well known phrases as passwords. This is because their MD5 hashes (which we
store as the cookie value) would easily reveal the password. Just mixing in a
couple of numbers or other characters should make for a fine password.
Try it onhttps://isc.sans.edu/tools/reversehash.htmlif you’re not sure.### Changing the passwordWhen you change the password, existing cookies will be invalid, because the
password hash changed. People without Plone accounts (or who are logged out
from Plone) will be forced to re-enter the credentials.## Thank youIngeniweb for iw.rejectanonymous, some of whose code this product copied.
All spelling mistakes are also their fault.
Package: collective.patchlinguaploneissue273
When CacheSetup is enabled, LinguaPlone cause an infinite loop and zope core dump
Its occur when cache tool emit header of css registry file.Products.CacheSetup.content.cache_tool.getRuleAndHeaderSet call Products.LinguaPlone.I18NBaseObject.getTranslation wich call Products.PloneLanguageTool.getContentLanguage and
getContentLanguage do an unrestrictedTraverse on css path wich cause the infinitThis package aimed to resolve this issueChangelog1.0dev (unreleased)Initial release
Package: collective.pathtouid
Table of contentsIntroductionHow is not going well on Kupu feature?TODOAuthorsChangelogIntroductionA Plone utility and view to help you to convert your paths inside site contents.You can use the new provided utility:>>> utility = getUtility(IUIDConverted)
Do something with the utility methodsAlso, a Plone view is provided to automatically fix paths inside documents.Simply call:http://yourplone/folder/subfolder/@@convertUIDThen you can fix all contents in the “subfolder” tree.How is not going well on Kupu feature?TheKupuproject has inside a similar feature for fixing Kupu (and TinyMCE) created
links.However this not always works, for example, if for some reason you contents have inside absolute
paths like this:/plonesite/foo/fooAlso: Kupu is less used in Plone worldandeven if you have it in your Plone environment,
youmusthave it installed and selected as your WYSIWYG editor to use its converting
features.WarningThis product is in early development stage; it will not substitute Kupu migration
utility and is much less tested.Use at your own risk…Data.fs backupcan make difference between life and deathTODOInternationalization of the UIPlone fixing form needs some love right nowMuch more testBeeing a complete alternative to Kupu migration toolAlso give the “UID to Path” featureRelative path conversion is not working for all possibiel path (i.e: ‘../foo/a-document’)Transformation will not works if linking method/traverse of target object
(i.e: “foo/image-id/image_thumb”)AuthorsThis product was developed by RedTurtle Technology team.Changelog0.1.0a (2010-12-22)Initial release
Package: collective.pdbpp
collective.pdbppAn addon for Plone that does allow you to use thepdbpppackageInstallationInstallcollective.pdbppby adding it to your buildout, e.g.:[instance]
eggs +=
    collective.pdbppand then runningbin/buildout.When your instance starts you can enter a pdb session by adding the pathpdbto any URL, e.g.:http://localhost:8080/pdbhttp://localhost:8080/Plone/pdbAuthorsTheSyslab.comTeam.ContributorsPut your name here, you deserve it!Alessandro Pisa,Syslab.comContributeIssue Tracker:https://github.com/collective/collective.pdbpp/issuesSource Code:https://github.com/collective/collective.pdbppDocumentation:https://docs.plone.org/foo/barSupportIf you are having issues, please let us know in theissue tracker.LicenseThe project is licensed under the GPLv2.Contributorsale-rt,alessandro.pisa@gmail.comChangelog1.0.0a2 (2023-11-27)Initial release.
[ale-rt]
Package: collective.pdfdocument
This package provides PDF metadata extraction and cover image generation
for Plone. Please see the collective.filemeta package for more information
(at github or PyPI).FeaturesPDF metadata extractionPDF cover page PNG generationInstallationInstall collective.pdfdocument by adding it to your buildout:[buildout]

...

eggs =
    collective.pdfdocumentand then runningbin/buildoutContributeIssue Tracker:https://github.com/collective/collective.pdfdocument/issuesSource Code:https://github.com/collective/collective.pdfdocumentSupportIf you are having issues, please let us know.LicenseThe project is licensed under the GPLv2.ContributorsPetri Savolainen,petri.savolainen@koodaamo.fiChangelog1.0rc2 (2016-06-07)Implement collective.filemeta 1.0rc2 API & policy change
(always overwrite metadata on ObjectAddedEvent)1.0a1 (unreleased)Initial release.
[petri]