Saravanan666/pypi-org huggingface dataset:
Package: collective.diffbot
This tool allows you to use diffbot.com API within your Plone siteInstallAdd collective.diffbot to your eggs and zcml section in your buildout
and re-run buildout.Install collective.diffbot within Site Setup > Add-onsRegister for a diffbot token at:http://diffbot.com/pricing/Within your Plone Site > Site Setup > Diffbot API add token and other diffbot
settingsUpgradeWithin “Plone > Site setup > Add-ons” click on upgrade button available for
collective.diffbot (if any)UsageAdddiffbotCSS class to your links:<a href="http://www.bbc.co.uk/news/uk-21375594"
   class="diffbot">Addrelattribute to tell to the system where to display diffbot.com results:<div class=".diffbot-container"></div>
<a href="http://www.bbc.co.uk/news/uk-21375594"
   class="diffbot"
   rel=".diffbot-container">ChangelogTODO:Cache: Client’s browser/localstorage1.0 (2013-02-13)Initial release
[avoinea]
Package: collective.diggdigg
IntroductionDiggDiggis a sharing tool (ala addthis) for Wordpress.
This addon provide DiggDigg to Plone.About DiggDiggWith Digg DiggDigg, you have an all in one social sharing plugin for your site. Display all social sharing buttons nicely on your blog and make it look amazing, just like Mashable.CreditsCompaniesPlanet Makina CorpusContact Makina CorpusCIRB / CIBGContact CIRBPeopleJeanMichel FRANCOIS aka toutpt <toutpt@gmail.com>Changelog1.0 (2013-01-02)Initial release
Package: collective.directory
collective.directoryDirectory package for PloneUse dev dataYou can initialize dev data withmake plone-site
./bin/instance fgand after go tohttp://localhost:8080/PloneContributorsLaurent Lasudry, Original Author [Affinitic]Changelog0.2.15 (2017-02-08)Set good class for listingcards.pt
[mgennart]0.2.14 (2016-09-28)Fix geomap import from collective.geo.leaflet.
[bsuttor]0.2.13 (2016-04-27)Fix typo import step registry.0.2.12 (2016-04-27)Add upgrade step for export view (to csv file).0.2.11 (2016-04-18)Add a new view “collective_directory_export_view” on directory to export cards to csv file.0.2.10 (2016-01-15)remove special chars in str replacementreindex cards in collective_directory_assign_geolocation view0.2.9 (2016-01-13)Add new method that clean a string. Use it to change category_name to category_id when importing cards from csv.0.2.8 (2016-01-13)Remove service OpenMapQuest.0.2.7 (2016-01-08)Add translation for all content types.
[bsuttor]0.2.6 (2016-01-08)Bad release.0.2.5 (2016-01-08)Add new view to set Geolocation to each Cards in a directory.
[boulch]Change zip_code schema from int to string.
[boulch]0.2.4 (2015-07-07)Correct a css class for email in detailcard.ptFix card in card are now return into json view.
[bsuttor]Open website link into a new page.
[bsuttor]0.2.3 (2015-02-10)Fix js error, use maxHeight instead of maxheight
[bsuttor]0.2.2 (2015-02-03)Use maxheight instead of height in control directory.
[bsuttor]0.2.1 (2015-02-03)Sort category by id in legend.
[bsuttor]Fix height and overflow for category legend
[bsuttor]0.2.0 (2015-02-02)Do not use geojson for directory view. Use marker and layerGroup instead
[bsuttor]0.1.8 (2015-01-20)Check if portal_directory exists.0.1.7 (2015-01-15)Try to add markercluster (Leaflet), first step.
[bsuttor]0.1.6 (2015-01-15)Order map and force width to 100% on install.
[bsuttor]Fix: card not imported into zcml.
[bsuttor]0.1.5 (2015-01-14)Imporve upgrade step with class change.
[bsuttor]0.1.4 (2015-01-14)Add import from csv tab for a directory.
[bsuttor]Improve creation of geojson leaflet objects.
[bsuttor]0.1.3 (2014-12-05)Update migration category. If a card has multi category,
it choose first one and forgot others.
[bsuttor]0.1.2 (2014-12-04)Add migration profile.
[bsuttor]Add migrate schedule opening_hours
[schminitz]0.1.1 (2014-10-07)Add upgrade step to rename all object with name from title.
[bsuttor]Fix tests
[laulaz]0.1 (2014-08-21)Initial release
Package: collective.directoryresourcepatch
IntroductionThis allows for resources in the form of ++resource++foo/css/bar.css
to be traversed by tools like the ResourceRegistries. Original fix
adapted from collective.jqueryui.Changelog1.2 (Unreleased)1.1 2011-02-05Check for parent __roles__ before copying, because a five.grok
ZopeTwoDirectoryResource parent does not have __roles__1.0 2010-06-17Initial release
Package: collective.disableuser
This Plone addon allows a site administrator to block and unblock users.FeaturesBlock/unblock users through the Plone User controlpanelBlock/unblock users through a REST endpointTranslationsThis product has been translated intoEnglishGermanInstallationInstall collective.disableuser by adding it to your buildout:[buildout]

...

eggs =
    collective.disableuserand then runningbin/buildoutContributeIssue Tracker:https://github.com/collective/collective.disableuser/issuesSource Code:https://github.com/collective/collective.disableuserDocumentation:https://docs.plone.org/foo/barCreditsThis plugin is developed and maintained bykitconcept.If you are having issues, please let us know.SupportIf you are having issues, please let us know via the github issue tracker athttps://github.com/collective/collective.disableuser/issues.LicenseThe project is licensed under the GPLv2.ContributorsRoel Bruggink,roel@jaroel.nlChangelog1.0a1 (2017-04-10)Initial release.
[jaroel]
Package: collective.disclaimer
DisclaimerTable of ContentsDisclaimerLife, the Universe, and EverythingMostly HarmlessDon’t PanicInstallationUsageHow Does It Work?Share and EnjoyChangelog1.0b1 (2018-12-08)1.0a1 (2018-05-14)Life, the Universe, and EverythingShow a disclaimer the first time a user visits a site.Mostly HarmlessGot an idea? Found a bug? Let us know byopening a support ticket.Don’t PanicInstallationTo enable this package in a buildout-based installation:Edit your buildout.cfg and add the following to it:[buildout]...eggs=collective.disclaimerAfter updating the configuration you need to run ‘’bin/buildout’’, which will take care of updating your system.Go to the ‘Site Setup’ page in a Plone site and click on the ‘Add-ons’ link.Check the box next to ‘Disclaimer’ and click the ‘Activate’ button.UsageAfter installing the package,
go to the ‘Disclaimer’ configlet on ‘Site Setup’ and enable the feature.The Disclaimer control panel configlet.Now, the first time a user visits the site the disclaimer will be shown at the bottom of the page.The Disclaimer viewlet at work.Users will see the disclaimer again whenever information in the configlet is updated.How Does It Work?This package registers a new viewlet onplone.portalfooterviewlet manager.
The viewlet is normally hidden and it will only be shown after checking the user hasn’t seen it yet.
The information on last time the viewlet was updated is stored in the user’s browser local storage.Share and EnjoyThis package would not have been possible without the contribution of the following people:Héctor VelardeFreepik(warning icon)You can find an updated list of package contributors onGitHub.Changelog1.0b1 (2018-12-08)Register the controlpanel for any context.
The correct registry is automatically acquired.
This way, it’s possible to set different disclaimer texts in a Lineage site with lineage.registry installed.
[thet]Add adisclaimer-innerwrapper to allow easier styling, e.g. positioning the viewlet centered on the website and darkening the whole background.
[thet]Move styles and scripts into the viewlet, so that they are included when using Diazo and just using the viewlet selector to copy the viewlet into the theme.
[thet]Add an “OK” button instead of the close link.
When the button is hit, the viewlet is closed and the storage key is set.
Previously the storage key was immediately set even without using the “close” link.
[thet]Fix translation of default values on configlet (HT @fredvd).
[hvelarde]Fix style of hover and visited links inside disclaimer viewlet.
[agnogueira]1.0a1 (2018-05-14)Initial release.
Package: collective.discussionintegration.plonegazette
IntroductionIf both products plone.app.discussion and Products.PloneGazette are installed
the creation of any PloneGazette contenttype fails, because PloneGazette
contenttypes not provide the adapter for a particular interface.This product makes possible the creation of the PloneGazette contenttypes
if there is an installation of plone.app.discussion in your instance.Changelog1.0.0Initial release
Package: collective.discussion.mentioning
This product introduce mentions in plone.app.discussion
textarea.When write comments you can use @ to put a referente to
a site user (eg. @jhonsmith)The product it’s usehttps://www.npmjs.com/package/tributejsto allow the mention behaviourInstallationInstall collective.discussion.mentioning by adding it to your buildout:[buildout]

...

eggs =
    collective.discussion.mentioningand then runningbin/buildoutUsageYou can install the product in the portal quickinstaller.
Installing collective.discussion.mentioning will enable comments
globaly; then in comment you can mention site users.This product also register an event that send email notification
to mentioned people.DependenciesThis products has been developed and tested on plone 5.1.4 .
Other 5.x versions should works.ContributeIssue Tracker:https://github.com/collective/collective.discussion.mentioning/issuesSource Code:https://github.com/collective/collective.discussion.mentioningTODOAdd some testAuthorsThis product was developed by RedTurtle Technology team.LicenseThe project is licensed under the GPLv2.ContributorsRedTurtle,sviluppo@redturtle.itChangelog1.0b1 (2021-07-20)Fix js to avoid breaking when comments are not available
[pnicolli]1.0a1 (2018-12-13)Initial release.
[lucabel]
Package: collective.discussionplus
IntroductionThis package provides some enhancements to Plone’s standard commenting
functionality. It attempts to keep as much of the existing commenting
machinery as possible, but adds the following features:Events:AnIObjectAddedEventis fired when a discussion item (described by the
interfaceProducts.CMFCore.interfaces.IDiscussionResponse) is created.Similarly, anIObjectRemovedEventis fired when a discussion item is
deleted.Indexing:Content items gain two additional catalogue indexes:number_of_comments,
which contains the number of comments left on a content item, andcommentators, which contains a list of unique usernames of those who
have left one or more comments on the content item.number_of_commentsis also available as catalogue metadata.Collections are configured so that it is possible to search by these
indexes. For example, the ‘Current author’ criterion can be used to list
all content items upon which the current user has left a comment.Discussion items gain an additional catalogue metadata column,comment_subject, which contains the title of the content item that was
commented upon (note that this is not updated if the content item changes
title).Workflow:Discussion items will respect the workflow set in portal_workflow. By
default, theone_state_workflowis used, which means a comment is
always published. An additionalcomment_review_workflowis installed,
which has two states:pendingandpublished. Comments may either be
published or deleted.A new view, @@review-comments, is available for any folder or the portal
root. This allows site-wide (or folder-wide) moderation of comments, with
quick publish/delete operations.Note that the @@review-comments view makes a few assumptions:Comments pending review are always in thependingstate. You can add
areview_staterequest parameter to specify a different state to search
for, however.There is a transition calledpublishto move a comment frompendingtopublished. You can request a different transition by providing a
request parameterpublish_transition.Furthermore:Thenumber_of_commentsindex will only include comments in thepublishedstate.Neither theportal_catalogClear and rebuild, nor theportal_workflowUpdate security settingsoperation will correctly
find and update comments, due to the way that comments are stored.RequirementsThis product requires Plone 3.3+ (and will likely not work with Plone 4). In
particular, it relies onplone.indexer, which is part of Plone 3.3+.Changelog1.0b2 - 2009-04-17Catch up to Plone 3.3
Package: collective.diversion
collective.diversioncollective.diversion wraps the existing behaviour for broken objects in the ZODB and provides a lookup table that will
be processed in advance of passing down requests. This allows developers to declare old locations of their classes and
have them be automatically and seamlessly migrated to the new code on load.UsageSimply include the following ZCML declaration in your code:<configure
    xmlns="http://namespaces.zope.org/zope"
    xmlns:diversion="http://namespaces.plone.org/diversion">

    <diversion:class
        old="Products.example.oldlocation"
        new="collective.example.shiny"
        />

</configure>CaveatsDiverted classes will persist their new class when they are written.  However, when ZODB stores references to persistent objects it stores both the oid and the name of the class.  Those class name references will only be updated when the persistent object they are attached to is re-serialised (modified).  Unfortunately this package cannot do this for you as there is no way to find the set of objects which reference a particular object (quickly).  You’ll have to leave the diversion directives in your package until you can confirm that all instances and all references have been updated.Changelog1.0 (Unreleased)Overrides the cPickle.Unpickler class in ZODB ExportImport to allow for copy/paste as well as export.
(MatthewWilkes)Rebind the class factory to existing DB connections on initialization
(MatthewWilkes)ZCML declaration to register diversionsImplementation of classFactory that uses diversionsContributorsTom Blockley
Alan Hoey
Matthew WilkesSponsored byTeam Rubber, Bristol
Package: collective.django
This package allows you to use theDjangoORM withinPlone.It takes care to merge Django transaction management within Zope’s own
transaction manager.Basic usageIn order to use this package you must have a setup that looks like the following:Your settings module must be within buildout’s “adjusted”sys.path. This means it should be importable from within Plone, hence
that it should be an egg (either released or more commonly in development).
Jacob Kaplan-Moss explains how to do this for aDjango buildout.Your buildout should contain both the Plone parts and the Django parts
together, hence the standard Plone buildouts plus the bits you see in
Jacob’s tutorial. Make sure that your plone instance has, within its eggs,
the project one (shorturlsin Jacob’s example) either derived from
buildout’s ones or local to the instance.The second step is to make sure that your Plone instance has a special
environment variable that Django needs to know where its settings are. Hence
put, under your instance buildout section, something like this:[buildout]
...
[instance]
recipe = plone.recipe.zope2instance
...
environment-vars =
    DJANGO_SETTINGS_MODULE shorturls.testsettingsAgain values are borrowed from Jacob’s post.NotePlease note that this environment variable will be set only if you
runbin/instance. Therefore when using supervisord, make sure you
have it runbin/instance consoleand not anyrun.pyscript
directly which would completely bypass setting the environment
variable and leave you in the mud.Then just add the egg to your buildout, like this:[buildout]
...
eggs =
    ...
    collective.djangoThe package itself relies onz3c.autoincludeto load its ZCML when Plone is
pulled up. In case this does not work, include a:<include package="collective.django" />Within your package ZCML.And whenever you will import your Django models from Plone, the transaction
will be managed by Zope.TestingTo run the tests, a minimal buildout is included. After checking out the source
code, run the following:$ python bootstrap.py
$ bin/buildout
$ bin/testAnd the tests should be ran.Changelog1.0 (2014-08-29)fix to work with Django 1.6
[vangheem]0.2 (2011-09-28)fix bad release0.1 (2011-09-16)Django 1.3 compatibility and initialization fixes [vangheem]Initial public version [shywolf9982]ContributorsSimone Deponti <simone.deponti@abstract.it>Nathan Van GheemA big thanks to the developers ofzope.sqlalchemyfor providing a good
“template”.Initial developement supported byAbstract Open Solutions
Package: collective.dms.batchimport
ContentsIntroductionTestsContributorsChangelog1.3.0 (2022-04-01)1.2.5 (2020-10-07)1.2.4 (2017-05-30)1.2.3 (2016-04-15)1.2.2 (2014-11-28)1.2.1 (2014-11-27)1.2 (2014-10-24)1.1 (2014-03-24)1.0 (2014-03-20)This package can read OS directories to find files to import. A metadata file can be
associated to each file.It creates for each file a dms item containing the file as a dmsmainfile.IntroductionThis package provides a configuration view, where you can define:a path to a directory to process, called the root directorya path to a directory, where to move processed filesa table where filename prefixes can be associated to portal typesThe root directory can contain a directory structure that will be followed to place
in imported dms content.
This directory structure must already exist in Plone.Each file can be joined to a metadata file in json format (A directory like
containing attributes).Example files structure:“folder 1” / “file1.pdf”“folder 1” / “file1.pdf.metadata”“folder 1” / “folder2” / “file2.pdf”TestsThis add-on is tested using Travis CI. The current status of the add-on is :ContributorsGauthier Bastien, IMIOStéphan Geulette, IMIOVincent Fretin, EcreallCédric Messiant, EcreallFrédéric Peters, Entr’ouvertDavid Convent, Entr’ouvertChangelog1.3.0 (2022-04-01)Corrected UnicodeEncodeError.Removed prefix from filenameSort filenames naturallyUsed filename as title if no metadataAdded script to add metadata (nothing done for now)
[sgeulette]1.2.5 (2020-10-07)Test portal type more generically.
[sgeulette]1.2.4 (2017-05-30)Set internal_reference_no if not set.
[sgeulette]Added dmsmainfile portal type parameter at creation.
[sgeulette]1.2.3 (2016-04-15)Removed useless message.
[sgeulette]1.2.2 (2014-11-28)Removed a fake attribute present in the dict passed to createContentInContainer.
[sgeulette]1.2.1 (2014-11-27)Return created objects
[sgeulette]1.2 (2014-10-24)Added specific role and permission to call batchimport view
[sgeulette]1.1 (2014-03-24)Remove useless parameter
[sgeulette]Don’t force title
[sgeulette]Skip useless directories
[sgeulette]Apply default_value only if necessary
[sgeulette]Pep8 corrections
[sgeulette]1.0 (2014-03-20)Improvements
[Frédéric Péters]Use adopt_user to create document and main file
[sgeulette]add a new @@fileimport endpoint
[cedricmessiant]Added configlet
[Frédéric Péters]Some improvements
[sgeulette]Read and import of files
[Frédéric Péters, David Convent]Package created using templer
[cedricmessiant]
Package: collective.dms.scanbehavior
FeaturesThis behavior adds some metadata related to scanning:
* scan_id : scan identification as a barcode
* version : version number
* pages_number : pages number
* scan_date : scan date
* scan_user : scan user
* scanner : scanner or pc informationTranslationsThis product has been translated intoEnglishFrenchInstallationInstall collective.dms.scanbehavior by adding it to your buildout:[buildout]

 ...

 eggs =
     collective.dms.scanbehaviorand then running “bin/buildout”ContributeIssue Tracker:https://github.com/collective/collective.dms.scanbehavior/issuesSource Code:https://github.com/collective/collective.dms.scanbehaviorSupportIf you are having issues, please let us know.LicenseThe project is licensed under the GPLv2.ContributorsFranck NGAHA,franck.o.ngaha@gmail.comStephan GEULETTE,stephan.geulette@imio.beChangelog1.3.0 (2023-09-07)Improved date range.
[sgeulette]Cleanup: isort, useunittestinsteadunittest2,
removed dependency onecreall.helpers.testing.
[gbastien]1.2 (2023-07-20)fix : [DMS-949] min & max for scan_date
[bleybaert]1.1 (2018-01-04)Added fieldto_signto the behavior.
[gbastien]1.0 (2017-05-30)Moved version attribute to the scan tab.
[gbastien]Move the signed attribute from IDmsFile schema
[mpeeters]Added signed index
[sgeulette]0.4 (2016-04-20)Add version attribute.
[sgeulette]0.3.3 (2015-11-24)Don’t store None in catalog. [sgeulette]0.3.2 (2015-06-05)Corrected MANIFEST [sgeulette]0.3.1 (2015-06-05)Modified scan_id index [sgeulette]0.3 (2014-11-28)Added scan_id as index [sgeulette]0.2.1 (2014-09-02)Updated changes.Corrected manifest.0.2 (2014-04-15)renamed IScan in IScanFields.changed zcml description of behaviortranslate the title and description of the behavior in the interface.delete the folder content.moved the zcml definition of import step in profile.correct the manifest.renamed “scan_user” to “operator”.0.1 (2014-04-14)Initial release.
[fngaha]
Package: collective.document-hide-summary
.. This README is meant for consumption by humans and pypi. Pypi can render rst files so please do not use Sphinx features.If you want to learn more about writing documentation, please check out: http://docs.plone.org/about/documentation_styleguide.htmlThis text does not appear on pypi or github. It is a comment.==============================================================================collective.document_hide_summary==============================================================================Adds Document view templates that hides the title, or the summary(description), or both the title and the summary.Features--------- uninstalls cleanlyDocumentation-------------After you activate this add-on, every page ("Document" content type)on your site will have new Display menu choices "Hide Title", "HideSummary", and "Hide Title and Summary".Beware: deactivating and/or removing this add-on will result in errorson pages (Documents) that you set to use the "Hide Summary" view. Tofix those pages, you must invoke selectViewTemplate on each page andspecify the default document_view, e.g.http://localhost:8080/Plone/my-page/selectViewTemplate?templateId=document_viewAlternatively, you can use the Management Interface on each such page, e.g.http://localhost:8080/Plone/my-page/manage_propertiesFormand delete the property named "Layout".Translations------------This product has not been translated.Installation------------Install collective.document_hide_summary by adding it to your buildout::[buildout]...eggs =collective.document_hide_summaryand then running ``bin/buildout``Contribute----------- Issue Tracker: https://github.com/collective/collective.document_hide_summary/issues- Source Code: https://github.com/collective/collective.document_hide_summaryLicense-------The project is licensed under the GPLv2.Contributors============- T. Kim Nguyen, kim.nguyen@wildcardcorp.comChangelog=========1.1.1 (2016-11-28)----------------- update add-on description[tkimnguyen]1.1 (2016-11-28)----------------- add views "Hide Title" and "Hide Title and Summary"[tkimnguyen]1.0 (2016-11-25)----------------- Fix PyPi trove classifier[tkimnguyen]- Add warning about deactivating or removing the add-on, and how tofix pages that were set to use the Hide Summary view.[tkimnguyen]- Initial release.[tkimnguyen]