Saravanan666/pypi-org huggingface dataset:
Package: collective.actions.delete
Deletion of Plone elements from the folder contents view is submitted to a
confirmation form.RequiresPlone 3.x or a later versionInstallationJust addcollective.actions.deleteto theeggslist of theplone.recipe.zope2instancepart in your zc.buildoutLicenseThis software is provided under the GPL v3 license.Credits and supportAlter WayYouenn BoussardGilles LenfantChangelog0.1.5 (2014-03-12)Plone 4.3.3 support
[spereverde]0.1.4 (2013-05-29)Plone 4.3 support
[gotcha]Removing items who’s title has non ASCII chars works (+ test)
[glenfant]Added german translation.
[jone]0.1.3 (2011/05/16)Added dutsch translation (thanks to Kim Paulissen)
[glenfant]z3c.autoinclude awareness
[glenfant]Remove portal id from confirmation screen
[gotcha]0.1.2 (2008/12/15)Back to folder_contents whatever action taken
[glenfant]0.1.1 (2008/10/02)Plone 3.0.x compatible0.1.0 (2008/10/01)Initial release
Package: collective.address
collective.addressThis package provides an Dexterity behavior for location addresses to be used
in Dexterity based types.How to provide a default value for the country fieldIf you want to provide a default value for the IAddress’ country field, you can
provide an ComputedWidgetAttribute adapter like so:from zope.component import provideAdapter
from z3c.form.widget import ComputedWidgetAttribute
from collective.address.behaviors import IAddress
DEFAULT_COUNTRY = "040"  # Austria
provideAdapter(ComputedWidgetAttribute(
    lambda data: DEFAULT_COUNTRY,
    field=IAddress['country']), name='default')Changelog1.6 (2019-06-07)Python 3 compatibilty
[petschki]Added french translation.
[bsuttor]Added italian translation.
[arsenico13]Added update.sh script for i18ndude taken directly from plonecli.
[arsenico13]Updated DE .po file with the update.sh script.
[arsenico13]1.5 (2017-01-13)Translate country name via pycountry translation catalog.
[thet]Code cleanup.
[thet]1.4 (2016-10-06)Add behavior shortnames.
[thet]Removeforattribute in behavior registrations, as this is unsupported.
[thet]Change all URL fields to usezope.schema.URI.
[thet]Added behavior for social media urls.
[agitator]1.3.2 (2015-09-24)Encode SearchableText indexer result in utf-8.
[thet]1.3.1 (2015-08-27)Fix error on creating the title for Person types with non-ascii characters in
names.
[thet]1.3 (2015-07-21)Let IAddressable not derive from schema.Model to have a pure marker
Interface.
[thet]Make sure, all SearchableText parts are seperated by a space.
[thet]1.2 (2015-07-15)Require the last_name attribute of IPerson behavior.
[thet]For the IPerson behavior, compute the title from first and last name and add
title (not required, hidden) and description to the IPerson behavior.
[thet]1.1 (2015-03-04)Add IContact and IPerson behaviors in addition to the IAddress behavior.
[thet]PEP 8.
[thet]1.0 (2014-04-30)initial.
Package: collective.addthis
IntroductionContentsIntroductionChangelog1.3.3 (2013-05-27)1.3.2 (2012-06-01)1.3.1 (2012-02-08)1.3 (2012-02-07)1.2 (2012-01-31)1.1.1 Released 2011-08-181.1 Released 2011-08-171.0.3 Released 2010-11-261.0.2 Released 2010-03-151.0.1 Released 2010-03-031.0 Released 2010-03-03Collective.addthisis a simple Plone addon which bringsaddthis.comservices to Plone CMS.Collective.addthishas customizable addthis url (pointing to your AddThis
username) and AddThis javascript url (pointing to addthis javascript url).
By default those settings have random values I got fromaddthis.comso
that testingcollective.addthiswould be easy. Those values are recommended
to be changed if you’re planning to use this addon in production.There are few other similar addons for Plone which does the same job with
different approach. Ifcollective.addthisdoesn’t do the job for you I
suggest to check these out too:collective.prettysociablecollective.plonebookmarkletssc.social.bookmarkscollective.sharerizerChangelog1.3.3 (2013-05-27)latest plone compatiblity [kiorky, hvelarde]Travis CI [kiorky]Better release infra [kiorky]1.3.2 (2012-06-01)Fix when work offline [toutpt]Refactor SocialMediaSources to work with plone.app.registry and not
fecthing them over http on each rendering. [toutpt, pingviini]1.3.1 (2012-02-08)Fixed javascript bug.1.3 (2012-02-07)Added configuration option to hide AddThis button.Fixed bug where addthis broke javascripts when watching content
without IBelowContentBody provider.Fixed styles to not display border-bottom for link (from Sunbursts
public.css).Added hints where to place css & js resources in registry so that
they get merged with majority of plones own resources.1.2 (2012-01-31)Add Italian translation [giacomos]Added spanish translation [Manuel, Acento Web, S.L.]Uses plone.app.registry for settings [pingviini]Added data_track_callback option [pingviini]Added tests [pingviini]Add french translation. [toutpt]Add collective.googleanalytics integration followinghttp://www.addthis.com/help/google-analytics-integration#.To83N5zOifZ[toutpt]Add data_track_addressbar option
[toutpt]1.1.1 Released 2011-08-18Fixed packaging problems.1.1 Released 2011-08-17Added a configuration setting that allows the user to select which
chicklets display on the page. [pumazi]1.0.3 Released 2010-11-26External javascript cannot be cached, cooked or merged (klingel).Removed a comma from the javscript to fix an error in IE (huub_bouma).Changed the default UI langage from Finnish to English (huub_bouma).1.0.2 Released 2010-03-15Added random addthis url to jsregistry.Changed GS profile name (collective.addthis -> default).1.0.1 Released 2010-03-03Package had missing locales folder and was broken. Fixed and tested.
that everything works correctly now.1.0 Released 2010-03-03Initial release.Adds addthis viewlet under content body.
Package: collective.addtofolder
Introductioncollective.addtofolder allows users to add content to the folder you are currently in. New content will be creaded “next to” the document you currently see.This overrides the default plone-behaviour that the ‘Add Item..’ menu is is only shown when viewing folders or their default pages.collective.addtofolder provides a configlet for the “Plone Control Panel” to enable/disable this behaviour.This behaviour used to be default until version 3.0 and was removed since some users consider it as confusing.See also:http://dev.plone.org/plone/ticket/9569new pliphttp://dev.plone.org/plone/ticket/7968discussionhttp://dev.plone.org/plone/ticket/6744removalSince the translations of “Add to folder” are still present in Plones po-files this should even work in al languages (tested in english and german).Changelog0.2 - RELEASEDremove pyc-files (gnnnnr!)0.1 - RELEASEDInitial release
Package: collective.adlibsyncmanager
IntroductionProvides external methods to sync and create content from Adlib APIFeaturesCreates Object content type in a Plone site based on Adlib API data.Synchronization of content from Adlib API with a Plone site.InstallationIf you are using zc.buildout and the plone.recipe.zope2instance recipe to manage your project, you can do this:
Add collective.adlibsyncmanager to the list of eggs to install, e.g.:[buildout]
        …
        eggs =
                …
                collective.adlibsyncmanagerHow to use method as a cron job?Add to your buildout.cfg:zope-conf-additional =
<clock-server>
        method /SiteName/adlib_sync
        period 60
        user username-to-invoke-method-with
        password password-for-user
        host localhost
</clock-server>Dependenciescollective.objectThe following dependencies are not required unless the creation of pictures and translations is requested.plone.namedfileplone.app.multilingualTodosGet deleted records from API and update contentCreate log document with every request result detailsSend email after several failed API request attemptsChangelog0.1 (2014-11-14)Initial release
Package: collective.ads
IntroductionPlone AdsThis is a product where u can insert commercial ads into your plone site,
including a portlet to show the ads.FeedbackPlease send any changes, improvements, or suggestions regarding this Plone
product to “Four Digits”:mailto:info@fourdigits.nlRequirementsPlone Ads is tested on Plone 3.1 and 3.2, please submit any compatibility issues
you may encounter.Changelog0.1 - UnreleasedInitial release
Package: collective.advancedsearchtamer
Introduction============collective.advancedsearchtamer is a small add-on for Plone 3 which attempts to tamethe advanced search form. It uses javascript to add a checkbox to each searchelement in the form which enables/disables that element.The result is that the urls generated by the search form are generally muchshorter, as only the required fields are sent on the request... _Plone 3: http://plone.org/Installing==========This package requires Plone 3.0 or later.Installing without buildout---------------------------First you need to install this package.You can install this in either the systempython path or in the lib/python directory of your Zope instance. If youhave setuptools installed you can do this using easy_install::easy_install collective.advancedsearchtamerIf you do not have setuptools you can install it manually using the setup.pyscript in the source. If you want to install it insideyour Zope instance instead of system wide you can its ''--prefix='' optionto install in the ''lib/python'' directory of your Zope instance.After installing the package it needs to be registered in your Zopeinstance.  This can be done by putting acollective.advancedsearchtamer-configure.zcml file in the etc/pakage-includesdirectory with this content::<include package="collective.advancedsearchtamer" />or, alternatively, you can add that line to the configure.zcml in apackage or Product that is already registered.Installing with buildout------------------------If you are using `buildout`_ to manage your instance installingcollective.advancedsearchtamer is even simpler. You can install it by addingit to the eggs line for your instance::[instance]eggs = collective.advancedsearchtamerzcml = collective.advancedsearchtamerThe last line tells buildout to generate a zcml snippet that tells Zopeto configure collective.advancedsearchtamer.After updating the configuration you need to run the ''bin/buildout'', whichwill take care of updating your system... _buildout: http://pypi.python.org/pypi/zc.buildoutUsing collective.advancedsearchtamer=================In order to use the the updated search you will first need to install thecollective.advancedsearchtamer product in your site.This is done through the standard ''Add-onproducts'' control panel in the Plone site setup.After this has been done, you should be able to visit the Advanced Searchform and, provided you have javascript enabled, see the enable/disablecheckboxes appear next to each search option.To perform a search, simply check the box next to each option you want tospecify, and then enter/select the values you require using the relevantform elements. Click 'search' as normal to get the results.Copyright and credits=====================collective.advancedsearchtamer is copyright 2009 by Netsight Internet SolutionsIt was written by Matthew Sital-Singh... _Netsight: http://www.netsight.co.uk/Changelog=========1.0 - 2009-03-27----------------* Initial release
Package: collective.ajaxkeywords
IntroductionThis Add-on hides the original keywords viewlet and adds a new one that is based on Tag-Handler (https://github.com/ioncache/Tag-Handler). It allows you to change the keywords/tags via ajax requests.InstallationJust add collective.ajaxkeywords to yout eggs and zcml section in your buildoutLicensecollective.ajaxkeywords is copyright 2011 by Dominik Ruf, and is licensed under the GPL. See docs/LICENSE.txt for details.Changelog0.1dev (unreleased)Initial release
Package: collective.akismet
IntroductionAkismetis a web service for recognising spam comments.
collective.akismet provides a Plone integration of the Akismet web service and
is based on theAkismet Python interfacepackage.collective.akismet was developed as Spam protection plugin forplone.app.discussion, but it can be used independentlycollective.akismet provides a form validator that connects to the Akismet web
service and raises a validation error if Akismet detects spam. The form
validator expects three form fields/values in the request:
‘form.widgets.author_name’, ‘form.widgets.author_email’, and ‘form.widgets.text’.Requirementscollective.akismet requires at least plone.app.discussion 1.0b5.Buildout InstallationAdd the following code to your buildout.cfg to install collective.akismet:[buildout]
...
eggs =
    ...
    collective.akismet
    ...

...
[instance]
...
zcml =
    ...
    collective.akismet
...Changelog1.0b1 (2010-10-04)Special character support added.
[timo]Remove failing plone.app.discussion message factory import.
[timo]1.0a3 - 2010-08-05Remove recaptcha.client.captcha to avoid an ImportError when not installed.
[timo]1.0a2 - 2010-07-16Move AkismetValidator from plone.app.discussion to collective.akismet.
[timo]Remove plone.app.discussion-captcha declaration.
[timo]1.0a1 - 2010-06-14Initial release
[timo, HammerToe]
Package: collective.alerts
IntroductionThis package implements Cory LaViska’s ‘JQuery Alert Dialogs’ for Plone.Basically, they are fancy, styleable replacements for the standard
‘alert’, ‘confirm’ and ‘prompt’ browser functions.Seehttp://abeautifulsite.net/blog/2008/12/jquery-alert-dialogs/for more
details.UsageWhen collective.alerts is installed and the jquery.alerts library registered in
portal_javascripts (should be automatic), then the alerts can be called as
follows:jAlert( message, [title, callback] )jConfirm( message, [title, callback] )jPrompt( message, [value, title, callback] )Dependencies:On Plone 3.x, make sure that you have a newer version of JQuery than what is
shipped with Plone. That would be JQuery > 1.3.5The easiest way to do this is to install collective.js.jquery.Plone 4.x users already have a new enough version of JQuery.Changelog1.2.3 (2011-02-08)Removed the setup.py dependency on collective.js.jquery (not needed for Plone 4) [jcbrand]Added GS-XML (metadata.xml) dependency on collective.js.jqueryui [jcbrand]Added css for the popup [jcbrand]1.2.2 (2010-04-12)Add jquery dependencies to setup.py [jcbrand]1.2.1 (2010-01-27)Remove collective.js.alerts from css registry [toutpt]1.2 - (2009-10-05)Released
Package: collective.alertviewlet
IntroductionCollective alertview allows site administrator and developers to quickly put a
global alert on the site.It is expecially userful to:mark the difference between a demo/stage/training site and the production sitespread maintainance warnings to all users on the sitemake any important message immediately visible sitewideUsage:From the plone control panel, select “Alert message settings”.
Write the message in the text area (html is allowed) and toggle message
visibility using
the checkbox.Versions:Collective.alertviewlet has been tested on Plone 3.2.x and 3.3Credits:Author:
Antonio Tirabasso <antonio.tirabasso@reflab.it>
Francesco Merlo <francesco.merlo@reflab.it>Contributions:
Eleonora Borelli <eleonora@reflab.com>Changelog0.2 (2009-09-22)Updated project descriptionChecked if property sheet has been configuredUpdated profile version0.1 (2009-09-18)Initial release
Package: collective.allowsearch
OverviewProvides an interface and a default adapter to allow users to search the
catalog independent of the View permission.InstallationAdd this package to your buildout or policy package, or add a ZCML slug
for it to your etc/site.zcml.UsageSimply mark any content which you want to be visible in searches for anonymous
users with the IAllowAnonymousSearchMarker interface.This can be done programmatically or using ZCML like:<configure
    xmlns="http://namespaces.zope.org/zope"
    xmlns:five="http://namespaces.zope.org/five"
    i18n_domain="collective.allowsearch">

    <include package="collective.allowsearch" />

    <!--
    EXAMPLE: Allow all ATDocument objects to be found by Anonymous users.
    NOTE: This does _NOT_ change the View permissions in any way.
    -->
    <five:implements
        class="Products.ATContentTypes.content.document.ATDocument"
        interface="collective.allowsearch.interfaces.IAllowAnonymousSearchMarker"
        />

</configure>That’s it. See the package’s doctest for more information.
Package: collective.allowtypes
IntroductionProvides a configlet to set the allowed content types for Plone in a n x n
Matrix.InstallationThese instructions assume that you already have a Plone 3 buildout that’s built
and ready to run.Edit your buildout.cfg file and look for the eggs key in the instance section.
Add collective.allowtypes to that list. Your list will look something like this:eggs =
    ${buildout:eggs}
    ${plone:eggs}
    collective.allowtypesIn the same section, look for the zcml key. Add collective.allowtypes here,
too:zcml = collective.allowtypesUsageA control panel configlet will be installedhttp://localhost:8080/plone/plone_control_panel::vim: set ft=rst ts=4 sw=4 expandtab tw=78 :Change historytrunk (2008-11-11)xxx [ramonski]Changelog0.2 (2008-11-11)changed browser template [ramonski]added control panel configlet [ramonski]added unittests [ramonski]0.1.1 (2008-06-18)removed info logging [ramonski]0.1 (2008-06-18)initial release [ramonski]Created package with ZopeSkel [ramonski]ContributorsRamon Bartl, AuthorDownload
Package: collective.amberjack.portlet
collective.amberjack.portletThis package provides portlet for collective.amberjack package.Set up environmentThis package allows you to create portlets that contain tours.
You can select the tours that can be display and choosen by an user on these portlet.
So this package allows you to create sets of tours on Plone site.Be aware that series 0.9.x is compatible with Plone3, series 1.x is compatible
with Plone4.Useful linksproject wiki, info:http://www.coactivate.org/projects/collectiveamberjackpypi:http://pypi.python.org/pypi/collective.amberjack.portletPlone:http://plone.org/products/collective.amberjack.portletissue tracker:https://bugs.launchpad.net/collective.amberjacksvn repository:http://svn.plone.org/svn/collective/collective.amberjack.portletChangelog1.1 (2010-11-05)moved the check procedure to identify the next tour from the portlet into viewlet
[mirco]updated the cookie that save the next tour; now we save the list of all tour after the current one.
[mirco]set sunburst theme as default
[nekorin]changed a js file name to do not make a conflict.
[mirco]1.1a (2010-09-21)added skins for js and images
[mirco]added function to save in a cookie the next tour
[mirco]added a control for use with sandbox
[mirco]modified the check for launch the tours; from tours and not from the first step
[mirco]add simple validation method
[amleczko]update imports
[amleczko]add filename sorting when tours not selected manualy
[amleczko]0.9.1 (unreleased)anonymous can’t view tour portlet #572137 [fdelia]disabled the completed step feature for portlet [keul]0.9 (2010-04-30)update metadata and pin to proper plone3 versions
[amleczko]Initial release
[amleczko]
Package: collective.annotationbrowser
collective.annotationbrowserThis package allows to browse zope.annotation based items. Package provides
“ann_view” browser view which lists all available (and allowed) annotation
keys and their values.By default, all annotation keys are shown. It is possible to define blacklist
and whitelist. Go to /Plone Site/manage_propertiesForm and add
‘annbrowser.blacklist’ and/or ‘annbrowser.whitelist’ properties (type: list).
If no whitelist is defined, .* is used. There is no blacklist by default.Annotation editorPage /ann_edit allows site manager to edit basic annotation values (strings,
integers and floats currently).Changelog0.3 - 2010/11/04fixed display of Image annotations0.2 - 2010/08/24added ++annotation++KEYNAME view - allows to display required key directly
and without length limitations. pprint is used for rendering the key
content. The traverser idea and code is stolen from
archetypes.fieldtraverser.added ann_remove?keyname=KEYNAME view - immediately removes the keyadded links to ++annotation++ traverser and to ann_remove view to ann_view
page so it is really easy to accidentaly remove any annotation key.0.1 - 2010/08/06Initial release
Package: collective.anonfeedback
This package contains two views, a form that will collect feedback, and view
to view the feedback. They are protected by two different permissions, the
permission to enter feedback is by default given to everyone, and the
permission to view the feedback is by default given to site administrators.The feedback is stored in var/anonfeedback with each feedback in it’s own
file. The reason for this is that if we store the feeback in the ZODB we
create a ZODB transaction, and if you are logged in to the site at that
point, it will be possible to see who wrote the feedback from the Undo
transaction log, and the requirement of this package was explicitly that you
should be anonymous even if you forget to log out.Warning!Please note that it may still be possible to figure out the posters identity
by comparing web-server logs and IP-adresses and times, etc. To achieve true
anonymity you must also anonymize the internet access. The purpose of this
package is just to make it hard for your boss to figure out who thought his
proposal for site color scheme was ugly, not to provide truly anonymous
whistleblower access.ContributorsLennart Regebro,regebro@gmail.comChange history1.0 (2014-03-23)Original release.
Package: collective.anonymouseditpatterns
This package was created to test several assumptions and suggestions to add some mockup patterns to the
‘anonymous’ js/css delivery of pages in Plone 5.2 . Easyform is the defacto forms packages on Plone 5.2 when
you use Python3, but some of its fields require widgets that are by default only bundled and delivered to
logged in users.Seehttps://github.com/collective/collective.easyform/issues/203ContributorsFred van Dijk, Zest Software,info@zestsoftware.nlChangelog1.0.1 (2022-03-19)Fix wrong python_requires in setup.py. [fredvd]1.0 (2021-12-13)Rebuild bundle with Plone 5.2.6:
- plone.staticresources 1.4.4
- Mockup 3.2.7
[fredvd]1.0a2 (2021-03-11)Fix uninstall profile to remove our resource and bundle.
[fredvd]1.0a1 (2021-03-09)Initial release. Adds inline validation and pickadage patterns in an extra bundle
to anonymous visitors. This is necessary when you use easyform on public websites.
The bundle also gets merged into default.js when you run in production.
[fredvd]
Package: collective.anonymousview
Introductioncollective.anonymousviewAllow a logged in user to view a page as anonymous user, so that the user does not have to logout or use another browser to preview
pages anonymously.Changelog1.1 (2012-08-02)fixed import error on Plone 4added z3c.autoinclude supportadded i18n support1.0Initial release1.0.1removed properties.xmladded extra tests
Package: collective.ant
Tell me what your product doesFeaturesCan be bullet pointsExamplesThis add-on can be seen in action at the following sites:
- Is there a page on the internet where everybody can see the features?DocumentationFull documentation for end users can be found in the “docs” folder, and is also available online athttp://docs.plone.org/foo/barTranslationsThis product has been translated intoKlingon (thanks, K’Plai)InstallationInstall collective.ant by adding it to your buildout:[buildout]

...

eggs =
    collective.antand then runningbin/buildoutContributeIssue Tracker:https://github.com/collective/collective.ant/issuesSource Code:https://github.com/collective/collective.antDocumentation: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.ContributorsJian Aijun,jianaijun@gmail.comChangelog1.0a1 (unreleased)Initial release.
[]