Saravanan666/pypi-org huggingface dataset:
Package: collective.comicbookreader
IntroductionA Comic Book Reader is an image viewer specific for comic books. The most common formats for comic books are *.cbz, *.cbr and *.cbt.
These are simple zip/rar/tar archives with special extensions.
This product add a new display view to File content: cbrview. This view allow to extract images present in the file and to display them in an cool way.These are the features provided:display images from archive filenavigation with buttons and keyboard arrowsNo flash please! Everything is based on javascript with a pure html fallback.normal mode and japanese mode: in most of the japanese comics pages start from right. You can easly switch the images positionsingle page and dual pagefullscreen viewThis product has been inspired to the fantastic opensource comic book readerComixChangelog1.0dev (2011-11-02)Initial release
Package: collective.complexrecordsproxy
collective.complexrecordsproxyProviding a proxy class for plone.registry allowing IObject fields to be stored as separate records using the plone.registry collection support.MotivationWith z3c.form it is possible to create forms allowing users to create and edit lists of complex records.An example:TODO from here.We have a main interface with an object field etc.We build a hierarchic structure composed of native types.
All boils down to simple native types in the end, and so in theory is possible to store in the registry without violating this principle of plone.registry:“To avoid potentially
breaking the registry with persistent references to symbols that may go away,
we purposefully limit the number of fields supported.UsageChangelog1.1 (2022-01-13)Add Python 3 & Plone 5.2 / 6.0 compatibility
[boulch, laulaz]1.0 (2016-01-29)Initial release
[sunew, tomgross]
Package: collective.conference
Conference Management Software on top of PloneA simple conference management tool which can be
deployed on Plone.Features include:Anonymous registration & CFP submissionFullcalendar based schedule displayMulti-track supportAt the moment, requires diazotheme.bootstrap to appear
prettyChangelog1.0a2Fix anonymous submissions [kagesenshi]Added listing template [sweemeng]Added SchemaTable to help generating table from schema [kagesenshi]Added attendee list, vegetarian list, and session list [kagesenshi]Added multi-days, multi-room support [kagesenshi]Added workflows for session and participant [kagesenshi]Bunch of minor bugfixes [kagesenshi]1.0a1Initial release
Package: collective.consent
Provides a functionality to ask authenticated users for consent to different topics, before they can continue. One can add multiple consent items and define which user will have to give there consent based on there permission roles. Each of this users have to give the consent before they can continue to work.DemoThis is realized by viewlet which will check a list of consents for each user/consent_item combination and redirect the user to the consent item case they still have to give there consent.SoupInternally the consents are stored in a soup on the ConsentsContainer (‘/consents’) object.FeaturesAllows you to add multiple consent items (documents).A consent item consists of a Title, Description, RichText and a custom button text.Also you can define an update period, when the user has to give the consent again.For every consent item one can choose the target permission roles and consent update period.Users are only ask for consent on published consent items.One can reset (invalidate) all existing consents for a consent item.ToDoSupport local roles, currently only if the user has global roles that match, she will see the consent note.Add a global list of consents, sorted per user (maybe)remove Anonymous from roles vocab, as we only support authenticated usersallow users to remove there consent?list given consents on the user dashboard (action: my consents)InstallationInstall collective.consent by adding it to your buildout:[buildout]

...

eggs =
    collective.consentand then runningbin/buildout, start Plone and activate the add-on in the add-on’s control panel. Then add a ConsentContainer on the top-level (portal-root).ThanksInitial implementation by: Derico -https://derico.deSponsored byhttps://www.uni-giessen.deContributorsMaik Derstappen (MrTango) -md@derio.deContributeIssue Tracker:https://github.com/collective/collective.consent/issuesSource Code:https://github.com/collective/collective.consentSupportIf you are having issues, please let us know.LicenseThe project is licensed under the GPLv2.ContributorsMaik Derstappen,md@derico.deChangelog2.0b1 (2023-01-19)Plone 6 compatibility
[MrTango]1.0b3 (2021-02-09)Fix permission on consent_item_consents view
[MrTango]1.0b2 (2019-11-19)add plone.app.contenttypes as dependency
[MrTango]sync travis config with tox config
[MrTango]remove plone.app.contenttypes dependency and define RichText field our self.
[MrTango]Add some german translations
[MrTango]Fix i18n domain, add styles, refacture views, exclude consents container from nav
[MrTango]1.0b1 (2019-05-16)Initial release.
[MrTango]
Package: collective.contactauthor
IntroductionA Plone customization for the “Contact the author” form.Normally in Plone only authenticated member can send internal messages to the author. This product open
the form also to anonymous users.When anonymous try to contact an author, they must provide also an email address and a captcha protection
value.Please note that access to theauthorpage is still guarded by the Plone setting
“Allow anyone to view ‘about’ information” in the “Security settings” control panel.You can still edit the contact author configuration from the new “Contact author settings” to change
this behavior. You can restore Plone default (where users must be authenticated) or freely enable it
to all anoymous users (this can be dangerous… this option is only provided for some intranet purpose).Form protectionThe captcha protection is given by thecollective.recaptchaproduct.SecurityKeep in mind that, even behind a robot/bot protection, this product open your site to anonymous message from
the Web. It’s mainly targeted to intranet environment.The given anonymous email can be unexistent (or the someone else ones).DependenciesThis product has been tested on Plone 4.3.CreditsDeveloped with the support ofS. Anna Hospital, Ferrara; S. Anna Hospital supports thePloneGov initiative.AuthorsThis product was developed by RedTurtle Technology team.Changelog1.1.0 (2014-09-01)Fixed MANIFEST file [keul]Many i18n infrastructure fixes [keul]Added control panel settings [keul]Uninstall profile added [keul]Added tests [keul]1.0.0 (2012-11-12)Fixed Plone 4 compatibility [cekk]0.1.1 (2011-04-05)italian translation fixes [keul]be more friendly is recaptcha is not configured [keul]if the used is not anonymous do not show the recaptcha field at all [keul]0.1.0 (2011-03-03)Initial release
Package: collective.contact.duplicated
This add-on is part of thecollective.contact.*suite. For an overview and a demo of these suite, seecollective.contact.demo.Add a view to manage contact duplications.InstallFor the moment, this needs collective.contact.faceted with batch actions allowed.
Select two (or more) contacts (organization, held_position, person, etc) and click
on “Merge duplicated” button.It is also possible to pass a data field with data that do not come from an existing contact. Such data may be merged with the final contact.TestsExtendAdapters of field objects that implements IFieldRenderer interface
renders the content of a field on the compare screen.
Create a new adapter if you have specific fields.ContributorsThomas Desvenain,thomas.desvenain@gmail.comEric Brehault,ebrehault@gmail.comSimon Prévidente,simon.previdente@makina-corpus.comStephan Geulette,stephan.geulette@imio.beChangelog0.6 (2022-08-19)Made buildout and tests running.
[sgeulette]Protect compare view against xss
[sgeulette]Avoided error in RelationList field when duplicated and canonical are set on the same field. We do not set a second
RelationValue pointing to canonical. (ValueError: term values must be unique !)0.5 (2018-01-04)Optimized back references update.
[thomasdesvenain]Hide ‘merge persons’ option when we merge object with non-object.
[thomasdesvenain]Revert: do merge action with Manager role.
It allowed to make actions without accurate permissions.
[tdesvenain]0.4 (2017-10-03)Handle when field value is a ComputedAttribute (from an acqproperty)
[thomasdesvenain]Do not dismiss merge if only one UID + data
[ebrehault]Avoid error with field using plone.app.vocabularies
[sgeulette]Do merge action with Manager role to avoid security problems
[sgeulette]0.3.1 (2017-02-09)Prevent fatal error when a back reference relation to a duplicated contact
is out of sync with any actual content.
[thomasdesvenain]Prefer a 400 error than a 500 when user directly access to merge page without accurate params.
[thomasdesvenain]0.3.0 (2016-09-23)Merge contacts with data
[simon-previdente]0.2 (2015-11-24)Fix plone.protect compliancy
[ebrehault]Fix permission: anybody allowed to add contacts must be able to merge
duplicates
[ebrehault]0.1 (2015-06-02)Initial release.
[tdesvenain]
Package: collective.contact.importexport
Import and export organizations and persons with csv files, there are 4 csv files:
- organizations
- persons
- functions_file
- occupied_functions_file! This is a WIP, only flat organizations can be imported for now.FeaturesImport flat organizations listExamples of csv fileshttps://github.com/IMIO/collective.contact.importexport/blob/master/src/collective/contact/importexport/tests/data/organizations.csvDocumentationFull 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 intoFrenchEnglishInstallationInstall collective.contact.importexport by adding it to your buildout:[buildout]

...

eggs =
    collective.contact.importexportand then runningbin/buildoutContributeIssue Tracker:https://github.com/IMIO/collective.contact.importexport/issuesSource Code:https://github.com/IMIO/collective.contact.importexportSupportIf you are having issues, please let us know in github issues tracker.LicenseThe project is licensed under the GPLv2.ContributorsBenoit Suttor,bsuttor@imio.beChangelog0.3.9 (2018-10-26)Now you can import taxonomy from collective.taxonomy.
[bsuttor]Add collective.taxonomy dependency.
[bsuttor]0.3.8 (2018-07-02)Get use_parent_address from file before import obj.
[bsuttor]Remove title from import person doc.
[bsuttor]0.3.7 (2018-03-22)Use plone.api instead of invokefactory.
[bsuttor]0.3.6 (2018-02-08)Improve importer, bug fix activity importer.
[bsuttor]0.3.5 (2018-01-22)Add collective.geo importer, you can now use latitude and longitude field in your files to import.
[bsuttor]0.3.4 (2017-12-18)Import become faster.
[bsuttor]0.3.3 (2017-09-29)Add import person.
[bsuttor]Do not add all not known field into activity.
[bsuttor]0.3.2 (2017-06-02)Remove profilehook.
[bsuttor]0.3.1 (2017-06-01)If IContactDetails is an heritage of anther behavior, IContactDetails fields can now be imported too.
[bsuttor]0.3 (2017-04-25)You can now add use_parent_address field.
[bsuttor]0.2 (2017-03-03)Do not add duplicates.
[bsuttor]Fix import with accent in title and add tests.
[bsuttor]0.1 (2017-03-02)Initial release.
[bsuttor]
Package: collective.contact.mailaction
Adds a “Send mail to” action to collective.contact.facetednav which allows you
to send a mail to the selected contacts by using a template for the mail.TranslationsThis product has been translated intoGermanItalianFrenchSlovenianInstallationInstall collective.contact.mailaction by adding it to your buildout:[buildout]

...

eggs =
    collective.contact.mailactionand then runningbin/buildoutContributeIssue Tracker:https://github.com/collective/collective.contact.mailaction/issuesSource Code:https://github.com/collective/collective.contact.mailactionLicenseThe project is licensed under the GPLv2.ContributorsRene Jochum, Webmeisterei GmbHHarald Frießnegger, Webmeisterei GmbHChangelog1.1 (2016-12-17)Add translations for de, it, fr and sl
[fRiSi]Skip contacts w/o email-address and list them in a warning message [fRiSi]1.0 (2016-09-21)Add the Name of the sender to the Reply-To field.
[pcdummy]Parse the input text field as restructured text.
[pcdummy]Use html2text to transfer the html email to text.
[pcdummy]Use only the lastname as sender name if no firstname has been given.
[pcdummy]Make the textfield 20 rows high.
[pcdummy]No need checking for contaclists in mailaction.
[pcdummy]Stonagehtml removed (got troubles with a html template).
[pcdummy]Make the recipient overwriteable over an adapter.
[pcdummy]Correct label the label for the ‘send’ button.
[pcdummy]Depend on ‘collective.contact.facetednav:default’.
[pcdummy]Add german translations.
[pcdummy]Added the mail action based upon contactlist.
[pcdummy]Initial mrbob template.
[pcdummy]
Package: collective.contact.membrane
===========================collective.contact.membrane===========================Integration of dexterity membrane with contacts from collective.contact.core.Contacts are Plone users========================When you install this package, contacts (Person contents) become Plone users.Once they have a password, they can login,using the contact id or the contact email (set the parameter in the control panel)Contact fields are properties of user.When you change some properties on user settings (for instance: email, location)contact entry is updated.Organizations are Plone Groups==============================Organizations and positions becomes Plone Groups.If a person has an held position into the organization or the position,he/she is a member of this group.Tests=====This add-on is tested using Travis CI. The current status of the add-on is :.. image:: https://secure.travis-ci.org/collective/collective.contact.membrane.png:target: http://travis-ci.org/collective/collective.contact.membraneContributors============- Cédric Messiant, cedricmessiant@ecreall.com- Eric Bréhault, ebrehault@gmail.comChangelog=========1.0.2 (2015-04-03)------------------- Add parameter to choose which held position states are used to addpersons to organization group. All positions are used if parameter is not set.[cedricmessiant]- Fix getGroupsForPrincipal so it does not crash if no position[ebrehault]- Do not crash Person membrane behavior if Group membrane behavior is not assigned toorganizations [ebrehault]1.0.1 (2014-09-15)------------------- Change i18n domain in person types xml (collective.contact.core)1.0 (2014-06-18)----------------- Initial release.[cedricmessiant]
Package: collective.contentcreator
=========================collective.contentcreator=========================Create content structures from JSON files or Python dictionaries.This package is meant as a helper to quickly create content structures from JSON files or Python structures for the purpose of pre-filling a site in development.It's the successor of the package `collective.setuphandlertools <https://github.com/collective/collective.setuphandlertools>`_.Examples--------Register a ``post_handler`` in a GenericSetup profile:.. code-block:: xml<genericsetup:registerProfilename="basic_content"title="create basic content structure"directory="profiles/basic_content"description="Creates the basic content structure"provides="Products.GenericSetup.interfaces.EXTENSION"post_handler=".setuphandlers.basic_content"/>In your ``setuphandler.py``:.. code-block:: python# -*- coding: utf-8 -*-from collective.contentcreator import create_item_runnerfrom collective.contentcreator import load_jsonfrom zope.component.hooks import getSitedef basic_content(context):content_structure = load_json('data/basic_content.json', __file__)create_item_runner(getSite(),content_structure,default_lang='en',default_wf_action='publish')And in your ``data/basic_content.json``:.. code-block:: json[{"@type": "Folder","id": "main","title": "Main Folder","items": [{"@type": "Page",   "title": "Page within Folder"},{"@type": "Folder", "title": "Folder within Folder", "description": "Not much more in here."}]}]License-------The project is licensed under the GPLv2.Changelog=========2.0 (2018-12-03)----------------- Use ``plone.restapi`` and base content creator on ``plone.restapi.services.content.add``.This gives us correct value deserialization and schema validation.E.g. text fields are correctly deserialized to ``plone.app.textfield`` values.Breaking Change: The JSON Structure is based on the ``plone.restapi`` JSON structure.TBDSee: https://plonerestapi.readthedocs.io/en/latest/content.html#creating-a-resource-with-post[thet]1.0 (2018-12-01)----------------- Initial release.[thet]
Package: collective.contentgovernance
IntroductionThis is an add-on for Plone to provide some content management metadata
essentials.Even if they are several fields, they complement each other to build a set of
useful features for managing and maintaining websites.Responsible personIt may come as a surprise to some that we don’t have this in Plone already. We
store and index the creator of content (a mostly useless value) and we manage an
owner role on content, a permission rule not indexed for practical use. The
responsible person is the person that owns the content and is responsible for
keeping it updated.Validity dateThe expiry date field in Plone is not very useful and not often used beyond
checkboxes in feature comparisons. This field, the validity date, is more
useful: It is always set when saving an object (like the versioning note) from a
vocabulary of dates in the future (1 week, 1 month, 3 months, 6 months, 1 year
from now). Whenever the object is saved, the date is set in the future.When the date approaches, the responsible person will be notified that his
content is about to expire. It will also be visible in her review lists. For
updating it, all she needs to do is to open the content and save it again,
effectively setting the expiry date some time in the future. If the content does
expire, it will, according to site policy, either be archived/made
unavailable/hidden, or visibly marked as obsolete/unmaintained.Views and actions neededMy contenta screen of content i am responsible for and its status
Perhaps batch operations on it
perhaps batch assign to someone elseNew document bylinethe responsible person, not the creator
alternatively a portlet with a photo and contact details of the responsible persona new ownership form which sets this field along with the owner rolea global change ownership form for when you delete/deactivate users.Changelog1.1 (2011-12-06)Prevent the default value to be set during indexing, to prevent breaking
ZCatalog internal structures.
[mj]ImportantYou’ll need to runhttp://url.to.your/plone-site/@@cleanup-catalog-ghoststo repair a broken ZCatalog after upgrade.1.0 (2011-08-09)Initial release
[ggozad]
Package: collective.contentlicensing
IntroductionThe ContentLicensing tool allows for both a site wide copyright license to be
set by default, and the ablility to set licenses on individual objects.It supports a number of licenses including all rights reserved, GFDL, and
Creative Commons (with an integrated license picker).You can also enter and select licenses not supported by default,
or configure new licenses that will appear in the selection widget for your
Plone instance.Changelog2.2.6Fixed multiple translation errors [blambert555]Updated .pot file [blambert555]Included updated Spanish translation files [blambert555]Included updated Brazilian Porteguese translations [blambert555]2.2.5Modified MANIFEST.in to include docs when creating egg [blambert555]Remove unused and duplicated code [erral]Use toLocalizedTime to get localized dates in cite pop-up [erral]Use Plone’s safe_unicode instead of custom-made method [erral]2.2.4Add missing docs folder to the tar.gz released on pypi [dimo]2.2.3Removed legacy templates that included copyright byline, which
results in duplicate bylines appearing [blambert]Added Basque (eu) translation [erral]2.2.2Allow content editors to select license [dimo]Fix copyright and other licenses [dimo]Don’t show license_other_button1 img if not necessary [dimo]Fix error when copyright holder had unicode chars [clopy]2.2.1 - UnreleasedFix the link “edit the container” when we are editing the default view of a
container (like in Products/Archetypes/skins/archetypes/edit_macros.pt).
[sylvainb]Review french translation [toutpt, kiorky]Added blob support [do3cc]Remove five:traversable already deprecated with Zope2.10 [toutpt]Move IObjectModifiedEvent from zope.app to zope.lifecycleevent [toutpt]Add metadata.xml to default profile [toutpt]Move import step to zcml [toutpt]Update testing buildout to support plone3.3 and plone4.0 as usual [toutpt]2.2.0 - Finalexpress additional metadata fields in rss viewsfix invalid CSS issues2.1.0 - UnreleasedInitial release
Package: collective.contentMapper
IntroductionOverrides collective.tagNavigator and adds a map interface instead of the menuChangelog0.12 (2013-01-17)Fixed a bug when searching on a collection that would ignore tags that are on the collection criteria0.11 (2012-06-26)Now the map image can be customized on custom skin0.10 (2012-05-08)Fixed a scales bug on the markers0.9 (2012-02-01)Small CSS fix on the markers0.8 (2012-01-31)Changed the portlet to search allways on the path given on the portlet configuration.0.7 (2012-01-31)Option for a description on the portlet.0.6 (2012-01-23)Fixed default tooltips and conflicts between markers0.5 (2012-01-21)Small visual bugfixes0.4 (2012-01-21)Added different size markers and cache values for number of search resultsSmall IE fixes0.3 (2012-01-20)Fixing some missing files on the 0.2 egg0.2 (2012-01-20)First version working with the North holland region of the Netherlands0.1dev (unreleased)Initial release
Package: collective.contentmigrationui
Introductionby Giacomo Spettoli<giacomo.spettoli@gmail.com> andRegione Emilia-RomagnaThis product is a user interface for migrate content based on frameworkProducts.contentmigration.The wizard will guide the site administrator with 3 step:select the desired migration from a listselect in which contents apply the migration from a filtered site mapconfirm the migration.This product also provide an easy way to register new migration. In “allmigration” folder you can
find some example.
Here the folderToLargeFolder migration:class FolderToLargePloneFolder(object, ATFolderMigrator):
    """Migrate the old item type to the new item type
    """
    implements(IContentMigrator)

    walker = CustomQueryWalker
    src_meta_type = "ATFolder"
    src_portal_type = "Folder"
    dst_meta_type = "ATBTreeFolder"
    dst_portal_type = "Large Plone Folder"
    description = "Document to Document"
    safeMigration = True

    def __init__(self, *args, **kwargs):
        ATFolderMigrator.__init__(self, *args, **kwargs)
        self.fields_map = BASE_AT_PROPERTIES

FolderToLargePloneFolderMigrator = FolderToLargePloneFolderIn order to create your own migration you must create a class that extend ATFolderMigrator or ATItemMigrator:from Products.contentmigration.archetypes import ATFolderMigrator,ATItemMigratorThis new class must implements IContentMigrator interface:implements(IContentMigrator)Next you insert source and destination portal_type and meta_type (you can find these values in zmi/portal_types):src_meta_type = "ATFolder"
src_portal_type = "Folder"
dst_meta_type = "ATBTreeFolder"
dst_portal_type = "Large Plone Folder"You can set the migration as “safe” or “unsafe”. A “safe” migration is a migration where
the destination content type has equal/more fields than origin content type. You can also insert a warning message in description:safeMigration = True
description = "Document to Document"And than,in the __init__ method you must map source fields in destination fields. Basic archetypes fields are already mapped in BASE_AT_PROPERTIES:self.fields_map = BASE_AT_PROPERTIESAt last insert this line to create a named utility::<class name>Migrator = <class name>In a zcml file register the new utility:<utility
    component=".basemigrations.FolderToLargePloneFolderMigrator"
    provides="..interfaces.IContentMigrator"
    name="collective.contentmigrationui.FolderToLargePloneFolderMigrator"
/>Changelog0.1Initial release