Saravanan666/pypi-org huggingface dataset:
Package: plone.app.event-ploneintegration
NOTE: THIS PACKAGE IS OBSOLETEplease use the latest plone.app.event release, which includes the ploneintegration code. See:http://pypi.python.org/pypi/plone.app.eventplone.app.event-ploneintegrationThis package integrates plone.app.event into Plone 4 releases, where
plone.app.event is not in the core. This is the case for all Plone 4 releases
at the time of this release.Installation for Plone 4.1To install plone.app.event for Plone 4.1, please use the
plone.app.event-ploneintegration package. Include it in your buildout config or
in your integration package’s setup.py and apply the
“plone.app.event Plone4 integration” profile.
The plone.app.event-ploneintegration package pulls all dependencies, which are
needed for plone.app.event.Warning!!!
Backup! Don’t do this on a Plone setups in production, only install
plone.app.event for new setups or report any upgrade issues. Upgrading is yet
not tested and no upgrade steps are provided - this is still a task to do.
Expect weired behavior regarding date/time/timezones and any other bugs.
!!!Bug reportingPlease report bugs here:https://github.com/collective/plone.app.eventThis url may change tohttps://github.com/plone/plone.app.eventsome time soon!More informationSee:https://python.org/pypi/plone.app.eventChangelog1.1 (2012-03-28)Add portlets.xml to unregister the Event portlet.
Fixes:https://github.com/collective/plone.app.event/issues/9[thet]1.0 (2012-03-12)Initial release.
[thet]
Package: plone.app.hud
This Plone add-on contains several HUD Panels:Best Practices - Plone best practices panel.Content Browser - browse through catalog.Security Advisories - RSS reader forsecuriry advisoriesdirectly inside Plone.Users - basic users information.It usesplone.hud frameworkSource code @ GitHubReleases @ PyPIContinuous Integration @ Travis-CIInstallationTo installplone.app.hudyou simply addplone.app.hudto the list of eggs in your buildout.ActivationRun buildout and restart Plone.
Then, installplone.app.hudusing the Add-ons control panel.UsageAccess the panels by adding/@@hudto the end of site URL, like so:http://localhost:8080/Plone/@@hudOr by clickingHUD PanelsinSite Setuppage.ConfigurationEvery panel has it’s own permission,
so that you can assign it to any role you wish.How to make your own panels?collective.examples.hud @ GitHubDevelopmentAdd to your Plonebuildout.cfg:...
eggs +=
    ...
    plone.hud
    plone.app.hud
...
extensions += mr.developer
sources = sources

auto-checkout =
    plone.hud
    plone.app.hud

[sources]
plone.hud = git git://github.com/plone/plone.hud.git
plone.app.hud = git git://github.com/plone/plone.app.hud.git
...Changelog1.0a1 (2013-09-17)Initial release.
[Matej Cotman]Translations sl, es and ru
[Natasa Cotman]
Package: plone.app.imagetile
Image tile, to be used withDeco Layout Editor.ContentsChangelogThis is initial release of Image Tile and is incomplete, but it is included in
first release of Deco, just to work on tiles api on which other tiles will be
based on.Please report issues inDeco’s issue trackerChangelog1.0 (2012-06-22)initial release.
[garbas]
Package: plone.app.intid
IntroductionThis package provides a Generic Setup extension profile that will
install an IntId utility in a CMF portal.  Additionally, it registers
intid handlers for the standard object events on CMF content.  Finally,
it finds existing CMF content in the portal and registers it with the
IntId utility.Installation notesInstallation for Plone 3.3 requires plone.app.intid <= 1.0b3 and
five.intid <= 0.4.3.Changelog2.0.0 (2023-04-15)Breaking changes:Drop python 2 support.
[gforcada] (#1)Internal:Update configuration files.
[plone devs] (3b8337e6)1.1.4 (2020-04-20)Bug fixes:Minor packaging updates. (#1)Initialize towncrier.
[gforcada] (#2548)1.1.3 (2017-06-08)Bug fixes:removed unittest2 dependency[kakshay21]1.1.2 (2016-07-05)Bug fixes:setuphandler now can deal with could-not-adapt exception (TypeError).This may happen and must not stop the handler from working1.1.1 (2016-04-15)Fixes:Fix code analysis errors reported byhttp://jenkins.plone.org/view/Pkgs/job/package-plone.app.intid[gforcada]1.1.0 (2015-09-07)Plone 5: plone.app.intid is a dependency of plone.app.linkintegrity which is
a dependency of CMFPlone, so it is always installed. Adapt tests to this
change.
[pbauer]1.0.4 (2015-03-12)Don’t install utility for zope.app.intid’s IIntIds,
which is just an alias for the one in zope.intid.
[davisagli]fix test to not addFolderfti in testSetup if it already exists.
[jensens]1.0.3 (2014-02-25)Make the test setup independent from basic content types in the
PLONE_FIXTURE.
[timo]1.0.2 (2012-12-17)removing zope.app.container as dependency and importing events interfaces
from zope.lifecycle
[garbas]intid/setuphandlers.py: Removed blacklisted and unused interface
IDynamicType from query. Closeshttp://dev.plone.org/ticket/11946.
[kleist]1.0.1 (2012-06-15)Fixed registration of pre existing contents in the intids utility
[gborelli]Added setup tests
[gborelli]1.0 (2012-02-20)Remove includeOverride for five.intid. [thet]Fix import step intid-register-content to register content
in all Languages if LinguaPlone is installed. [csenger]1.0b3 2010-02-27Made compatible with Plone 3.3
[alecm]1.0b2 2010-02-22fixed dependency of import profiles
[naro]1.0b1 2010-02-07Initial release
[alecm]
Package: plone.app.jquery
Introductionplone.app.jquery adds thejquerylibrary to Plone.Included is the jQuery migration plugin. You can install it by importing thedevelopmentprofile.VersionsVersion numbers of the package is the same as the jQuery library + packaging version.For the latest available versions of this package, see ourPyPI page.Note that this 1.11 version is not officially used by any Plone
version.  Use at your own risk/discretion.  Plone 4.3 uses 1.7.x.Note that on Plone 5, this package is no longer used.Changelog1.11.2 (2015-08-28)Use jQuery 1.11.2
[MatthewWilkes]1.9.1.2 (2014-09-23)Add jquery.min.map for jQuery 1.9.1 fromhttps://raw.githubusercontent.com/jquery/jquery/1.9.1/jquery.min.mapand
modify jquery-1.9.1.js script to include it.
[thet]1.9.1.1 (2014-07-10)Add development profile to include the unminified version of jQuery and the
migrate plugin.
[thet]Add jQuery migrate plugin.
[thet]Better naming for jQuery resources in filesystem.
[thet]Fix initial-upgrade profile directory declaration.
[fulv]1.9.1 (2013-03-06)Add 1.9 branch with jQuery 1.9.1.
[toutpt]
Package: plone.app.jsonfield
ContentsIntroduction (plone.app.jsonfield)FeaturesInstallationLinksLicenseContributorsChangelog1.0.0a3 (2018-01-22)1.0.0a2 (2017-12-27)1.0.0a1 (2017-12-24)Introduction (plone.app.jsonfield)JSON field for Plone.FeaturesPlone restapi supportWidget: z3cform supportplone.supermodel supportplone.rfc822 marshaler field supportjson schema support (draft3 and draft4)InstallationInstall plone.app.jsonfield by adding it to your buildout:[buildout]

...

eggs =
    plone.app.jsonfieldand then runningbin/buildoutLinksCode repository:https://github.com/nazrulworld/plone.app.jsonfieldContinuous Integration:https://travis-ci.org/nazrulworld/plone.app.jsonfieldIssue Tracker:https://github.com/nazrulworld/plone.app.jsonfield/issuesLicenseThe project is licensed under the GPLv2.ContributorsMd Nazrul Islam (Author),email2nazrul@gmail.comChangelog1.0.0a3 (2018-01-22)fix(bug): Empty string value raise json validation error1.0.0a2 (2017-12-27)plone restapi,z3c widget,plone.supermodel,plone.rfc822marshaler field and plone schema editor are activated.[nazrulworld]json schemavalidation support is added.[nazrulworld]1.0.0a1 (2017-12-24)Initial release.
[nazrulworld]
Package: plone.app.layoutpage
plone.app.layoutpageprovides a very basic page content type for Plone
that is editable via Deco.Changelog1.1 (2012-12-17)flake8 on code
[garbas]possibility to add “page” content type as default page and marking it as
folderish for TinyMCE
[garbas]use deco grid classes
[davisagli]use classes and only one column, row by default
[vangheem]1.0 (2012-06-23)initial release.
[garbas]
Package: plone.app.lockingbehavior
IntroductionTheplone.app.lockingbehaviorpackage provides aplone.lockingintegration
for dexterity.UsageJust use the behaviorplone.app.lockingbehavior.behaviors.ILockingin
your dexterity content type. Also check the condition of the “edit” action
of your type, it should check if the object is locked.In yourprofiles/default/types/YOURTYPE.xmladd the behavior and the
edit action:<?xml version="1.0"?>
<object name="example.conference.presenter" meta_type="Dexterity FTI"
        i18n:domain="example.conference" xmlns:i18n="http://xml.zope.org/namespaces/i18n">

    <!-- enabled behaviors -->
    <property name="behaviors">
        <element value="plone.app.lockingbehavior.behaviors.ILocking" />
    </property>

    <action action_id="edit"
            visible="True"
            title="Edit"
            category="object"
            url_expr="string:${object_url}/edit"
            condition_expr="not:object/@@plone_lock_info/is_locked_for_current_user|python:True">
        <permission value="Modify portal content"/>
    </action>

</object>The ILocking behavior enables locking support for your content type. This adds
theITTWLockableinterface fromplone.locking. The locking viewlet
fromplone.app.layoutis also working for the dexterity content type.More Informationhttp://pypi.python.org/pypi/plone.lockingChangelog2.0.0 (2023-10-07)Internal:Update configuration files.
[plone devs] (cfffba8c)1.0.7 (2020-04-20)Bug fixes:Minor packaging updates. (#1)1.0.6 (2018-11-21)Bug fixes:Cleanup project level files (setup.py, .travis-ci.yml…) [maurits]
[gforcada] (#2524)1.0.5 (2017-02-12)Bug fixes:Add coding header on python files.
[gforcada]Unskip test for Zope 4, as isolation problems are already fixed.
[thet]1.0.4 (2016-05-02)New:Add behavior short name.
[jensens]1.0.3 (2016-02-20)Fixes:Use a functional layer to resolve test isolation problems.
[gforcada]Refactor doctest to an integration test and skip it for Zope 4 due to isolation problems.
[pbauer]Changed i18n_domain to “plone”.
Requires plone.app.locales 4.3.9 or higher.
[claytonc]1.0.2 (2015-09-09)Remove superfluous ‘for’.
[fulv]Fix tests: redirect was changed in commit e7367258.
[jone]If the content is locked, the redirect points to the default view and
not to the absolute_url of the object. It avoids image opening on redirect
[parruc]1.0.1 (2011-12-06)Fix version requirement of plone.dexterity: 1.1 is compatible.
[jone]1.0 (2011-11-27)Fixed problem: locks were not released when editing content and saving
it without changing anything. Fixed by using new IEditFinishedEvent instead
of IObjectModifiedEvent.
[jbaumann]Fixed problem which caused widget traversal to fail.
The edit form is now protected for non-anonymous user, since locking for
anyonmous users does not work anyway.
[jbaumann]Initial implementation
[jbaumann]
Package: plone.app.protect
IntroductionThis package contains utilities that can help to protect parts of Plone
or applications build on top of the Plone framework.protect decoratorThe most common way to use plone.app.protect is through theprotectdecorator. This decorator takes a list ofcheckersas parameters: each
checker will check a specific security aspect of the request. For example:from plone.app.protect import protect
from plone.app.protect import PostOnly

@protect(PostOnly)
def SensitiveMethod(self, REQUEST=None):
    # This is only allowed with HTTP POST requests.This relies on the protected method having a parameter called REQUEST.HTTP POSTIf you only need to allow HTTP POST requests you can use thePostOnlychecker:from plone.app.protect import PostOnly
from plone.app.protect import protect

@protect(PostOnly)
def manage_doSomething(self, param, REQUEST=None):
    passThis checker only operators on HTTP requests; other types of requests
are not checked.Form authenticationA common problem in web applications is Cross Site Request Forgery or CSRF.
This is an attack method in which an attacker tricks a browser to do a HTTP
form submit to another site. To do this the attacker needs to know the exact
form parameters. Form authentication is a method to make it impossible for an
attacker to predict those parameters by adding an extra authenticator which
can be verified.To use the form authenticator you first need to insert it into your form.
This can be done using a simple TAL statement inside your form:<span tal:replace="structure context/@@authenticator/authenticator"/>this will produce a HTML input element with the authentication information.
Next you need to add logic somewhere to verify the authenticator. This
can be done using a call to the authenticator view. For example:authenticator=getMultiAdapter((request, context), name=u"authenticator")
if not authenticator.verify():
    raise UnauthorizedYou can do the same thing more conveniently using theprotectdecorator:from plone.app.protect import CheckAuthenticator
from plone.app.protect import protect

@protect(CheckAuthenticator)
def manage_doSomething(self, param, REQUEST=None):
    passChangelog1.0b1 - March 7, 2008Refactor the code to offer a generic protect decorator for methods
which takes a list of checkers as options. Add checkers for both the
authenticator verification and HTTP POST-only.
[wichert]1.0a1 - January 27, 2008Initial release
[wichert]
Package: plone.app.relations
OverviewA set of components to provide a content centric API for the engine from
plone.relations, as well as a few different core relationship types and
policies. See the package README.txt for details on usage.CreditsAuthor: Alec Mitchell <apm13@columbia.edu>Based on the index and relationship container from zc.relationship by
Gary Poster from Zope Corporation.This work was partly sponsored by The Daily Reel (http://www.thedailyreel.com)Changelog2.0 - 2011-10-10Avoid dependency on zope.app.event and use zope.lifecycleevent if available.
[hannosch]Changed the way temporary interfaces are attached and removed during
the various stage of copy events.
[do3cc]1.0rc1 - 2008-10-28Removed the bool(rel.__parent__) check for performance reasons and
replaced with if/else
[tesdal]
Package: plone.app.s5slideshow
IntroductionThis addon integrates the s5 slideshow to Plone.It is intended for use with Plone 4.4. Previous versions of Plone
included the s5 slideshow feature in core.About S5S5 is a slide show format based entirely on XHTML, CSS, and JavaScript. With one
file, you can run a complete slide show and have a printer-friendly version as
well. The markup used for the slides is very simple, highly semantic, and
completely accessible. Anyone with even a smidgen of familiarity with HTML or
XHTML can look at the markup and figure out how to adapt it to their particular
needs. Anyone familiar with CSS can create their own slide show theme. It’s
totally simple, and it’s totally standards-driven.Installation and UsageGo to Site Setup and activate the ‘S5 Slideshow support’ add-on.Now when you edit a document and go to the Settings tab there is a
checkbox to enable presentation mode. When it is enabled a link
will be shown at the top of the document to access the presentation
mode.Changelog1.0 (2013-03-09)Initial release
[toutpt & davisagli]
Package: plone.contentrules
Overviewplone.contentrules provides a “pure Zope” implementation of a a rules engine
which allows arbitrary conditions and actions to be combined into rules, and
rules to be executed dependent on events.You can think of this as somewhat similar to user-assembled mail filtering rules
or something like Apple’s Automator. It is used by plone.app.contentrules to
provide such functionality for Plone.Changelog3.0.1 (2023-11-30)Bug fixes:Replace deprecated zope.container imports with their canonical locations.
[maurits] (#1)Internal:Update configuration files.
[plone devs] (cfffba8c)3.0.0 (2023-04-19)Bug fixes:Drop python 2.7.
[gforcada] (#1)Internal:Update configuration files.
[plone devs] (5cc689e5)2.1.3 (2023-03-21)Bug fixes:UseZODBas dependency rather than the deprecatedZODB3.
[gforcada] (#1)2.1.2 (2021-07-28)Bug fixes:Fixed another deprecation warning forObjectEventfromzope.component.
[maurits] (#3130)2.1.1 (2021-04-27)Bug fixes:Fix fields in the interface IRuleConfiguration: enabled, stop and cascading are not required. [andreesg] (#11)2.1.0 (2020-09-07)New features:Fixed deprecation warning forIObjectEvent/ObjectEventfromzope.component.
Drops compatibility with Plone 5.0 and earlier.
[maurits] (#3130)2.0.10 (2020-04-20)Bug fixes:Minor packaging updates. (#1)2.0.9 (2018-10-31)Bug fixes:Fix tests to not rely on a specific__repr__of MoveToFolderAction and make py3 the default in test-output.
[pbauer]2.0.8 (2018-09-27)Bug fixes:Fix tests in py3.
[pbauer]2.0.7 (2018-01-30)Bug fixes:Add Python 2 / 3 compatibility
[pbauer]2.0.6 (2016-08-08)Fixes:Use zope.interface decorator.
[gforcada]2.0.5 (2016-02-25)Fixes:CSRF fix: safe write on read.
[gforcada]2.0.4 (2014-01-27)If a rule is ‘cascading’, actions executed by this rule
can recursively trigger other rules.
[thomasdesvenain]2.0.3 (2013-06-13)Fix: Plone 4.3 sites were broken by “Content added” content rules created before 4.3.
[thomasdesvenain]2.0.2 (2013-01-13)Field descriptions on add form are consistent with the ones in edit form.
[thomasdesvenain]Add MANIFEST.in.
[WouterVH]2.0.1 - 2011-04-01Event types vocabulary is internationalized.
This closeshttp://dev.plone.org/plone/ticket/7059.
This closeshttp://dev.plone.org/plone/ticket/6902.
[thomasdesvenain]2.0 - 2010-07-18Update license to GPL version 2 only.
[hannosch]2.0b1 - 2010-06-13Cleaned up package metadata.
[hannosch]Usezope.containerinstead of its olderzope.appvariant.
[hannosch]Cleaned up tests to rely on a minimal amount of packages.
[hannosch]Clarified license and copyright.
[hannosch]Specify package dependencies.
[hannosch]1.1.0 - 2008-04-20Unchanged from 1.1.0a11.1.0a1Merge PLIP 204 - GenericSetup support. A contentrules.xml file can now
be used to import and export rule definitions and assignments.
[optilude]1.0.5Use the plone i18n domain for text found in metadirectives.py.
[hannosch]Added i18n markup to the IRuleConfiguration schema, which is used in a
user-visible configuration. This closeshttp://dev.plone.org/plone/ticket/6886.
[hannosch]
Package: plone.controller
Introductionplone.controller is a wxpython visual controller for Zope2 / Plone. Add it to a buildout
with a part specification like:[controller]
recipe = zc.recipe.egg
eggs =
  plone.controllerThis will generate a script, bin/plone-controller to start the controller, reading the
buildout.cfg in the current directory for configuration information. You may also specify
the config file on the command line.The Python used for the buildout must include wx. This is not currently set as
a “requires” for the package because wx has a very large number of dependencies.The controller provides a GUI for starting/stopping and checking the status of
a Zope 2 intance.Changelog1.8 - 2010-08-11Forgot to check in this change for Plone 4.0 beta 5. Closes #10448.
[kleist]1.7 - 2010-07-31Changed name on the “View Plone” button to “Create/View Plone site”,
clicking it now opens the new fancy Zope root page.
[kleist]1.6 - 2009-08-18Request privilege elevation.
[sidnei]1.5If buildout.cfg is not specified, and not in the current path,
look for it in the path above the script.1.4Added an icon set for Windows.1.3Removed File and Help menu items. The only useful thing lost is
access to the “about” page, and we should look for another way to
provide that. [smcmahon]1.2Import pywintypes and pythoncom before any other import of
pywin32. This makes pywin32 find them correctly on a relocatable
Python build. [sidnei]1.1Turn off diagnostic messages unless the “DEBUG” environment
variable is set. [smcmahon]Search for buildout.cfg in current directory if
no config file is specified on command line.
[smcmahon]Widen display and move sw to better fit sidnei’s
changes.1.0 - 2009-03-04Eggified from XController, added dependency on
collective.buildout.cluster [sidnei]Initial release [sidnei]
Package: plone.directives.tiles
This package provides declarative configuration (grokkers) for theplone.tilespackage.ContentsUsageNotesChangelog1.2 (unreleased)1.1 (2012-11-26)1.0 (2012-06-23)UsageA basic tile is configured like this:from five import grok
from plone.directives import tiles

from my.package import MyMessageFactory as _
from my.package.interfaces import IMyTileSchema

class MyTile(tiles.Tile):
    grok.context(IContext)
    grok.require('zope2.View')

    grok.name('my.tile')
    grok.title(_(u"My title"))
    grok.description(_(u"My description"))

    tiles.add_permission('mypackage.AddMyTile')
    tiles.schema(IMyTileSchema)NotesA persistent tile can be configured by deriving fromPersistentTileinstead ofTile.Thecontext(),requires(),name(), andlayer()directives
are used in the same way as they are for a view derived fromgrok.View.Templates are associated using the same semantics as are used for views. For
example, a tile inmytiles.pydefined in the classMyTilewould
be associated with a templatemytiles_templates/mytile.ptby default.Unlike a view, thename()directive is required and should give a dotted
name for the tile by convention.Dictionary key access (__getitem__()) is defined to work as it does in
a tile. In a standard grokked view, it will retrieve a macro from the
template. In a tile, it is used as a traversal hook to set the tile id,
and subsequently to look up views on the tile. Seeplone.tilesfor
details.Similarly, standard grokked views have aurl()method which can be used
to construct a URL, possibly with query string parameters. For grokked
tiles, this is replaced by aurlread-only property, which returns the
canonical tile URL, as perplone.tiles.Changelog1.2 (unreleased)Use zope.interface decorators.
[gforcada]Change i18n domain.
[thet]Cleanup package.
[maurits]1.1 (2012-11-26)Added icon directive to support plone.tiles >= 1.1.
[datakurre]1.0 (2012-06-23)Initial release
[garbas]
Package: plone.fieldsets
OverviewAn extension to zope.formlib, which allows to group fields into different
fieldsets.Changelog2.0.3 (2015-05-11)Whitespace cleanup, git ignores.
[gforcada, rnixx]2.0.2 (2012-07-02)Add MANIFEST.in.
[WouterVH]2.0.1 - 2011-04-03Require five.formlib on Zope 2.13 to call processInputs before rendering
the fieldset.
[vincentfretin]2.0 - 2010-07-18Update license to GPL version 2 only.
[hannosch]Clarify test dependencies and remove deprecated code, allowing us to remove
thezope.deferredimportdependency.
[hannosch]2.0a1 - 2009-04-04Specify package dependencies.
[hannosch]1.0.3 - 2008-08-18Documentation updates.
[hannosch]1.0.2 - 2008-07-04Restored Zope 2.9 compatibility. This closeshttp://dev.plone.org/plone/ticket/8177.
[hannosch]Added conditional import logic to make the package work without Five.
[hannosch]1.0.1 - 2008-03-09Deprecated the convenience import, as it confused the test coverage tool.
[hannosch]Added tests for all aspects of the fieldsets.
[hannosch]Added tests for the edit and input forms.
[hannosch]1.0 - 2007-08-13No changes.
[hannosch]1.0rc3 - 2007-07-28Corrected missing history.
[hannosch]1.0rc2 - 2007-07-27Removed unnecessary adapters definition in FieldsetsInputForm.
[davconvent]Added FieldsetsInputForm to the available fieldsets forms.
[davconvent]1.0rc1 - 2007-07-09Removed useless setup.cfg.
[hannosch]Added new optional description attribute to fieldsets.
[hannosch]1.0b2 - 2007-05-01No changes.
[hannosch]1.0b1 - 2007-03-05Fixed error reporting by referencing the widgets on the form itself on
the individual fieldsets rather than copying them.
[duncan, nouri]Initial implementation of the fieldsets class and the edit form support.
[hannosch]Initial package structure.
[zopeskel]