Saravanan666/pypi-org huggingface dataset:
Package: collective.feedback
collective.feedbackFeedback mechanism integration for volto.Users can add vote and a comment to every page on the site.Bot protectionThis product usecollective.honeypotto prevent bot submissions.You just need to set two environment variables:EXTRA_PROTECTED_ACTIONS feedback-addHONEYPOT_FIELD xxxxxx should be a field name that bot should compile.If you get hacked, you could simply change that variable.PermissionsThere are two new specific permission:collective.feedback.ManageFeedbacks (collective.feedback: Manage Feedbacks) Allows to reset data (by default Manager and Site Administrator).collective.feedback.AccessFeedbacks (collective.feedback: Access Feedbacks) Allows users to list feedbacks on contents where they have that permission (by default Editor, Manager and Site Administrator)Feedbacks catalogReviews are stored inside an internal catalog (based onsouper.plone).You can access/edit data through restapi routes (see below) or through a Plone utility:from zope.component import getUtility
from collective.feedback.interfaces import ICollectiveFeedbackStore

tool = getUtility(ICollectiveFeedbackStore)Add a voteMethodaddParameters:data(dictionary with parameters)Response: unique-id of new recorddatashould be a dictionary with the following parameters:uid [required]: the uid of the Plone contentvote [required]: the voteanswer: a custom string, like a commenttitle: the title of the Plone contentcomment: an optional commentOthers parameters will be ignored.Search reviewsMethodsearchParameters:query(dictionary with parameters),sort_index(default=date),reverse(default=False)Response: a list of resultsqueryis a dictionary of indexes where perform the search.Right now data is not indexed so search filters does not work. You only need to call search method to get all data.InstallationInstall collective.feedback by adding it to your buildout:[buildout]

...

eggs =
    collective.feedbackand then runningbin/buildoutContributeIssue Tracker:https://github.com/RedTurtle/collective.feedback/issuesSource Code:https://github.com/RedTurtle/collective.feedbackCompatibilityThis product has been tested on Plone 6AuthorsThis product was developed by RedTurtle Technology team.ContributorsRedTurtle Technology,sviluppoplone@redturtle.itChangelog1.0.0 (2023-02-16)Initial release.
[eikichi18]
Package: collective.feedfiller
FeedfillerContentsFeedfillerWhat is it?DependenciesHow does it work?TODOCREDITSChangelogWhat is it?Feedfilleris intended to work alongside Zest Software’sFeedFeederpackage,
and provide the additional functionality of filling each news feed item
with the clean body content of the page it refers to. Feedfiller can be
educated about structure of content, to help access the most interesting page
elements.
If does not yet ‘know’ the structure of the target page, all it can do is
include the whole page. We will improve this as the project develops.Clearly there are potential copyright issues with the re-publishing of
copyrighted works. But for research and analysis purposes, these may not
be an issue for your organization. Our own purpose is to use collected
text for classification and analysis for internal use. You should
seek your own legal advice on this topic.DependenciesBeautifulSoup, Products.feedfeeder.  If you use the egg package,
these dependencies will be managed for you.How does it work?Feedfiller subscribes to the event created after storage of each news feed
item created by FeedFeeder and fetches the target page of that item. This
means that all items will be be filled with the content of the page they refer
to. Fetched pages are flayed (“Flay: Verb: to strip off the skin or surface
of”) by a Flayer looked up in a FlayerRegistry by URL.Flayers may be easily written to accomodate new pages. Flayers can be
created and registered for different sections of a site, in case HTML
structure varies in sub-trees of the site.If no flayer is registered for the URL, a default flayer is used that
returns the whole body of the page.Currently site-specific flayers try to reveal author, copyright, and body,
but the default flayerThe flayer base-class currently stores the original page fetched from
the server, to facilitate further development and refinemement of flayers
without repeatedly fetching content.TODOThe next step is to develop a table-driven flayer, for which table entries
can be generated interactively by clicking on an enhanced version of the
default flay, a bit like a basic firebug view of the structure of a page
with buttons to manually select the body area of a page. This will
rmoyrequire a new view for this purpose, available to managers.There is no reason why the table-drive flayer should not be able to handle the
complexity of the BBC news page, leaving only the trickiest pages to the
custom class approach used currently.Table items should eventually be replicated across all other feedfiller users,
perhaps using bi-directional rsync using a central repository, or perhaps
using svn.CREDITSThe project was initiated by Russ Ferriday, Topia Systems Ltd, in
November, 2008.Thanks to ‘Business Across Borders’__ for sponsorship of this work.__BusinessAcrossBorders:http://businessacrossborders.com/Thanks to Zest Software and the van Rees brothers for FeedFeeder.Contributions are welcome, and contributors are listed below:Changelog0.1 - UnreleasedInitial release
Package: collective.fgrcon.portletadmin
collective.fgrcon.portletadmin allows to get an overwiew of all portlet assignments within a Plone siteor subtree thereof. Furthermore it offers links for editing, moving or deleting any individual portlet.Please use it at your own risk - backup before usage. It was developed for Plone 5.1.FeaturesThe addon provides a view:@@portlet-adminwhich can be appended to site root or any subfolder of the site.it lists all portlet assignments on all containers within the selected range recursivelyfor each listed container it provides a link to view the container/pagefor each existing portlet manager in the container it lists all assigned portletsfor each portlet listed there is:a link to edit the portlet directlya link to remove (delete) the portletan option to move the portlet assignment to a different portlet manager within the same or a different container.
(when selecting a different target container the available portlet managers will be fetched via an AJAX call.)Examples /DocumentationSee all portlet assignments of the whole site
e.g.:http://Server/Plone/@@portlet-adminSee all portlet assignments in Folder 1 an below onlyMove Collection portlet from right portlets in /Plone/folder1/page1-in-folder-one to left-portlets in
/Plone/folder1 (parent)Virtual HostingThe addon can handle something likehttp://1.2.3.4:8080/Ploneand mapped this (rewritten) ashttp:/example.orgTranslationsThis product is available in English only  - its just an utility not ment for end users.InstallationInstall collective.fgrcon.portletadmin by adding it to your buildout:[buildout]

...

eggs =
    collective.fgrcon.portletadminand then runningbin/buildoutContributeIssue Tracker:https://github.com/collective/collective.fgrcon.portletadmin/issuesSource Code:https://github.com/collective/collective.fgrcon.portletadminDocumentation:https://docs.plone.org/foo/barSupportIf you are having issues, please use the issue trackerLicenseThe project is licensed under the GPLv2.ContributorsFranz Gerhard Reinisch,franz@fgrcon.netChangelog1.2 (2018-04-18)fix VHM path issues
now can handle something likehttp://1.2.3.4:8080/Ploneand mapped (rewritten) ashttp:/example.orghttps://github.com/collective/collective.fgrcon.portletadmin/issues/1[fgrcon]1.0 (2018-04-17)Initial release.
[fgrcon]
Package: collective.fieldedit
collective.fieldeditA view to edit selected fields of a content type.FeaturesUseable by simply calling a view with a the fields you want to edit as query-string-parametersSelect the field or fields you want to editFor each field you can choose between input, display and hiddenUses the same widgets and validators as the default edit-formRespects schema-hints like field-permissions, invariants and widgetsNice to use in modals/popups fo allow editing one ore more fields (but not all)Use it by adding a link to the view@@field_edit_formand pass the fiels you want to edit as a query-string with up to three parameters separated by a “:” for each field.ExamplesEdit the text of a document:http://localhost:8080/Plone/front-page/@@field_edit_form?fields=IRichTextBehavior.textEdit the fields title and subjects:http://localhost:8080/Plone/front-page/@@field_edit_form?fields=IDublinCore.subjects&fields=IDublinCore.titleDisplay the text and edit the publishing date:http://localhost:8080/Plone/front-page/@@field_edit_form?fields=IRichTextBehavior.text:display:0&fields=IRelatedItems.relatedItemsRender a link to edit the title in a modal:<a href="${python:context.absolute_url()}/field_edit_form?fields=IDublinCore.title"
   class="pat-plone-modal"
   data-pat-plone-modal='{"actionOptions": {"reloadWindowOnClose": false, "redirectOnResponse": true, "disableAjaxFormSubmit": true},
                          "buttons": ".formControls > button"'>
    Edit the Title in a modal
</a>Edit multiple fields:<a href="${python:context.absolute_url()}/@@field_edit_form?fields=field1&amp;fields=field2&amp;fields=field3"
    Edit some fields.
</a>Display one field, edit another”<a href="${python:context.absolute_url()}/@@field_edit_form?fields=field1:display&amp;fields=field2"
    Edit one field, display another.
</a>Hide the label:<a href="${python:context.absolute_url()}/@@field_edit_form?fields=field1::0"
    Edit one field, display another.
</a>Add a hidden field:<a href="${python:context.absolute_url()}/@@field_edit_form?fields=field1:hidden&amp;fields=field2"
    Edit one field, display another.
</a>Behavior-fields need to be prefixed with the Behavior:<a href="${python:context.absolute_url()}/@@field_edit_form?fields=IBasic.title"
    Edit one field, display another.
</a>Supported Versionscollective.fieldedit is tested in Plone 5.1, 5.2 and 6.InstallationInstall collective.fieldedit by adding it to your buildout:[buildout]

...

eggs =
    collective.fieldeditand then runningbin/buildoutThen got to the add-on controlpanel (/prefs_install_products_form) to enable it.ContributeIssue Tracker:https://github.com/collective/collective.fieldedit/issuesSource Code:https://github.com/collective/collective.fieldeditLicenseThe project is licensed under the GPLv2.Changelog1.0 (2022-06-25)Additional Markup for Plone 6.0 (Bootstrap 5)
[jensens]Formatted with Black/isort according to Plone standards.
[jensens]Add support for Python 3, Plone 5.2 and 6.
[pbauer]1.0a2 (2018-08-04)Fix redirect and remaining webdav locks on cancel (#1)
[pbauer]1.0a1 (2017-10-10)Initial release.
[pbauer]
Package: collective.filepreviewbehavior
Introductioncollective.filepreviewbehavior contains a behavior for using
Products.ARFilePreview with dexterity content types. The views and some adapters
are overwritten ARFilePreview uses some Archetypes specific stuff.BE WARNED: If you have a dexterity setup, you may not want to install
Archetypes. But Products.ARFilePreview was developed for Archetypes and may
still depend on it.UsageAdd the behaviorcollective.filepreviewbehavior.interfaces.IPreviewableto
the behaviors list of your dexterity conten type, then the uploaded file will be
converted to a HTML preview.Use as name for the file-field “file” and mark it as primary field. The file
field should be in your primary schema interfaces, a behavior schema interface
may not work.For more information about marking as primary field check out the dexterity
documentation (the chapter on webdav):http://plone.org/products/dexterity/documentation/manual/developer-manual/advanced/webdav-and-other-file-representationsThe ViewsProducts.ARFilePreview provides three views:
*file_preview: A view containg the download link and a the preview of the
document embedded in the plone theme.
*preview_provider: A view only containing the preview of the document. This
view can be used as fullscreen / popup preview.
*file_asdoc: A view only containing the preview of the document, but embedded
in the plone theme.You may the make some actions for your content, collective.filepreviewbehavior
will not create any actions.Changelog1.0a1We should not expect the objects to provide the IBasic behavior, but we know
that there is always a Title() and a Description() method (inherited from CMFCore)
[26.11.2009, jbaumann]MissingBinary should not fail, but skip creating the preview and put a error
message into the log.
[06.11.2009, jbaumann]It should not fail if there is no primary field value
[06.11.2009, jbaumann]Added some tests, they are not working well because we test with a plain
type (without any schemata and without a required file field).
[23.10.2009, jbaumann]Added some documentation
[23.10.2009, jbaumann]Initial implementation
[22.10.2009, jbaumann]
Package: collective.filteredlocking
Change default Plone behavior inlocking documentsmanagement: add a new (specific) permission
instead of relying onto the modify permission.IntroductionPlone has a native locking protection given bt theplone.lockingmodule but, as said in the
documentation, users able to modify a document can always steal the lock.How this worksThis add-on adds a new different permission for locking:collective.filteredlocking: Can unlock objects.Users without this permission will be not able to unlock the document until it’s released by the owner or
lock expires.CreditsDeveloped with the support ofRegione Emilia Romagna;
Regione Emilia Romagna supports thePloneGov initiative.AuthorsThis product was developed by RedTurtle Technology team.Changelog2.0.0 (2022-07-15)Python 3 support. Dropped support for Python 2.7 and Plone < 5.2.
[reflab]1.2.0 (2014-05-15)Fix to egg format [keul]Proper package dependencies [keul]Removed useless GS profiles [keul]Do not rewrite the wholeTTWLockablecode, but inherit from Plone default ones [keul]Pyflakes cleanup [keul]Default permission will now replicate default Plone behavior (edit can release locks) [keul]A user can always remove his own lock. This prevent strange behavior where users lockout
others because they don’t have the proper permission [keul]Added support for Site Administrator role [keul]Added tests suite1.1.0 (2013-06-24)z3c.autoinclude1.0.0 - UnreleasedInitial release
Package: collective.fixorderedfolder
plone.foldermaintains a data structure to support ordering.In certain cases, that data structure can get into incoherent state.For instance, there is a possibility that an item sitting in a folder can still
be viewed or edited but not moved or renamed.collective.fixorderedfolderprovides a view (fixOrderedFolders) on Plone sites that walk
through the site folders to fix the case described.Further, it logs discrepancies in the ordering data structure.ContributorsGodefroid Chapelle,gotcha@bubblenet.beChangelog0.1a5 (2018-09-11)Refactor diagnose and fix algorithm.
[gotcha]0.1a4 (2018-05-07)Defend against UnorderedOrdering.
[gotcha]0.1a3 (2018-05-07)plone.apiis required only by tests.
[gotcha]0.1a2 (2018-05-07)Fix broken classifier
[gotcha]0.1a1 (2018-05-07)Initial release.
[gotcha]
Package: collective.flag
Introductioncollective.flagis a simple package that adds an option of marking special
objects in a Plone site — flagging them. An additional field added to theSettingsschemata can be used to differentiate regular documents from the
special ones. Possible use-cases:Put items to the frontpage. Usually not every most recent item should go
to the frontpage, but those having a special meaning;Allow to search for items that are special when building aCollection.TipsRename the field’s titleThere is not easy way of renaming field’s title using a controlpanel or
something like that. What you can do instead — translate the title using
standard mechanisms of Plone.The recommended solution is to override the translation for thelabel_flaggedobject_titlemsgid in thecollective.flagdomain. Read
more about how to do this in Plone 3.x or later here —i18n, locales and
Plone 3.0.Developed byJarn AS—http://www.jarn.comDevelopment sponsored by theBergen Public Library—http://www.nettbiblioteket.noChangelog1.3 - March 4, 2013Support for new-style Collections
[mishunov]1.2 - January 7, 2011Dutch translation
[markvl]1.1 - 2010-06-30Sanitized Norwegian translation.
[elvix]Add empty english file to workaround bug in zope.i18n where fallback
cannot be english if the catalog does not exist.
[gotcha]Various cleanups.
[spliter, hannosch, witsch]1.0 - 2009-09-08Initial release
[spliter]
Package: collective.flattr
Introductioncollective.flattr includeshttp://flattr.com/into Plone. It gives you
a portlet for the entire site, as well as a flattr button (implemented
as viewlet) for Content Types. If you want to, collective.flattr
creates a “thing” on flattr on IObjectInitializedEvent. Then, this
“thing” will be linked to your content automatically.InstallationAdd collective.flattr to eggs of the instance section of your
buildout and run buildoutuse quickinstall to install collective.flattrgo tohttps://flattr.com/appsand register your Plone Sitego tohttp://YOURSITE/@@flattr-controlpaneland follow the
instructions
(or go to Plone Control Panel -> collective.flattr Settings)Known issuesDuring my tests, getting of the access token didn’t work always on the
first try, because Flattr denied the access. But on a second try it
worked.The Compact Counter and Large Counter only works in the productive
environment. In development and/or staging, flattr’s javascript is not
able to map things via url.Changelog0.2 (2012-01-07)Make collective.flattr work in https environments (#911980)0.1 (2011-12-30)Initial release
Package: collective.flexibleordering
Introduction============This product provides a couple IOrdering adpaters to provide efficientauto-sorting of folders with significant amounts of content.It includes a title (``flexible-title-ordering``) and id(``flexible-id-ordering``) ordering, but is intended to allow easycreation of custom sorts.It is easy to create custom ordering implementations by subclassingone of the included implementations and simply overriding the``key_func(obj)`` method which generates a sort key for containedcontent.  Essentially, any ordering can be achieved in this manner.Note: The full data structure containing the folder order key -> idmapping is stored on the folder itself.  This means that folderinstances with a large amount of content may become somewhat large,but that order lookups should be quite fast.Credits-------Alec MitchellJazkarta, Inc.With thanks to:Dumbarton OaksKCRW RadioChangelog=========1.0beta1 (2014-03-08)-------------------- Initial release
Package: collective.flowplayercaptions
Table of contentsIntroductionHow it worksConfigurationDependenciesPlone 3TODOChangelogIntroductionAdd to Plone andcollective.flowplayercaptioning support through the inclusion ofFlowplayer Captions plugin.How it worksAfter the installation of the product you’ll continue the creation new video contents normally,
using the basic collective.flowplayer features.But when you have created a new internal video content (uploading a new File inside Plone with
a compatible video format like.flv) then going back to edit the new video, you will find a
newfieldsetnamed “Subtitles”.If you provide “Captions file” in a compatible format (like.srt) your video will display
captionsConfigurationThe captions pluging offer a great set of configuration options that you can easily change,
thanks to the collective.flowplayer structure.You will find many new entry in theflowplayer_properties, but you can add new ones. Please,
see the “Configuration” section of the “Flash plugin: Captions” given above, but also theDisplay propertiesandStyling propertiesof Flowplayer plugings guide.You are welcome to change default settings if you want cool stuffs like transparency, gradient
and other. This product use a default configuration that look first of all to high video
accessibility.DependenciesDependencies there is a quite long list, but very simple to be satisfied.Flowplayer Flash plugin needed (provided with the product):Flowplayer Captions pluginFlowplayer Contents pluginPlone dependencies:collective.flowplayerPlone 3Plone 3.3is supportedwith some additional dependencies that are automatically satisfied on
Plone 4:archetypes.schemaextenderplone.app.blobQuick note onplone.app.blob. It works perfectly on Plone 3.3 but maybe that your Plone
configuration is not using it yet.Withoutconfiguring plone.app.blobyou will get an error like this:Traceback (innermost last):
  Module ZPublisher.Publish, line 125, in publish
  Module Zope2.App.startup, line 238, in commit
  Module transaction._manager, line 93, in commit
  Module transaction._transaction, line 325, in commit
  Module transaction._transaction, line 424, in _commitResources
  Module ZODB.Connection, line 545, in commit
  Module ZODB.Connection, line 590, in _commit
  Module ZODB.Connection, line 628, in _store_objects
Unsupported: Storing Blobs in <ZODB.FileStorage.FileStorage.FileStorage object at 0x1025ae090> is not supported.NoteYou are welcome to help making this product works also on Plone 3withoutBLOB support.TODOA way to display the SubRip source easily (I wrotecollective.subrip2htmlfor this, then I
saw that it was not really needed for the captioning support…)Supporting subtitles also forCollectioncontent types (I’ve problems with the confuse
Flowplayer APIs)Changelog0.1.0 (2011-01-03)Initial release
Package: collective.flowplayerclipviews
DocumentationAdd to your Plone videos (that usecollective.flowplayeror derivated products), a
“views count” feature.Development stateThis is only a proof of concept, right now heavily based on JavaScript. Malicious users can
hack your clip view counts right now.Do you know that…This product has been developed during a travel from Ferrara to Rome (and back).Changelog0.1.0 (2012-02-25)Initial release
Package: collective.FolderContentsPortletManager
IntroductionPortlet manager for the folder_contents (contents tab). Usefull to add a mass uploader portlet for exampleChangelog0.3 (2014-09-24)Adapted to plone 4.3.3 IColumn interface [andreg]0.2 (2013-05-22)Adapted to plone 4.30.1dev (unreleased)Initial release
Package: collective.folderishpage
collective.folderishpageContentscollective.folderishpageChangelog0.8 (2013-04-09)0.7 (2013-04-09)0.6 (2010-12-29)0.5 (2010-05-27)0.4 (2010-05-07)0.3 (2010-04-08)0.2 (2010-01-14)0.1 (2009-07-08)IntroductionContributorsCode repository:http://svn.plone.org/svn/collective/collective.folderishpageQuestions and comments torob@fourdigits.nlReport bugs atrob@fourdigits.nlChangelog0.8 (2013-04-09)Nothing changed yet.0.7 (2013-04-09)Changed versioning to use Generic Setup since the previous method is removed in
CMFEditions >= 2.1
[robgietema]Addz3c.autoincludeentry point for automatic ZCML loading in Plone 3.3+.
[WouterVH]Removed unsupported <require /> for set_schema on archetype content types. [WouterVH]
Cfr.http://plone.org/products/zopeskel/issues/32.0.6 (2010-12-29)Updated for plone 4.0 [ralphjacobs]PEP8 fixes [ralphjacobs]Imports from plone.app.folder [ralphjacobs]Changed storage of text to attributestorage for CMFDiffTool [ralphjacobs]0.5 (2010-05-27)Added relatedItems to folderishpages [ralphjacobs]Updated metadata.xml info [ralphjacobs]Update history info [ralphjacobs]0.4 (2010-05-07)Make copy of schemas, not use them0.3 (2010-04-08)Allow owner to add folderishpage, same settings as folder/page0.2 (2010-01-14)Fix annotation storage.Fix tinymce.xml0.1 (2009-07-08)Initial releaseIntroductioncollective.folderishpage is a replacement for a default plone page.ContributorsFour Digits, AuthorWouter Vanden Hove, <wouter@wvhconsulting.org>