Saravanan666/pypi-org huggingface dataset:
Package: collective.volto.subfooter
Add-on for Volto to manage a subfooter (right column) forVolto Subfooter.FeaturesControl panel for plone registry to manage subfooter configuration.Restapi view that exposes these settings for VoltoVolto endpointAnonymous users can’t access registry resources by default with plone.restapi (there is a special permission).To avoid enabling registry access to everyone, this package exposes a dedicated restapi route with the infos to draw the menu:@subfooter:> curl -i http://localhost:8080/Plone/@subfooter -H 'Accept: application/json'Control panelYou can edit settings directly from Volto because the control has been registered on Plone and available with plone.restapi.Volto integrationTo use this product in Volto, your Volto project needs to include a new plugin:https://github.com/collective/volto-subfooterTranslationsThis product has been translated intoItalianInstallationInstall collective.volto.subfooter by adding it to your buildout:[buildout]

...

eggs =
    collective.volto.subfooterand then runningbin/buildoutContributeIssue Tracker:https://github.com/collective/collective.volto.subfooter/issuesSource Code:https://github.com/collective/collective.volto.subfooterLicenseThe project is licensed under the GPLv2.AuthorsThis product was developed byRedTurtle Technologyteam.ContributorsRedTurtle Technology,sviluppo@redturtle.itChangelog1.1.0 (2021-10-10)p.a.caching rules for rest api services.
[cekk]1.0.0 (2021-09-20)Initial release.
[cekk]
Package: collective.volto.subsites
This add-on enable a newSubsitecontent-type and provides some utilities for Volto.SubsiteIt’s a basic folderish content with some additional fields:Header textFooter textColorImageThese fields are useful for Volto theme that will draw some components based on these values.Subsitecontents are not searchable.Accessing Subsite data from restapiThere is a new expansion slot in restapi response when getting content data:subsite.This expansion works like the standard ones (workflow, breadcrumbs, etc) and returns some metadata of the
parent Subsite if the requested content is inside a Subsite.Control panelThere is a control panel that allows to set some settings for Subsites:Styles: you can set a predefined list of css classes that will be used in Volto theme to set some custom styles inside the subsite.TranslationsThis product has been translated intoItalianInstallationInstall collective.volto.subsites by adding it to your buildout:[buildout]

...

eggs =
    collective.volto.subsitesand then runningbin/buildoutContributeIssue Tracker:https://github.com/collective/collective.volto.subsites/issuesSource Code:https://github.com/collective/collective.volto.subsitesLicenseThe project is licensed under the GPLv2.AuthorsThis product was developed byRedTurtle Technologyteam.ContributorsRedTurtle Technology,sviluppo@redturtle.itChangelog1.4.0 (2021-10-10)p.a.caching rules for rest api services.
[cekk]1.3.1 (2021-10-02)Add kitconcept.seo behaviour.
[daniele]1.3.0 (2021-10-01)Add subsite_logo field.
[cekk]1.2.2 (2021-06-07)Enable subsites to be translatables.
[cekk]1.2.1 (2021-05-04)Add default value to social links field.
[cekk]1.2.0 (2021-05-04)Add additional field for manage social links in subsite.
[cekk]1.1.0 (2021-04-30)Disable Subsite from searchable contents.
[cekk]1.0.0 (2020-12-15)Initial release.
[cekk]
Package: collective.wasthisuseful
IntroductionThis product adds a viewlet which allows users to rate the usefulness of a
content item.It also registers an Event which can be used in Plone’s Content Rules so that
an e-mail can be sent immediately after a rating has been submitted.FeaturesViewlet (below content) presents a form with the question
“Was this information useful?”:Clicking “Yes” immediately submitsClicking “No” shows a comment field and submit buttonBy default, enabled for “Document” types, others selectable.Can be overridden (enabled and disabled) for all content types.Enables immediate e-mail notification, with the rating value (“Yes” or “No”)
and rating comment (in the case of “No”) as e-mail variables.InstallationTo yourbuildout.cfg, add:eggs =
    ...
    collective.wasthisusefulAfter that, just install via the “Add-on” controlpanel.UsageEnable e-mail notificationCreate a content rule which has “Usefulness rated” as a trigger. As the rule’s
action, select “Send e-mail”. In the e-mail message, you can use${usefulness_comment}and${usefulness_value}as variables (in addition to
the usual${url}and${title}.Select enabled typesThe “WasThisUseful-settings” form enables you to select on which content types
the viewlet is available. You can reach is via the Plone control panel (“Site
setup”) or directly via@@wasthisuseful-settings.Enabling and disabling specific foldersYou can override the “enabled types” behaviour by going to
the “Usefulness ratings” tab. On folderish objects, you can disable rating for
the folderish object and its children.You can even do this for content items that are not in the “enabled types”
list.Whether an object has ratings enabled is decided in the following order:Has the object itself been set to enabled / disabled (using the
“Usefulness ratings” tab)? If so, use that setting.Has the object’s direct parent been set to enabled / disabled (using the
“Usefulness ratings” tab)? If so, use that setting.Is the object of a type that has been enabled on the
“WasThisUseful-settings” controlpanel?To doEvent IUsefulnessEvent seems only to be fired for non-folderish itemsShow warning when viewing settings of item that is default view (like Topicaggregatorin News Folder).Show number of ratingsIntegrate withcollective.contentratingsTranslate rating value (“Yes”/”No”) in content rule e-mailChangelog1.0 (2012-06-13)Stable release0.3 (unreleased)Depend on plone.app.registry in setup.pyOnly show wasthisuseful viewlet in views marked with IViewViewAdded Dutch translationMinor template/css changes in add this viewlet0.2 (2011-11-15)Add permissionwasthisuseful: Manage ratingsfor controlpanelAllow to disable ratings for folders (and the children in them)Make settings on folder take precedende over enabled types0.1dvldev (2011-11-04)Initial release
Package: collective.webhook
A Plone content rule action for executing HTTP GET or POST with interpolated JSON payload on content event.FeaturesCan be used to trigger webhooks from Plone content rules.Outgoing request are pooled through Plone instance local worker thread throttled by one request / second.ExamplesCan be used to trigger CI webhook for building GatsbyJS site from Plone after each time content is being modified.InstallationInstall collective.webhook by adding it to your buildout:[buildout]

...

eggs =
    collective.webhookand then runningbin/buildoutContributeIssue Tracker:https://github.com/collective/collective.webhook/issuesSource Code:https://github.com/collective/collective.webhookLicenseThe project is licensed under the GPLv2.ContributorsAsko Soukka,asko.soukka@iki.fiChangelog0.3.0 (2018-12-05)Add buildout for Plone 4.3
[Asko Soukka]0.2.1 (2018-06-04)Fix typo in vocabulary value title
[Asko Soukka]0.2 (2018-06-04)Add dedicated method POST FORM for HTTP POST with Content-Type:
application/x-www-form-urlencoded
[datakurre]0.1 (2018-05-27)Initial release.
[datakurre]
Package: collective.weightedportlets
IntroductionThe Plone portlets system gives site managers a powerful system for assigning
portlets to different sections, content types, and groups.  However, there is a
predefined order in which portlets coming from these sources are displayed. So
there is no built-in way to, for instance, specify that one contextual portlet
should appear above any inherited portlets and another one should appear below
them.This product addresses that limitation by adding to each portlet assignment a
“weight” field on the portlet management pages, where an integer can be
specified (it defaults to 50). The full list of portlets will be retrieved in
their standard order; then a final sort based on the weight will be applied
before the portlets are displayed.  Portlets with a lower weight will be sorted
to the top, while portlets with a higher weight will be sorted to the bottom.So, for example, if I wanted to display one contextual portlet above all
inherited portlets and one contextual portlet below all inherited portlets,
I could set their weights to 40 and 60 respectively.Note that adjustments to the portlet order are saved via an AJAX request; you
don’t have to press a button and reload the page to save the new weights.Import and export of portlet assignment weights via GenericSetup is also
supported.InstallationAdd the collective.weightedportlets egg to your buildout.  If using Plone
3.1 or 3.2, make sure you add its ZCML as well.  The ZCML should be
loaded automatically in Plone >= 3.3.Start Zope and install “Weighted Portlet Ordering” via the Add/Remove Products
panel in Site Setup.CompatibilityThis product requires Plone 3.1 or greater.This product operates by overriding the following parts of the portlet
machinery.  You may run into problems if using other products or custom
code that also overrides these components:the template macros used to render the portlet management UIthe IPortletRetriever adapterthe IPortletAssignmentExportImportHandler adapterSelf-certification[X] Internationalized[X] Unit tests[X] End-user documentation[X] Internal documentation (documentation, interfaces, etc.)[X] Existed and maintained for at least 6 months[X] Installs and uninstalls cleanly[X] Code structure follows best practice[X] No side effects on Plone sites where not installedCreditsDavid Glick [davisagli]Thanks to Martin Aspeli for the Plone 3 portlet system.Change history1.2 (2017-09-05)Support plone.portlets 2.3
[montypie]1.1 (2013-10-16)Submit changes to portlet weights using jQuery rather than KSS.This makes the addon compatible with Plone 4.3.You must run the upgrade step to install the javascript.[AdCastle, davisagli]1.0 (2009-10-12)Override the portlet edit macros in a way that is more compatible with
ongoing changes in the base template from plone.app.portlets.
[davisagli]1.0rc2 (2009-05-04)Add version.txt so the version shows correctly in Plone <3.3.
[davisagli]Fixed last-minute typo that made it into the edit macros.
[davisagli]1.0rc1 (2009-05-01)Initial release.
[davisagli]
Package: collective.wfadaptations
This package allows you to create adaptations for your workflows. To add a workflow adaptation, simply add an utility that implementsIWorkflowAdaptation. See example inexample.pyfile.ContributorsCédric Messiant,cedricmessiant@ecreall.comChangelog1.2 (2022-10-28)Addednameparameter onapply_from_registryto apply given adaptation.
[sgeulette]1.1 (2021-04-20)Added reapply adaptation parameter to differentiate a reapply after a workflow reset.
[sgeulette]Kept keys as unicode inget_applied_adaptations[sgeulette]1.0 (2020-10-07)Added multiplicity adaptation parameter to authorize an adaptation to be applied multiple times.
[sgeulette]0.2 (2019-09-20)Set default value to None.
[sgeulette]0.1 (2017-05-31)Add base class for workflow adaptation.
[sgeulette]Initial release.
[cedricmessiant]
Package: collective.wfautodoc
Automatic Workflow DocumentationGenerates aGraphvizfile (or directly creates an SVG) from a Zope/CMF DCWorkflow defintion.Usage:in ZMI got to the workflow which you want to document.there are two additional tabs one for raw DOT data file, one for a rendered SVG file.Features:generation of Graphviz file with states and transitions.each state shows a permissions-tableeach transition shows its guards.Todo:add views to control_panelInstallationJust depend in your buildout on the eggcollective.wfautodoc.
When used within Plone ZCML is loaded automagically with`z3c.autoinclude`.
Otherwise add the package to buildout section`instance``zcml`variable.This package is written for Plone but works also in a pure  Zope2/CMF environment.Source Code and ContributionsIf you want to help with the development (improvement, update, bug-fixing, …) ofcollective.wfautodocthis is a great idea!The code is located in thegithub collective.You can clone it orget access to the github-collectiveand work directly on the project.Maintainer is Jens Klein and the BlueDynamics Alliance developer team.
We appreciate any contribution and if a release is needed to be done on PyPI, please just contact one of usdev@bluedynamics dot comContributorsJens W. Klein <jens@bluedynamics.com>History1.2.0 (2021-07-07)Some code-style and make it work with Python 3/ Zope 4.
[jensens]Fix bug with special characters in review states.
[cedricmessiant]1.1not zipsafe, removes superfluos generic setup references.
thx to SyZn for contribution.
[jensens, 2013-12-03]1.0make it work [jensens, 2012-03-01]
Package: collective.wfcomment
IntroductionThis package installs a JavaScript handler (using jQuery) that will present
a prompt box inviting the user to enter a comment before triggering a workflow
transition from the ‘state’ drop-down in a standard Plone site.The handler will only be used for workflow actions using the standardcontent_status_modifyscript.You can restrict this behaviour on some transitions through a control panel.You can make the comment required or not.ScreenshotIf enabled, you’ll see a popup as shown below when initiating a workflow
transition.RequirementsPlone 4.0+ (tested under Plone 4.0, 4.1, 4.2 and 4.3).Tested with ie6, ie7, ff3, ff4, chrome.LanguagesEnglishFrenchGermanCreditsMartin Aspeli, release 1.0Vincent Fretin and Thomas Desvenain, release 2.0Daniel Widerin  [saily]Changelog2.1.5 (2013-05-31)Split up robottests intokeywords.robotwhich is reusable in your
tests, by adding:*** Settings ***
Resource    plone/app/robotframework/selenium.robot
Resource    plone/app/robotframework/keywords.robot
Resource    collective/wfcomment/tests/robot/keywords.robot
...[saily]Use id or name selectors to makekeywords.robotmore generic and
reuseable for any languages.
[saily]2.1.4 (2013-05-17)Add a new test and remove unneeded ones.
[saily]Add support for dexterity content types.
[saily]Update permissions for comment view and javascript viewlet.
[saily]2.1.3 (2013-05-16)Add tests using robotframework, travis integration and .
[saily]Add german translations and add anupdate_translationsscript to be
generated through buildout.  [saily]‘form.buttons.cancel’ inprepOverlaycloseselector has to be in quotes
to avoid unrecognized expression javascript errors.  [saily]Set correct javascript filter forprepOverlay.
[saily]Move from svn to collective, merge tdesvenain’s remote repo into collective.
Please maintain in collective in future.  [saily]Restructure buildout for Plone 4.3 and Plone 4.2.
[saily]2.1.2 (2013-04-18)Really removed kss dependency (unused imports)
[cedricmessiant]2.1.1 (2012-07-29)Full jquery: kss behaviours entirely replaced.
Fixes under 4.1.x
[thomasdesvenain]2.0.2 (2011-05-02)controlpanel: hide transition selection if ‘all transitions’ option is selected.
[thomasdesvenain]fix when ‘all transitions’ option is selected.
[thomasdesvenain]fix plone.app.registry dependency
[toutpt]2.0.1 (2011-05-02)Fixed profile.2.0 (2011-04-28)Complete rewrite:uses ajax internationalized form,allows to select a list of transitions,kss compliant.[vincentfretin, thomasdesvenain]1.0b2 - 2009-08-31Fix ‘undefined’ error in IE.1.0b1 - 2009-03-19Initial release
Package: collective.wfform
Introduction============collective.wfform gives a developer the ability to present a z3c.formduring a workflow transition.To implement this for a transition in a particular workflow,change the transition url from:%(content_url)s/content_status_modify?workflow_action=submitto:%(content_url)s/workflow_transition_form?workflow_action=submitThis will give you a jQuery popup form with a comments field.To add your own fields, add a method to your content type whichreturns a z3c schema based on the transition.security.declareProtected(permissions.ModifyPortalContent, 'getSchemaForTransition')def getSchemaForTransition(self, transition):"""Return a fieldset depending on the transition"""if transition == 'my_transition':return IMyTransitionFormIMyTransitionForm should be a standard interface class with a zope3 schema.To process the data from the form, add another method onto your class to manage this.security.declareProtected(permissions.ModifyPortalContent, 'processTransitionForm')def processTransitionForm(self, data):"""Return a fieldset depending on the transition"""if data.has_key('my_field'):self.setMyField(data['my_field'])collective.wfform Installation------------------------------To install collective.wfform into the global Python environment (or a workingenv),using a traditional Zope 2 instance, you can do this:* When you're reading this you have probably already run``easy_install collective.wfform``. Find out how to install setuptools(and EasyInstall) here:http://peak.telecommunity.com/DevCenter/EasyInstall* If you are using Zope 2.9 (not 2.10), get `pythonproducts`_ and install itvia::python setup.py install --home /path/to/instanceinto your Zope instance.* Create a file called ``collective.wfform-configure.zcml`` in the``/path/to/instance/etc/package-includes`` directory.  The fileshould only contain this::<include package="collective.wfform" />.. _pythonproducts: http://plone.org/products/pythonproductsAlternatively, if you are using zc.buildout and the plone.recipe.zope2instancerecipe to manage your project, you can do this:* Add ``collective.wfform`` to the list of eggs to install, e.g.:[buildout]...eggs =...collective.wfform* Tell the plone.recipe.zope2instance recipe to install a ZCML slug:[instance]recipe = plone.recipe.zope2instance...zcml =collective.wfform* Re-run buildout, e.g. with:$ ./bin/buildoutYou can skip the ZCML slug if you are going to explicitly include the packagefrom another package's configure.zcml file.Changelog=========1.0dev (unreleased)-------------------- Initial release
Package: collective.workflowed
Introduction============A graphical workflow editor for PloneChangelog=========(name of developer listed in brackets)collective.workflowed - 1.1 (2008-10-16)----------------------------------------- Moved the 'Workflow Editor' control panel into the 'Add-on' section.[claytron]- Removed the overrides of the base style sheets since that is not necessaryfor this product.[claytron]- Fixed the GenericSetup profile so that it doesn't force people to usethe 'Plone Default' skin.[claytron]- Fixed up the reStructuredText in the docs[claytron]collective.workflowed - 1.0 (2008-07-25)---------------------------- Initial release to cheese shop[cguardia]collective.workflowed - 0.8 Unreleased--------------------------------------- Initial package structure.[zopeskel]
Package: collective.wowcharacter
ContentsChange history0.1 (09-03-10)0.2 (09-03-10)0.3 (09-06-10)0.4 (09-10-10)0.5 (09-16-10)Detailed Documentationwowcharacter@@wowhcaracterrealmstatusContributorsDownloadChange historyChangelog0.1 (09-03-10)Initial release0.2 (09-03-10)Fixed a typo in wowcharacter.cssUpdated the wowrealmstatus images0.3 (09-06-10)Added generic deDE i18n (locales/de/LC_MESSAGES/collective.wowcharacter.po)0.4 (09-10-10)(armory_api.py) Modified armory-API to fetch additional info (arenateams, glyphs, secondary professions)(wowcharacter.py) Added char_arena_teams(), char_glyphs(), char_secondary_professions(), char_activity() and char_activity_feed()(wowcharater.pt) Display additional info from the APIs, added numerated headings(wowcharacter.css) Added opacity to equip-icons (standard: 0.3, hover: 1.0)Updated deDE i18nAdded activity-API to fetch recent activities of the character from the armoryAdded unittest for activity-API (tests/test_activity.py)0.5 (09-16-10)Fixed a typo in the unittest(wowcharacter.py) Added armory_error(), returns false if the API gets no data (due to misspelling name/server and/or unavailability of
the armory)(wowcharacter.pt) Added a condition using armory_error() (aka Exception Handling)(armory_api.py, activity_api.py) Modified, if plonesitelanguage=en -> en_GB XML, if plonesitelanguage=de -> de_DE XML for better i18nUpdated armory_api, activity_api and realmstatus_api to newest versionUpdated testsDetailed DocumentationIntroductionThe package is meant to be used with the Plone3 theme collective.wowlichking,
but it is not required.Best viewed with Mozilla Firefox.It includes a custom contenttype (wowcharacter), a custom view (@@wowcharacter) and a custom portlet (realmstatus).wowcharacterThe contenttype represents a World of Warcraft character.
When creating one, you need to state the Name and Realm of the character,
also its faction (Horde/Alliance) and its zone (EU/US).@@wowhcaracterThe view uses two APIs to communicate with the WoW-Armory to display additional
information about the character, like class, guild, talent specs, professions, equip, recent activities etc.
It also implements the wowhead-Tooltip for showing a WoW-ingame-like tooltip when hovering
over the equip-icons.realmstatusThe portlet uses an API to fetch the realmstatus-xml from wow-europe.com to display the status of the realm
of the actual character.  It also displays the name and the type of the realm.ContributorsMarc Goetz, AuthorDownload
Package: collective.wowlichking
ContentsChange history0.1 (09-03-10)0.2 (09-03-10)0.3 (09-03-10)0.4 (09-06-10)0.5 (09-10-10)Detailed DocumentationContributorsDownloadChange historyChangelog0.1 (09-03-10)Initial release0.2 (09-03-10)Removed whitespace from code WoW Lich King -> WoWLichKing as this broke the code0.3 (09-03-10)Modified footer, added animated “banner” with jQuery and spritely0.4 (09-06-10)Using plone built-in jQuery instead of an extern one
-> deleted ++resource++collective.wowlichking.scripts/jquery-1.3.2.min.jsMoved css from footer-template to main.css0.5 (09-10-10)(footer.pt) added controls (start stop slow fast etc.) to footer-bannerDetailed DocumentationIntroductionA World of Warcraft Plone3 theme based on reteeps wordpress theme “WoW Lich King”.Best viewed with Mozilla Firefox.ContributorsMarc Goetz, AuthorDownload
Package: collective.wpadmin
IntroductionWhen dealing with blog, people are used to Wordpress.
This addon provide management screens for Plone to help people
from wordpress to use administrate their website.Let’s start with /wp-adminHow to installYou can install this addon as any other Plone addons. Please follow the
officaldocumentation.This addon do not has setup for Plone. You can just add it to the buildout
and hit /wp-admin where you want.If you are looking for further integration you should check the addoncirb.blog <https://github.com/CIRB/cirb.blog>FeaturesDashboard pageThis page display many widgets that let you see what’s up in your blog.summarytotal number of published blog poststotal number of commentslast draftsquickpressYou can add a news item very quickly (title, body, tags and image)add boxBig blue button to add a new news item (using the Plone add form) plus a
quickupload form to upload images to media folder.draftthis widget give you a direct access into Plone to your current blog posts into
draft state.recent commentthis widget give you a direct access into Plone to last commentUpload pageThis page let you browse the media folder and manage existing content. You
can rename, delete or modify any image from this page without going to Plone.Blogs pageThis page let you browse current blog posts and manage them. You can rename,
delete any posts from this page without going to Plone. You also has a direct
access to the Plone edit form.CreditsCompaniesCIRB / CIBGContact CIRBPlanet Makina CorpusContact Makina CorpusPeopleJeanMichel FRANCOIS aka toutpt <toutpt@gmail.com>Changelog1.0a3 (2013-01-17)fix quick press’s create_post: respect blog_type settingsfix draft widget: respect blog_type settings1.0a2 (2013-01-17)remove collective.googleanalytics dependency1.0a1 (2013-01-16)Initial release
Package: collective.wysiwyg_biografy
IntroductionSimple product for Plone. It change the userBiografyfield to use the current
WYSIWYG editor.CreditsDeveloped with the support ofS. Anna Hospital, Ferrara;
S. Anna Hospital supports thePloneGov initiative.AuthorsThis product was developed by RedTurtle Technology team.Changelog0.2.1 (2014-10-28)Fix Plone 4.3 compatibility in @@user-information [cekk]0.2.0 (2014-07-10)Dropped Plone 3.3 compatibilityPlone 4.3 supported [keul]0.1.0 (2012-02-21)Initial release