Saravanan666/pypi-org huggingface dataset:
Package: collective.contentrules.comingsoon
IntroductionThis module adds a new rule type to Plone content rules system
which is handled when a Plone event, or any content having a start date,
will begin tomorrow, or within any delay.First, add collective.contentrules.comingsoon package to the
‘eggs’ parameter of your buildout, or in the dependencies of your policy product,
and restart your buildout.Then you have to create a cron
that calls once a day ‘@@comingsoon-notify’ view on site root,
using a wget for example. (http://localhost:port/my/site/@@cominsoon-notify).You may use z3c.recipe.usercrontab recipe that manages cron tasks from buildout:http://pypi.python.org/pypi/z3c.recipe.usercrontab/Then, you can add ‘Coming soon’ rules to your content rules.
Those rules will be handled on each event content
whose start date is among a defined delay.The notification delay can be set on ‘Coming soon’ configuration page.
The default delay is one day.Changelog1.2 (2013-03-27)It is now possible to use per content type delays !
[cedricmessiant]1.1 (2012-12-21)index is now a view parameter (for example, for expirationDate : @@comingsoon-notify?index=expires)
[cedricmessiant]Update buildout
[cedricmessiant]1.0.2 (2011-04-28)Add buildout & bootstrap.
[toutpt]Add dependency of plone.app.registry in default profile and upgrade step.
[toutpt]1.0.1 (2011-04-27)Avoid ComponentLookupError with Plone 4.0.
[thomasdesvenain]1.0 (2011-04-06)Initial release.
[thomasdesvenain]
Package: collective.contentrules.imaging
IntroductionThis addon let you configure a pre compute of images scales using a content rule.Using gallery or slideshow addons can be a problem when you handle lots of photos.
To optimize the database Plone do not pre compute image’s scales. But when it’s
time to display of photo gallery with 30 thumbs the server has to compute them
at the same time. That’s what this addon try to workaround.How to installAs any other plone addons, please the official documentation:http://plone.org/documentation/kb/installing-add-ons-quick-how-toNote this addon doesn’t have any profile to activate it.How to useYou have to create the content rule in the backoffice,
activate it on the folder you need it.CreditsCompaniesPlanet Makina CorpusContact Makina CorpusPeopleJeanMichel FRANCOIS aka toutpt <toutpt@gmail.com>Changelog1.0 (2013-01-03)Initial release
Package: collective.contentrules.linguatarget
IntroductionThe normal Plone ‘move’ and ‘copy’ content rules do not take translations of
the specified target folder into account. Instead, all objects, regardless of
their language, are moved/copied to the single specified folder.This product provides two custom Plone Content Rules.LinguaMoveLinguaCopyThe purpose of which is to move or copy objects to the correct language version
(translation) of the specified target folder.Changelog0.5 (2012-09-17)Include CMFCore’spermissions.zcml. [thomasw]0.4 (2009-10-09)Plone4 complianceFixed a bug with objects added that have no language set (jcbrand)0.3 (2009-10-06)Fixed a bug where non-lingua actions also invoke the Lingua Executioner (jcbrand)Use the UberSelectionWidget (jcbrand)0.1 (unreleased)Initial release
Package: collective.contentrules.mail
IntroductionThis package provides an extended content rule “mail” action with many more
variable substitutions available, including the name and email address of
the content owner, making it possible to email the owner of a piece of
content.It is also possible to provide new “replacers” by writing an interface with
an associated adapter and registering a newIMailModelutility. The user
is able to pick the replacer to use on the action edit form.Changelog0.7 (2016-03-17)Ported tests to plone.app.testing
[tomgross]Plone 4.3 compatibiliy
[tomgross]Moved tohttps://github.com/collective/collective.contentrules.mail[maurits]0.6 (2012-02-23)Remove an extra From header when calling mailhost.secureSend()
[dimboo]0.5 - 2011-05-20Added an exception in IVocabularyFactory import for Plone >= 4.1.
[lepri]0.4 - 2009-09-06Avoid a site error if the mail cannot be sent, e.g. because the mail
server is down.
[optilude]Avoid throwing an exception on encoded strings in the replacer.
[optilude]Caught workflow exception when trying to get state on object without any
workflow.
[tiazma]Added cc and bcc fields to IMailAction enabling the use of these fields in
mail messages
[erico_andrei]Added new variables to IMailReplacer so it is possible to send emails to
users with other roles than owner on the object
[erico_andrei]Made sure Archetypes content implements IDublinCore (It’s not the default
behavior until AT 1.5.10)
[erico_andrei]Correct action mail fail on try to replace bcc or cc when it returns None [lucmult]0.3 - 2009/03/24Added a note in the UI about how to use variables.
[optilude]The ‘source’ field is not required, but would throw an error if not filled
in. This is now fixed.
[optilude]0.2 - 2009/03/24Made the executor fail gracefully if the content being acted upon is not
adaptable to the replacer interface.
[optilude]Made the default replacer adapt any Dublin Core-capable content, avoiding
an unnecessary dependency on Archetypes.
[optilude]Made the default IMailModel implementation more re-usable.
[optildue]Updated documentation and interface specifications.
[optilude]Fixes actions/configure.zcml in order to play nice with GenericSetup0.1 - UnreleasedInitial release
Package: collective.contentrules.parentchild
IntroductionThis package provides new conditions and actions for the Plone content rules
system:A condition to check whether a child object of a given type and/or
workflow state exists.An action to trigger automatic workflow transitions on the current
object or the nearest parent object of a given type.An action to invoke a particular workflow transition on the nearest parent
object of a given type.Changelog1.0b1 (2009-03-25)Initial release
Package: collective.contentrules.setfield
collective.contentrules.setfieldIntroductionThis content rule lets you set the value of fields on a content object.The rule lets you enter PythonScript and you return a dictionary of fields
and their values.The package defines an ‘Objects parent modified’ trigger so that the rule can
be triggered when an objects parent is modified.Changelog0.9.1 (2021-08-05)Fixed running setfield when using theupdate_alloption instead of the object that triggered the content rule #27 [JeffersonBledsoe]Added black, isort and flake8 #28 [JeffersonBledsoe]0.9.0 (2021-07-27)Initial release.
[instification]Add configurable option to set values on all content that would match the executing rule.
[instification]Add configurable option to preserve modification date of updated objects.
[instification]Add ‘Objects parent modified’ trigger and handler to contentrules.
[instification]Add unit tests.
[JeffersonBledsoe]Ensure only dexterity fields can be set and values are valid or error thrown
[djay]Fix bug where object with no workflow would prevent rule being fired
[djay]
Package: collective.contentrules.subscription
This product will add to Plone a new content rule, similar to the default “Send an email” ones, but email recipients are taken from a list of addresses that are subscribed for that rule.Use-caseWe want to notify about some updated of the site, and we want to allows users to subscribe or not to these notifications automatically.We can do this with a contentrule registered for some object creation, and use our new action to send emails.ContentsUse-caseSetting up the ruleRule subscriptionSubscriptions overwiewTo-doRequirementsAuthorsChangelogSetting up the ruleThis product provides a new rule action to connect with base Plone rules. When you create a new action, you need to fill some fields:SubjectThe e-mail subject. You can place inside this text some markers.Sender emailThe sender of the e-mail. If empty, will be automatically used the one set in portal mail settings.MessageThe body text of the e-mail that will be sent. The text is the same for all section where
the rule is activated on.You can place inside this text some markers.The list of markes is shown at the bottom of action’s edit form.Rule subscriptionAs we said previously, site managers can create some rules, and users (also anonymous users) can choose which rules subscribes to.To do this, there is a simple form created with z3c.form that shows all available rules with our custom action.The form is available at “http://site_url/@@notify-subscribe”If the user is authenticated and have an email address, email field is automatically filled.There is also an anti-spam check made withcollective.z3cform.norobots.Subscriptions overwiewThere is also an overview controlpanel for site administrators that shows all rule subscriptions and allows to remove some addresses.This view is available from Plone controlpanel or at “http://site_url/@@contentrules-subscription-controlpanel”To-doAllow users to unsubscribeImprove subscription security using some confirm machineryRequirementsThis product has been tested on:Plone 4.0Plone 4.1Plone 4.2Plone 4.3AuthorsThis product was developed by RedTurtle Technology team.Changelog0.1.0 (2013-05-10)Initial release [cekk]
Package: collective.contentrules.talesaction
InstallationAdd collective.contentrules.talesaction to the ‘egg’ parameter of your buildout section[buildout]
...
eggs +=
    ...
    collective.contentrules.talesactionOr add it to the install_requires parameter of the setup.py of your modulesetup(
    ...
   install_requires=[
    ...
    'collective.contentrules.talesaction',
    ]Then restart your buildout and your instance.UseGo to theRulessection ofSite configuration.
You can now addTALES Expression actionto the actions of your rules.
Changelog
=========1.0 (2011-04-13)Initial release
Package: collective.contentrules.template
IntroductionThis package provides a new action for the Plone content rules system that
can create content based on a template. The content rule is set up with a
template content item that will be copied into the context folder when the
rule is executed.ChangelogunreleasedAdded support to copy children objects of source folder  [lucmult]1.0b1 (2009-03-24)Initial release [optilude]
Package: collective.contentrules.yearmonth
collective.contentrules.yearmonthThis package defines a content rules action similar to the the standard move one provided by Plone.
You are able to choose a root destination target folder and once applied the element will be moved into a dynamic target destination/YYYY/MM folder.
Year and month folders depend on the rule execution date and they are automatically added if not existent.
You can provide a different target folder writing your own adapter and move contents in different dynamic target folders.Credits and contributionsRedominoMakina CorpusContributorsJeanMichel FRANCOIS [toutpt]Davide Moro [davideilmoro]Changelog1.1 (2013-01-07)Add transitions and folderish_type options to the add/edit form.
[toutpt]Fix issue with year/month when month < 10 should be 2013/01 and not 2013/1
[toutpt]1.0 (2012-12-04)Initial release
Package: collective.contentstats
Introductioncollective.contentstats  adds a section to the Plone control panel
showing summary statics of the content of the site. Specifically,
it provides a table listing the number of content items broken down
by portal type versus review state. Non-zero entries are linked to
a listing of the respective items. Access to the page requires the
‘Manage portal’ permission.FeaturesWorks on catalog data exclusively - no content is touched.Only lists portal types that are usedOnly lists review states usedWorks with custom add-ons right awaySupports CSV export of summary dataTested with Plone 3.3.5 and 4.0.5Changelog1.0.1 (2011-05-09)Get rid of setup.cfg1.0 (2011-05-09)Initial release
Package: collective.contentsync
Introduction============collective.contentsync addresses the case where many folders must be synchronized with one master folder template.For example, your system has many clients who need to upload files into a directory structure. Your template may look like this:Template- Accreditation files- Financial statements 2008- Financial statements 2009- Staff profilesEvery client must also have this structure since content is going to be uploaded into that structure. Suppose you have 1000 clients and now you add "Financial statements 2010" to your template. This new folder must be pushed to every single client. This process would be time-consuming by hand, hence the existence of collective.contentsync.Rules of synchronization========================The terms "source" and "destination" are used. The rules are dependent on an item providing information as to whether it was created by a synchronization or a user.1. New items in the source tree are copied to the corresponding location in the destination tree. If an item already exists at this location in the destination tree it is preserved.2. Items which appear in the destination tree but not the source tree are deleted if and only if they were created during a synchronization and do not contain any items that were created by a user.3. Items which appear in the destination tree and which were created during a synchronization are renamed if the corresponding source item is renamed. The rename is limited to title and does not include the id.User interface==============The user is presented with a progress bar and a detailed log. This providesconstant feedback and prevents timeouts.Usage=====Append /@@collective.contentsync.form to the URL of the item you wish to synchronize, or simply run the collective.contentsync profile in portal_setup. Running the profile will add a Synchronize tab to every folderish item in your site.collective.contentsync has not been tested with a pure Zope application but should "just work" since it has no Plone dependencies.Changelog=========1.01----* If an object in the source tree is renamed it is renamed in the target on a* sync* More progress outputs1.0----------------* Initial release
Package: collective.contextualcontactinfo
Table of contentsDocumentationDependenciesCreditsAuthorsChangelogDocumentationThis package change the “contact info” behavior of your Plone Site,
adding the information about the context where the user were when he
accessed the contact form.In this way the Site Manager will receive an additional URL indicating
the position of the “problem”.This is very useful if users send messages like:“I get an error in this page” (but he don’t say where)“I can’t access the page” (but he don’t say where)DependenciesTested with:Plone 3.3Plone 4.1CreditsDeveloped with the support ofAzienda USL Ferrara;
Azienda USL Ferrara supports thePloneGov initiative.AuthorsThis product was developed by RedTurtle Technology team.Changelog0.1.0 (2012-06-15)Initial release
Package: collective.contract-management
collective.contract_managementProvides Contracts container and Contract item CT’s, to manage contracts and there lifespan. It helps you to keep track of the notice period and start on time with the negotiation, planing or canceling for each contract.FeaturesOverview of all contracts or contracts which are due to verify, based on Collectionsical export of a notice period event, including a defined reminder via @@ics_viewical export of multible contract notice periods via collection and @@contracts_ics_viewworks well in combination withcollective.collectionfilterExported events are set as full day events for the contract end date, including an alarm. The event summery is prefixed with the title of the most upper parent Contracts obj.TranslationsThis product has been translated intoEnglish (MrTango)German (MrTango)InstallationInstall collective.contract_management by adding it to your buildout:[buildout]

...

eggs =
    collective.contract_management[collectionfilter]and then runningbin/buildoutContributeIssue Tracker:https://github.com/collective/collective.contract_management/issuesSource Code:https://github.com/collective/collective.contract_managementSupportIf you are having issues, please let us know.
If you have questions or need adjustments, contactmd@derico.de.LicenseThe project is licensed under the GPLv2.ContributorsMaik Derstappen,md@derico.deChangelog2.0 (2020-02-17)Allow collectionfilter to work with contentlisting view
[MrTango]2.0b8 (2020-02-04)Fix bug in ical export when contract end date was missing
[MrTango]2.0b7 (2020-02-04)Fix pdf landscape mode
[MrTango]2.0b6 (2020-02-04)Use landscape for pdf export
[MrTango]2.0b5 (2020-02-04)Optimize layout of Contracts view table
[MrTango]2.0b4 (2020-02-03)Don’t implement IEvent, because it breaks the event portlet.
[MrTango]Add PDF-Export view for Contracts and add buttons for PDF and iCal-Export
[MrTango]2.0b3 (2020-01-27)only process IContract objects not IEvent objects
[MrTango]2.0b2 (2020-01-21)Add uid and url fields to ICS export.
[MrTango]Add summery_prefix to exported event summeries, based on most upper parent Contracts obj.
[MrTango]2.0b1 (2020-01-20)Add contracts_ics_view, calendar_from_collection adapter, locales and optimize styling on contract_view1.0b5 (2020-01-14)Add contract_amount field to Contract and add an index for it
[MrTango]1.0b4 (2019-11-26)Allow nested Contracts containers
[MrTango]Make start/end date not required
[MrTango]Fix upgrade steps to not show up in addon control panel
[MrTango]1.0b3 (2019-11-21)Add Collection to allowed_content_types for Contracts CT
[MrTango]Add contract_view and locales
[MrTango]1.0b2 (2019-11-21)Enable Notice period criteria for Collections
[MrTango]Fix vocabularies
[MrTango]Add indexer for contract_reminder and enable it for Collections
[MrTango]1.0b1 (2019-11-21)Initial release.
[MrTango]
Package: collective.coreloadtests
# IntroductionCoreloadtests contains 3 tests:ContentCreationReadonlyWriteheavy## Usage:Add to buildoutCreate Plonesite called coreloadtestsUse quickinstaller to install collective.coreloadtests contentcreationRun test: bin/test -s collective.coreloadtestsChangelog0.2 (2014-04-04)Moved to githubadded some simple instructions in README0.1 - UnreleasedInitial release
Package: collective.cropimage
This package provides image cropping for images which reside in ATContentTypes fields in Plone.
Those images can be cropped without losing the original images and without adding new images to blobs.
It only sets the cropping dimension to the object annotations.Currently tested WithPlone-4.3.6 and Python-2.7.10Image and News Item Content Types.collective.contentleadimageHow to crop imageActivate collective.cropimage package throughAdd-ons configurationpage.Click linkCrop Image RegistryunderAdd-on Configuration.Add ID with which the crop dimension will be stored.Go to content type where you want to crop images.From Actions, clickCrop Image.Select the name of ID.Now you can drag over image to select the crop area.Save the area.How to use the cropped image on your templateFor example:<div tal:replace="structure python: context.restrictedTraverse('cropped-image')('image', 'small-image')" />Here,imageis the field name andsmall-imageis the ID name.collective.contentleadimagecollective.cropimageworks withcollective.contentleadimage, too.
The image field name isleadImage, so use cropped image like:<div tal:replace="structure python: context.restrictedTraverse('cropped-image')('leadImage', 'small-image')" />Change log1.8 (2015-07-16)Add dependency to Products.CMFPlacefulWorkflow for test. [taito]Fix crop image for image wider than 680px.1.7 (2014-08-13)Update jquery.jcrop.js to version 0.9.12. [taito]Fix for image scaling site which uses max-width. [taito]1.6 (2013-05-11)Move test packages to extras_require. [taito]1.5 (2013-01-06)Test with Plone-4.2.3. [taito]Add testing integration to Travis CI. [taito]1.4 (2012-11-14)Test with Plone-4.2.2. [taito]1.3 (2012-08-30)Fix bug in registry.xml export. [taito]1.2.1 (2012-04-07)Change package name from inicie.cropimage into collective.cropimage. [taito]Turn into non-Zope2 package. [taito]Fix javascript loading error for production site. [taito]1.1.1 (2012-01-25)CSS updates. [taito]1.1 (2011-11-12)Setting aspectRatio, minSize and maxSize is not available. [taito]Update copy right. [taito]Test with collective.contentleadimage. [taito]1.0 (2011-10-03)Initial release. [taito]CreditsThe Finnish Association for Nature Conservation (Suomen Luonnonsuojeluliitto).
Package: collective.css3buttons
# CSS3 Buttons for Plone #This package brings in the functionality of [CSS3 buttons](http://css3buttons.michaelhenriksen.dk) into [Zope](http://zope.org) /[Plone](http://plone.org/).## Buildout Installation ##Add the egg and zcml references to your buildout.cfg:[buildout]...eggs =...collective.css3buttons...[instance]...zcml =...collective.css3buttons...## Usage Instructions ##### Enable the stylesheet ###If you are using this directly (i.e. within Zope and/or without Plone),you will need to include the css resource file like so:<style type="text/css">@import url(/++resource++collective.css3buttons.resources/stylesheets/css3buttons.css);</style>If this is used under Plone, just activate the product `CSS3 Buttons`under Site Setup > Add-ons.### Add the classes ###Just insert the HTML fragments as defined in the [documentation](http://css3buttons.michaelhenriksen.dk) for CSS3 Buttons into yourtemplate files.## License ##### The [Unlicense](http://unlicense.org): ###This is free and unencumbered software released into the public domain.Anyone is free to copy, modify, publish, use, compile, sell, ordistribute this software, either in source code form or as a compiledbinary, for any purpose, commercial or non-commercial, and by any means.In jurisdictions that recognize copyright laws, the author or authors ofthis software dedicate any and all copyright interest in the software tothe public domain. We make this dedication for the benefit of the publicat large and to the detriment of our heirs and successors. We intendthis dedication to be an overt act of relinquishment in perpetuity ofall present and future rights to this software under copyright law.THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESSOR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHERLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISINGFROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHERDEALINGS IN THE SOFTWARE.For more information, please refer to <http://unlicense.org/>Changelog=========0.1 - 2011-06-08----------------* Initial release
Package: collective.cssgridsystem
IntroductionCSS frameworks that trying to cut down css work to create pages based on grid
layouts960 grid system960cssGrid System is an effort to streamline web development workflow.The packaged version is 1.5URLS:++resource++960gs/960.css++resource++960gs/960_24_col.css++resource++960gs/reset.css++resource++960gs/rtl_960_24_col.css++resource++960gs/rtl_960.css++resource++960gs/rtl_text.css++resource++960gs/text.cssSource non minified is available under ++resource++960gs/src/Documentation is available in the package.Blueprint cssblueprintcssA CSS framework that aims to cut down on your CSS development timeThe provided version is 0.9URLS:++resource++blueprintcss/ie.css++resource++blueprintcss/print.css++resource++blueprintcss/screen.cssSource non minified is available under ++resource++blueprintcss/src/Plugins are available under ++resource++blueprintcss/plugins/buttonsfancy-typelink-iconsrtlCreditsCompaniesPlanet Makina CorpusContact usAuthorsJeanMichel FRANCOIS aka toutpt <toutpt@gmail.com>ContributorsChangelog1.0 (2010-07-28)Initial release
Package: collective.cultureRelations
IntroductionA setup for Products.references that configures it for cultural institutions according to the INTK Online StrategyChangelog0.5 (2011-3-8)Added Date translations0.4 (2011-2-22)Tweeked StrategicTypes.Recurse into works to find Events to relate to people.0.3 (2011-2-17)Added missing files0.2 (2011-2-17)Activated share counter0.1 (2011-2-16)Initial release