Saravanan666/pypi-org huggingface dataset:
Package: collective.restrictportlets
This packages allows you to restrict the available portlets that non-Managers can add.FeaturesOn any page where portlets can be added, the product checks a list of portlets that are restricted to only Managers.
This includes the personal dashboard.There is a control panel for selecting which portlets to disallow for non-Managers.CompatibilityThis package is tested on Plone 4.3 and 5.0.It should be fine for Plone 4.1 and 4.2 as well:It patches a method fromplone.portletsthat has not changed since version 2.0 (Plone 4.0).We needplone.app.registryfor our setting and the control panel, so this means Plone 4.1.The most important part of this package is a smallmonkey patchforplone.portlets.manager.PortletManager.getAddablePortletTypes.
If you have other code that patches this, it may not work.TestingThis package is tested with Travis:DefaultAfter you install the product in the Plone add-ons control panel, by default these portlets are restricted:Classic portletLogin portletYou can make them available again in theRestrict portletscontrol panel.TranslationsThis product has been translated into:Dutch (Maurits van Rees)InstallationInstall collective.restrictportlets by adding it to your buildout:[buildout]

...

eggs =
    collective.restrictportletsand then runningbin/buildout.
Now you can activate it in the add-ons control panel and configure it in theRestrict portletscontrol panel.ContributeIssue Tracker:https://github.com/collective/collective.restrictportlets/issuesSource Code:https://github.com/collective/collective.restrictportletsLicenseThe project is licensed under the GPLv2.SponsorshipWork on collective.restrictportlets has been made possible by The Flemish Environment Agency, or VMM.
Seehttps://www.vmm.be.
VMM operates as an agency of the Flemish government for a better environment in Flanders.
Flanders is one of the three Belgian regions with its own government, parliament and administration.
The other two are the Brussels-Capital Region and the Walloon Region.ContributorsMaurits van Rees,m.van.rees@zestsoftware.nlChangelog1.0.0 (2021-12-21)Test on Plone 4.3, 5.1, 5.2, 6.0.  [maurits]Switch to tox and GitHub Actions.  [maurits]Get rid of includeDependencies.  [maurits]1.0a1 (2017-08-14)Initial release.
[maurits]
Package: collective.resume
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.resume by adding it to your buildout:[buildout]

...

eggs =
    collective.resumeand then runningbin/buildoutContributeIssue Tracker:https://github.com/collective/collective.resume/issuesSource Code:https://github.com/collective/collective.resumeDocumentation: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.
[]
Package: collective.rip
Formerly collective.controlpanel.edit_cssIntroductioncollective.rip: (r)esources (i)n (p)lone is for quick and dirty UI prototyping. Install this add-on to edit CSS and JavaScript from within the Plone control panel. You may also toggle CSS and JavaScript debug modes.InstallationTo install:Addcollective.ripto your buildoutplone.recipe.zope2instancesection’s eggs parameter:[plone]
recipe = plone.recipe.zope2instance
...
eggs =
    ...
    collective.ripRunBuildoutand restartPlone.Browse toSite Setup->Add-ons->Availableadd-ons.CheckResources in Ploneand clickActivate.Have fun!Questions/comments/concerns? E-mail:aclark@aclark.net
Package: collective.rolereport
IntroductionThis module can generate a report on all roles and all users for each role.
It generates an HTML report with userid, fullname and email.Go tohttp://<plonesite>/@@role-reportDO NOT GIVE THAT URL TO AN END USER!The report will be generated to the file system. This is because on the site
where this is being used, the report runs longer than the Apache timeout.
It also tends to block a lot of the site, so it becomes unusable.Tested with Plone 3. Should work in Plone 4.Changelog1.1 (2014-06-19)Now saves the report to disk.1.0 (2014-06-19)Initial release
Package: collective.rooter
IntroductionThis package adds a patch to Plone to ensure that call catalog queries are
‘rooted’ to the current navigation root (as defined by the INavigationRoot
interface). When installed, all catalog queries will have an implicitpathparameter that limits search results to within the current navigation root,
unless apathorUIDparameter is explicitly provided. This avoids
“leakage” of search results, portlet listings and the like. If aUIDparameter is present, known content can be explicitly searched.In this context, the navigation root must be:A folderish objectThat provides the INavigationRoot marker interfaceAnd is a “component site” in the Zope 3 Component Architecture senseThe ‘collective.lineage’ product provides a user friendly way to create such
types.The navigation root will be kept as a thread local variable, in the same way
that the component site is accessible via the globalgetSite()function.
To get hold of the current traversed-over navigation root, you can use:from collective.rooter import getNavigationRoot

current_root = getNavigationRoot()The root may be None if no INavigationRoot has been traversed over.Changelog1.0 (2015-07-15)IfUIDis given in the catalog search keywords, don’t apply the
INavigationRoot path. This allows for explicit queries for known objects in
other areas of the portal. Obsoletes pull-request #1.
[thet]PEP 8.
[thet]1.0b1 (2009-03-29)Initial release.
[optilude]
Package: collective.roster
Personnel Rostercollective.rosteraka Personnel Roster provides highly customizable
personnel listing, which can be extended easily with custom file system
developed add-ons.Adding a new rosterAdding a new personAlphabetical listingGroups listingGallery listingPerson viewPerson viewlets managerAvailable behaviorsChangelog2.3.1 (2017-12-18)Fix groups behavior to not acquire person groups from roster when dexterity
implicit attribute lookup is disabled and groups attribute is missing
[datakurre]2.3.0 (2017-10-27)Change english translation for subject from studysubject to subject
[Grrandi]2.2.1 (2017-10-03)Fixed SimpleTerm creation.
[iham]2.2.0 (2017-04-04)Add option for groups behavior to mark person a groups leader and sort
leaders before others in grouped views
[datakurre]2.1.4 (2017-04-04)Fix issue where group links on gallery depended on current URL and might have
been broken
[datakurre]2.1.3 (2017-03-29)Fix to require plone.app.registry>=1.2.5 [fixes #6]
[datakurre]2.1.2 (2017-01-12)Fix issue where groups adapter returned None
[datakurre]2.1.1 (2017-01-11)Fix biography to be primary field
[datakurre]2.1.0 (2016-12-19)Make roster views aware of possibly enabled RichText-behavior
[datakurre]2.0.3 (2016-12-16)Fix issue where group anchors on groups_view were broken
[datakurre]2.0.2 (2016-12-07)Fix alphabetical listing to sort using locale aware sortable title
[datakurre]2.0.1 (2016-11-08)Fix issue where empty value for JS bundle broke Plone bundle merge
on a new site
[datakurre]2.0.0 (2016-11-04)Allow short number to be anything between 100 and 9999
[datakurre]Plone 5 compatibility: Optionally importcheckEmailAddressandEmailAddressInvalidfrom CMFPlone respectively CMFDefault.
[thet]Add file type checking for person portrait image
[Grrandi, datakurre]Change studysubject behavior label from ‘Studysubject’ to ‘Subject’
[Grrandi, datakurre]Refactored grokless public release.
[datakurre]
Package: collective.roundabout
IntroductionThis product lets you add 360 degree panoramic photos to your website by tagging
your image in the WYSIWYG editor (TinyMCE and Kupu supported). The image will be
tagged with the “roundabout” class which is converted into a viewer using
jQuery when the page is displayed. The viewer is javascript only, so plugins
like flash are not needed.This product also has a couple of contenttypes which you can use to create a
virtual tour of multiple panoramic photos. This tour includes one (or more)
overview maps and a compass at the current location.HISTORY0.3.1 (2009-07-06)Fixed initialization0.3 (2008-12-23)Added start image optionAdded start angle optionAdded image transitionsAdded number of animation frames optionFixed bug with selectionFixed IE bugsMoved all config data to JSONAll data storing at elements now using the data method of jquery0.2 (2008-12-18)Added contenttypes (tour, image, map, imagehotspot, maphotspot)Added tour viewAdded hotspots on image and mapAdded compass on mapAdded viewer size config options0.1 (2008-12-14)Added basic support to convert images with a “roundabout” class to a 360
degree panoramic image viewerAdded support for TinyMCEAdded support for Kupu
Package: collective.rtvideo.mediacore
This is an add-on forRedTurtle Videoproduct for Plone. Additional documentation can be found in the main product’s page.Add this to your Plone installation for beeing able to useMediaCorevideo link as valid URLs for “Video link” content type.In order to serve content from Mediacore you need to configure an adapter and specify the domain name.
Is possible to add an adapter to your application in many way:directly to the buildout section on a .cfg file (example below):within a configure.zcml in collective.rtvideo.mediacorewithin an other package which implements redturtle.video.interfaces.IRTRemoteVideo[instance]
...
eggs =
    collective.rtvideo.mediacore
    ...

zcml-additional =
    <configure xmlns="http://namespaces.zope.org/zope">
        <adapter for = "redturtle.video.interfaces.IRTRemoteVideo zope.publisher.interfaces.browser.IHTTPRequest"
            provides = "collective.rtvideo.mediacore.videoembedcode.IMediaCoreEmbedCode"
            factory = "collective.rtvideo.mediacore.videoembedcode.JWPlayerEmbedCode"
            name= "your.domain"/>
    </configure>NoteThis plugin alone is not enougth.
Mediacore must provides a view to serve some information about media as JSON.
Seemediacore.mediainfopackage for more details.
Package: collective.rtvideo.metacafe
IntroductionThis is an add-on adapter forRedTurtle Videoproduct for Plone. For additional documentation see
the main product’s page.Add this to your Plone installation for beeing able to useMetacafevideo link as valid
URLs for “Video link” content type.Changelog0.1.0 (2011-08-31)Initial release (moved out fromredturtle.video)
Package: collective.rtvideo.vimeo
IntroductionThis is an add-on adapter forRedTurtle Videoproduct for Plone. For additional documentation see
the main product’s page.Add this to your Plone installation for beeing able to useVimeovideo link as valid
URLs for “Video link” content type.AutoplayYou can enabled the Vimeo video autoplay in two ways:Use the YouTubeautoplay=1parameter in the video URL
you are saving in Plone.This is a permanent autoplay: the editor choose to autoplay the video at every visitCall the RedTurtle video content with theautoplay=1parameter.This is a user choice autoplay: who links the Plone content choose to auto
start it.Changelog0.2.0 (2014-12-01)Switched to new embed mode (usingiframe)
[keul]Video provided in https
[keul]Plone 4.3 compatibility
[keul]Autoplay feature added
[keul]0.1.0 (2011-08-31)Initial release (moved out fromredturtle.video)
Package: collective.rtvideo.youtube
IntroductionThis is an add-on adapter forRedTurtle Videoproduct for Plone. For additional documentation see
the main product’s page.Add this to your Plone installation for beeing able to useYouTubevideo link as valid
URLs for “Video link” content type.Valid URL formatsClassic URL is supported:http://www.youtube.com/watch?v=f7OLg1AZvr4&...otherparamsAlso the shortened version can be used:http://youtu.be/f7OLg1AZvr4AutoplayYou can enabled the YouTube video autoplay in two ways:Use the YouTubeautoplay=1parameter in the YouTube video URL
you are saving in Plone.This is a permanent autoplay: the editor choose to autoplay the video at every visitCall the RedTurtle video content with theautoplay=1parameter.This is a user choice autoplay: who links the Plone content choose to auto
start it.In the latter case, some accessibility improvements are added to the page for automatically
put the focus onto the video and simplify keyboard controls (this works on Internet Explorer
and Firefox, probably other browsers also but there isn’t a common behavior).CreditsDeveloped with the support of:Rete Civica Mo-Net - Comune di ModenaRegione Emilia RomagnaAll of them supports thePloneGov initiative.AuthorsThis product was developed by RedTurtle Technology team.Changelog0.3.1 (2014-12-01)Always load the https version of resources URL
[keul]Fixed non-XHTML usage ofallowfullscreenattribute
[keul]0.3.0 (2014-07-21)Added a video object id (for usability reason)
[keul]If the YouTube URL contains theautoplay=1parameter
or if the RedTurtle video contents is called with the same
param, autoplay on video will be enabled
[keul]If the request url use autoplay, some accessibility/usability
improvements are added to the page, for simply keyboard controls
[keul]Removed the secondary template, just use one template for standard
and shortened embedding
[keul]Fixed Python import for Plone 4.3 (same problem of ticket#14)
[bhenker, keul]Replaced object tag with iframe [cekk]0.2.0 (2012-09-04)Fixed egg dependency only toredturtle.video[keul]add getThumb method to return a default thumbnail image to redturtle.video on
IRemoteVideo creation. This is a new feature of redturtle.video 0.8 and up.
[lucabel]Add a new div around object tag in video template, new param and transparency.
So you can be able to set correctly a z-index on this div and solve overlap
problem with other elements on Internet Explorer.
[lucabel]0.1.0 (2011-05-12)Initial release (moved out fromredturtle.video)Support newyoutu.beURLs
Package: collective.ruleactions.pythonscript
collective.ruleactions.pythonscriptOverviewChangelog0.1 (2015-01-05)AddMANIFEST.in.
[WouterVH]Addedz3c.autoinclude-entrypoint to mark this as a Plone-plugin.
This avoids the need to explicitly load the zcml-slug.
[WouterVH]Initial implementation.
[fschulze]Initial package structure.
[zopeskel]ContributorsFlorian Schulze <florian.schulze@gmx.net>Wouter Vanden Hove <wouter.vanden.hove@gmail.com>
Package: collective.saconnect
IntroductionThis package provides a simple control panel and storage forSQLAlchemyconnection strings.
It presents a form where one can add and remove named connections, and a GS import and export step to manage these.This package doesnotprovide SQLAlchemy integration itself;
use a library likezope.sqlalchemy,collective.leadorpas.plugins.sqlalchemyinstead.Example usage:from zope.app.component.hooks import getSite
from collective.saconnect.interfaces import ISQLAlchemyConnectionStrings

saconnect = ISQLAlchemyConnectionStrings(getSite())
myconnection = saconnect['myidentifier']ISQLAlchemyConnectionStringsacts as a simple dictionary, although it’s keys and values must be simple strings.To import connection strings through GenericSetup, simply include a file named saconnections.xml in your profile, with a top-level ‘connections’  element and one ‘connection’ element per connection, with name and string attributes:<?xml version="1.0"?>
<connections>
 <connection name="bar" string="sqlite:////path/to/bar.sqlite"/>
 <connection name="foo" string="oracle://username:password/tnsnamethere"/>
</connections>To remove any of the connections, use the ‘remove’ attribute:<?xml version="1.0"?>
<connections>
  <connection name="bar" remove=""/>
</connections>If you cache your SQLAlchemy connections, you may want to listen for the IObjectModifiedEvent for ISQLAlchemyConnectionStrings.
The event includes the key of the modified string, so you can easily refresh your database connections:<subscriber
    handler=".mymodule.saconnectionUpdated"
    for="collective.saconnect.interfaces.ISQLAlchemyConnectionStrings
         zope.lifecycleevent.interfaces.IObjectModifiedEvent"
/>def saconnectionUpdated(connections, event):
    if 'myconnectionstring' in event.descriptions:
        getUtility(IDatabase, u'myconnection').invalidate()ContributeIf you are having issues, please let us know.Issue Tracker:https://github.com/collective/collective.saconnect/issuesSource Code:https://github.com/collective/collective.saconnectYou can clone the source and submit pull requests orget access to the github-collectiveand work directly on the project repository.Changelog2.0.1 (2016-04-04)fixed packaging2.0 (2016-03-31)Overhaul: autopep8/manual pep8, utf8-header, buildout/setup modernized
[jensens]1.4 (2011-10-06)Include CMFCore’s permissions.zcml under Plone 4, so thecmf.ManagePortalpermission is known.
[hannosch]Fix typo that prevented z3c.saconfig support from ever being enabled.
[elro]1.3 (2009-05-28)Update z3cform dependency to plone.app.z3cform, and add include it’s
configuration in configure.zcml.
[mj]Added optional support for z3c.saconfig connections; each connection
string in collective.saconnect automatically is registered as a z3c.saconfig
scoped session utility.
[elro, mj]1.2 (2009-03-20)Fixed adding new entries after the editing fix.
[mj]1.1 (2009-03-17)Fixed editing existing entries.
[mj]1.0 (2009-03-17)Initial release
[mj]
Package: collective.saoraclefixes
collective.saoraclefixesFix SQLAlchemy 0.4 and 0.5 Oracle quoting and offset/limit problems.This package monkeypatches the SQLAlchemy Oracle driver with backports from
the SQLAlchemy 0.6 branch. Fixes included are:Reserved words. Before 0.6 no Oracle-specific reserved words were included,
requiring you to rename columns and labels, making it difficult to code
in a database-neutral fashion.Note that the oracle reserved words list in this package is a superset of
the list in SQLAlchemy 0.6 (at least until SQLAlchemy branches/rel_0_6
r6245). This package includes semi-reserved identifiers as defined by theOracle V$RESERVED_WORDS viewBindparameter quoting. Using a reserved word as a bind parameter requires
quoting as well. Parameters are quoted in the generated SQL code, and all
use of the parameters during execution correctly uses the quoted versions.Limit/offset handling. 0.6 introduces a (much) better method of implementing
query limits and offsets in Oracle, following recommended Oracle practice.
The 0.4/0.5 method could result in incorrect ordering, or would completely
fail when sorting on a aliased column.The backport includes support for the optimize_limits=False dialect flag.
For more information on the change, seeSQLAlchemy ticket #536.To use, simply add an import to this package:import collective.saoraclefixes # apply oracle fixesNote that the patches will only apply when SQLAlchemy versions 0.4 and 0.5 are
used. All patching activity will be logged via python’s logger module with
loglevel DEBUG.Licensecollective.saoraclefixes is distributed under theMIT license, just like SQLAlchemy.CreditsBackporting workMartijn PietersatJarnChangelog1.2 - 2009-08-20Disable FromClause.default_order_by in 0.4; 0.5 removes this functionality
altogether, it’s not needed, and interferes with the quoting of rowid on
Oracle.1.1 - 2009-08-12Add the improved LIMIT/OFFSET handling from 0.6.1.0 - 2009-08-05Initial release
Package: collective.schedule
collective.schedule===================This package integrates the python 'schedule' library (https://github.com/dbader/schedule) with Plone.It provides the following:* A ZML interface for scheduling jobs* A single 'tick' job processing view that can be registered using a Zope Clock ServerConfiguration-------------First add `collective.schedule` to your buildout eggs.Then register the collective.schedule 'tick' method as a clock server in your buildout config:[buildout]...[instance]recipe = plone.recipe.zope2instance...zope-conf-additional =<clock-server>method /plonesitename/@@schedule-tick# If you have virtual host rewriting, you will need to# use the following format instead:# method /VirtualHostBase/http/www.mysite.com/plonesitename/VirtualHostRoot/@@schedule-tickperiod 300user usernamepassword password</clock-server>Scheduling jobs---------------You can then register jobs using ZCML as follows:<configurexmlns:schedule="http://namespaces.zope.org/schedule"><include package="collective.schedule" /><schedule:jobview="@@some-regular-job"unit="day"at="22:00"/></configure>Where 'view' is the *name* of a browser view that can be looked up on the Plone Site and executed with the user defined in the clock server above.For more details on the options for scheduling jobs, see https://github.com/dbader/scheduleContributors============- Matt Sital-Singh (mattss), Original AuthorChangelog=========0.2 (2015-03-23)----------------- Better error handling and logging.Exceptions in jobs no longer affect other jobs.[mattss]0.1.4 (2013-10-02)-------------------- Package distribution fixes[mattss]0.1.3 (2013-09-20)-------------------- Documentation updates[mattss]0.1.2 (2013-09-20)-------------------- Look up the context (plone site) correctly[mattss]0.1.1 (2013-09-20)-------------------- Correctly wrap the context in with a request (Fixes AttributeError 'REQUEST' in page templates)[mattss]0.1 (2013-06-14)-------------------- Initial release[mattss]
Package: collective.schedulefield
collective.schedulefieldNew schedule field for formsContributorsGillian Sampont, Original Author [Affinitic]Martin Peeters [Affinitic]Changelog0.6.1 (2018-10-15)Do not display comment if empty.
[bsuttor]0.6 (2018-04-23)Also view schedule if only comment is set.
[bsuttor]Added missing z3c.form meta.zcml.
[sgeulette]0.5 (2017-04-27)Bugfix: get json schedule.
[bsuttor]0.4 (2017-04-25)Bugfix: do not try to load json value if there is no values.
[bsuttor]0.3 (2017-03-01)Do not render the viewlet if there is no values
[mpeeters]0.2 (2016-07-14)Add the ScheduledContent behavior
[mpeeters]Add a comment field for each schedule day
[mpeeters]0.1 (2014-08-26)Initial release