Saravanan666/pypi-org huggingface dataset:
Package: collective.symlink
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.symlink by adding it to your buildout:[buildout]

...

eggs =
    collective.symlinkand then runningbin/buildoutContributeIssue Tracker:https://github.com/collective/collective.symlink/issuesSource Code:https://github.com/collective/collective.symlinkDocumentation: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.ContributorsAffinitic,support@affinitic.beChangelog1.0a1 (2021-08-25)Initial release.
[affinitic, sgeulette]
Package: collective.synchro
A tool for synchronize content beetwen plone instanceHow to install ?o In plone3 go to portal_quickinstaller and install collective.synchroo In plone2.5 go to portal_setup , in properties select collective synchro as
active configuration and in import click toImport all stepsHow it work ?This tool import content via plugin. By default there is three plugins : fss, zexp and delete
You can add and write new plugin (see PLUGIN.txt) for your use caseIt store exported data in file system in order to be reimported in an
another instance (or multiple instance). An external program must copy data to an import queue.
This egg provide a scripts for ssh transport.
Add in your buildout (example of buildout are available in collective/synchro/buildout directory) this part to configure scripts:[synchro]
recipe = zc.recipe.egg
eggs =
   collective.synchro

extra-paths=
   ${instance:location}
   ${zope2:location}/lib/pythonThis create in your bin of buildout three scripts :o bin/create_queue  -d PATH, –directory=PATH , create a queue structureo bin/synchronize_queue  -s SOURCE -d DEST , synchronize queue by ssh (via ssh key) (-h for other options)o bin/import_queue -p PATH , import data from queue (-h for other options)Important, the import_queuemust berun with an zeoclient instance:>>> bin/instance run bin/import_queue ...The synchronization is fire by the zope3 event system. There is a generic method
call by all events : collective.synchro.events.synchro.Plugin are choice by event (plugin list for ObjectModified and  ObjectRemovedEvent are different).
This registry is managed by the synchronization_toolThe localisation of import is done by queyring a multiadapter that decide where the content
is reimported. You can change by zca, the localisation of your import content.The structure of a queue looks like as this:./IMPORT
./IMPORT/TO_PROCESS -> all files in order to process
./IMPORT/DONE -> file that are synchronized with an EXPORT queue
./IMPORT/ERROR -> data in error
./IMPORT/PROCESSING -> files are synchronizing with an EXPORT queue
./EXPORT
./EXPORT/TO_PROCESS -> files that are scheduled to export
./EXPORT/DONE -> files that are imported in the instance
./EXPORT/ERROR -> files in error
./EXPORT/PROCESSING -> files are importing from queueHow to configure the export ?Go to zmi, in portal_synchronisation configure:o queues : filesystem path (create if don't exits, one queue for one instance)

o expressions : a tal expression that must be true to synchronized contentCompatibilityThis package is tested in plone2.5 and plone3.1TODOo interface to register/unregister plugins in zmio callback for imported contentChangelog1.0.2 - Plone2.5.2 complianttest on Plone2.5.2 with Five 1.4.2reindex object after importfix fss import for Five 1.4.21.0.1 - InitialAdd script to synchronized and import contentFix bug in delete plugin (see export.txt)1.0.0 - UnreleasedInitial release
Package: collective.synchronisedworkflow
Fix a security bug that allowed people with permission to transition a
subset of translations to transition them all.
[MatthewWilkes]Take account of new translations being created and move the latest item from
the workflow history (including state) to the newly created object.
[MatthewWilkes]Support in Plone 4 for automatically propagating workflow transitions
between translations.
[MatthewWilkes]Initial Skeleton
[MatthewWilkes]
Package: collective.tabr
Introductioncollective.tabr allows for easy editing of “tabbed content” using thejQuery
Tools TabsUI tool.InstallationAdd collective.tabr to your buildout. It uses the z3c.autoinclude plugin so you
do not need to add it to thezcml=section of your buildout.Install via the Add-on Products control panel like you would any other Product.UsageTabs are created by selecting “Tab” from the style menu of your editor. This
will cause everything after the “Tab” element to be a part of that tab’s pane
until another Tab, Default Tab, or “Pane Break” is reached. For example:<h2 class="content-tab">First Tab</h2>
<p>This is a paragraph inside the first tab</p>

<h2 class="default-content-tab">Second Tab</h2>
<p>This is a paragraph inside the second tab</p>
<p>This tab will be shown first</p>

<hr class="pane-break" />

<p>This paragraph is not inside of a tab</p>

<h2 class="content-tab">First Tab part 2</h2>
<p>This paragraph will be in the first tab of the second grouping of tabs</p>This will result in two groups of tabs, the first of which will contain two tabs
of which the second will be pre-selected when the page loads. The second tab
group will only have a single tab in it, and it will be preceded by a paragraph
between itself and the end of the previous tab group.CustomizingCSS is available in thetabrskin layer for customization, as are the
example images for the CSS.DependenciesThis package depends on thejQuery Toolslibrary which is provided byplone.app.jquerytools. It does not depend on a specific version of either
jQuery Tools or jQuery, but you should check to make sure that another package
is not including multiple versions of any library in use, though this is not
common.CreditsThanks to Mikko Ohtamaa forcollective.kuputabswhich was my inspiration for
this. Most of the code was his to begin with, and I ripped it appart and mademanychanges.Also thanks to Douglas Bowman for hisCSS Sliding Doorstechnique for the
tab styling.Changelog1.2 - 2010-07-02Added working “insert pane break” button to Kupu.
[dunlapm]Improve styling for the pane break in all browsers.
[dunlapm]1.1 - 2010-06-30Removed locales directory since we don’t have any translations
[dunlapm]1.0 - 2010-06-25Initial release
Package: collective.tabularlabeloverrides
collective.tabularlabeloverridesAllows to override the labels for the tabular view on a Collection.Featuresprovides a behavior for Collections with a Label Overrides fieldThese labels will override existing labels in the tabular viewthis addon depends on collective.taxonomy to allow both working togetherInstallationInstall collective.tabularlabeloverrides by adding it to your buildout:[buildout]

...

eggs =
    collective.tabularlabeloverridesand then runningbin/buildoutOr install it viapip install collective.tabularlabeloverridesUsageDefine some label overrides mappings on a Collectionchange the display view to the newTabular label override viewAuthorsMaik Derstappen -md@derico.deContributorsPut your name here, you deserve it!?ContributeIssue Tracker:https://github.com/collective/collective.tabularlabeloverrides/issuesSource Code:https://github.com/collective/collective.tabularlabeloverridesDocumentation:https://docs.plone.org/foo/barSupportIf you are having issues, please let us know by opening an issue on GitHub.LicenseThe project is licensed under the GPLv2.ContributorsMaik Derstappen,md@derico.deChangelog1.0b4 (2023-08-17)Fix label override view, when no override is provided.
[MrTango]1.0b3 (2023-08-14)Fix label override validator, when no override is provided.
[MrTango]1.0b2 (2023-08-11)enable tabular_label_overrides behavior on Collection by default
[MrTango]add tabular_label_override_view to available_view of Collection CT
[MrTango]1.0b1 (2023-08-11)general functions
[MrTango]1.0a1 (2023-08-11)Initial release.
[MrTango]
Package: collective.taghelper
Project Description===================Taghelper uses Zemanta, OpenAmplify, Evri, OpenCalais, Yahoo, SiLLCand tagthe.netInstallation with buildout==========================Add collective.taghelper to the eggs section of you buildout: ::eggs =collective.taghelperActivate the product in your add ons section. This will install a Tag Helpercontrolpanel in you site setup. You have to fill in the API Keys for thewebservices you want to use and choose if you want to use the local contentor the destination of a link if your content type has an attribute remote_url(In Plone OOTB this would be the link type). The product addsa new tab for your content named tagging. In this form you can choose thekeywords you want to add to your content. Keywords assigned earliermanually will be preserved.- Code repository: https://svn.plone.org/svn/collective/collective.taghelper/- Questions and comments to product-developers@lists.plone.org- Report bugs at http://plone.org/products/collective.taghelper/issuesChange history**************Changelog=========0.3.1 (2011/12/19)------------------- fix unicode errors- catch error if evri does not return any results0.3 (2011/12/08)----------------- add Zemanta, OpenAmplify, Evri- make relevance configurable where applicable0.2 (2011/11/16)----------------- add AlchemyApi- get tags asynchronsously via AJAX- comment out rarely used api methods to reduce clutter- ommit tags that are already assigned as keywords- add terms of use for webservices0.1 (2011/02/22)----------------- initial release- Created recipe with ZopeSkel["nan"]Download********
Package: collective.teamwork
Introductioncollective.teamwork is an add-on for Plone supporting workspaces with
associated workgroups of users, managed locally.There are two native types of workspaces: a project, which is a workspace
that is considered top-level and serves as a navigation root, and a normal
workspace, which can be nested within other workspaces, including projects.RequiresPlone 4.2+ (currently tested against 4.3).Dexterity (plone.app.dexterity) 1.0+–Author: Sean Upton <sean.upton@hsc.utah.edu>Copyright 2011-2013, The University of Utah.Released as free software under the GNU GPL version 2 license.
See doc/COPYING.txtChangelog0.9 (2013-12-16)Updated to use of UUID-based group names. [seanupton]Various updates to make group configuration management
pluggable.
[seanupton]Moved source from uu.qiext to collective.teamwork
[seanupton]
Package: collective.teaser
collective.teaserTeaser/Banner content type for PloneThis Plone add-on installs the content type teaser, which is meant to be used
for small advertisements on a homepage to advertise own or external content.Randomly selected teasers will be shown in a Teaser portlet. An importance
level controls the frequency, how often teasers are shown - a teaser with
higher importance will be shown more frequently. If more teasers are shown in
portlets on a page, one teaser isn’t shown twice.If you need to show specific teasers only in specific portlets (e.g. to
distinguish between horizontal and vertical teasers), use the importance levels
or subject filter to assign teasers to those portlets.CopyrightJohannes Raggam, BlueDynamics Alliance - AuthorRobert Niederreiter, BlueDynamics Alliance - ContributionsChangelog2.3 (2013-11-23)Add an upgrade helper for old, pre 2.0 collective.teaser portlets by adding
a dummy Assignment class to common.py.
[thet]Don’t restrict to only published teasers. Also show unpublished for users
with appropriate permissions.
[thet]Just cache portlet rendering on request instead of custom cachekey function.
[thet]2.2Fix Unicode.
[rnix, 2012-09-26]Fix use in conjunction withcollective.lineage.
[rnix, 2012-09-25]Fix portlet assignment lookup.
[rnix, 2012-09-25]Adddisplay_columnsfor teaser portlet.
[rnix, 2012-08-16]Add portlet header for teaser portlet.
[rnix, 2012-08-16]2.1Fix HTML validation error - div not allowed as direct descendent of dl.
[thet]2.0Configurable search path of teaser portlet.
[rnix]2.0b1Remove IPortletAvailable adapter, which was a overcomponentized
proof-of-concept and too complicated to be used.
[thet]Remove alternative image field, which was meant to allow a portlet to select
an Landscape/Portrait image from the same teaser. The meaning of the option
was unclear. Instead, upload two different Teasers and select different
importance levels for it.
[rnix, thet]Option to get Teasers via AJAX call. This makes the teaser portlet better
cachable.
[rnix]1.0Remove text field and use optionally the description field instead.
[thet]Add Teaser to image_types in portal_atct to allow image scale recreation.
[thet]Add HistroyAwareMixin and configure Teaser to be versionable.
[thet]Initial release
Package: collective.testimony
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.testimony by adding it to your buildout:[buildout]

...

eggs =
    collective.testimonyand then runningbin/buildoutContributeIssue Tracker:https://github.com/collective/collective.testimony/issuesSource Code:https://github.com/collective/collective.testimonyDocumentation: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.ContributorsValentin Piret,valentin.piret@affinitic.be, Original Author [Affinitic]Sébastien Sirtoli,sebastien@affinitic.be[Affinitic]Nicolas Demonté,nicolas.demonte@affinitic.be[Affinitic]Aurore Mariscal,aurore.mariscal@affinitic.be[Affinitic]Laurent Lasudry,laurent.lasudry@affinitic.be[Affinitic]Changelog1.0a1 (2020-08-19)Initial release.
[Vaal24]
Package: collective.testing
general package for testing and debugging aids for CMF, Plone, Zope2 and Zope3includes a layer for ZCML integratin testingzcml for a default page for test objects (useful in zope 2.9)postmortem helper:>>> from collective.testing.debug import autopsy
>>> @autopsy
>>> def problem_func():
...     raise Exception('Trouble!')some profiling toolssome logging and printing subscribers for zope.eventssome fake response and request objects for zope
Package: collective.testswarm
A test layer for running JavaScript test jobs on a TestSwarm instanceThis uses plone.app.testing.layers.PLONE_ZSERVER as a base to start a plone instance. The test job can be configured either from buildout or overridden with shell environment variables. After the job is scheduled the plone instance runs until the timeout is reached. Results are not yet collected from the TestSwarm instance.How to configure your project to use collective.testswarmFirst you will need to set up a testswarm instance:https://github.com/jquery/testswarmAdd a user (e.g. tsuser) and find out the auth key for that user (mysql: select auth from users where name = “tsuser”;). This is the user account that your tests can use for adding test jobs. Use these details in the buildout section described below or pass them as environment variables (uppercase) to the test runner:$ TS_USER=myuser ./bin/testyour.product/setup.py:extras_require={
    'test': 'collective.testswarm'
    }buildout.cfg:[test]
recipe = zc.recipe.testrunner
eggs = your.product [test]
environment = testswarm-instance

[testswarm-instance]
ts_url = http://testswarm
ts_user = tsuser
ts_auth = asdf1234asdf #select auth from users where name = "tsuser";
ts_job_name = Test collective.testswarm
ts_urls = http://localhost:55555/plone/example-qunit-suite
ts_suites = QUnit example
ts_browsers = popularbeta
ts_max_jobs = 1
ZSERVER_HOST = 55555
ZSERVER_PORT = localhostHow to use the collective.testswarm layeryour.product/your/product/tests/layers.py:from plone.app.testing import PloneSandboxLayer

from collective.testswarm.layers import TESTSWARM_LAYER

class YourProductLayer(PloneSandboxLayer):
    defaultBases = (TESTSWARM_LAYER, )

    def setUpPloneSite(self, portal):
        self.applyProfile(portal, 'your.product:testswarm')

YOURPRODUCT_LAYER = YourProductLayer()your.product/your/product/tests/test_swarm.py:import unittest2 as unittest

from layers import YOURPRODUCT_LAYER


class TestSwarmTestCase(unittest.TestCase):
    layer = YOURPRODUCT_LAYER

    def test_your_product_swarm(self):
        """ You need one test for the testrunner to sniff out
        """collective.testswarm changelog0.3 (2011-07-24)Removing the accent from my name in setup.py [cillian]0.2 (2011-07-24)Nothing changed, just trying to push another release to avoid a
UnicodeEncodeError on the author field [cillian]0.1 (2011-07-24)Initial release, has only been used for running its own tests
[cillian]ContributorsCillian de Roiste (Syslab.com GmbH)
Package: collective.theme.iwaters
===============================================collective.theme.iwaters===============================================Overview--------This product is a installable Plone Theme developed by `IW:LEARN <http://iwlearn.net/>`_.The origins of this theme date back to 2005, it was converted to a deliverance theme in 2010.Requirements------------- Plone 4.1.x (http://plone.org/products/plone)- plone.app.themingInstallation------------Add Plone site~~~~~~~~~~~~~~Install Plone 4.1 with plone.app.theming and create a Plone site (if you have not already) with Diazo theming configured.Zip file~~~~~~~~If you are an end user, you might enjoy installation via zip file import.Download the zip file: http://plone.org/products/collective.theme.iwaters/releases/0.3/iwaters.zipImport the theme from the Diazo theme control panel.With buildout~~~~~~~~~~~~~To use this skin, on a buildout based installation:Edit your buildout.cfg and add the following information::[buildout]...eggs =collective.theme.iwatersplone.app.themingIf another package depends on the collective.theme.iwaters egg orincludes its zcml directly you do not need to specify anything in thebuildout configuration: buildout will detect this automatically.After updating the configuration you need to run the ''bin/buildout'',which will take care of updating your system.Go to the 'Site Setup' page in the Plone interface and click on the'Add/Remove Products' link.Choose the product (check its checkbox) and click the 'Install' button.Uninstall -- This can be done from the same management screen, but onlyif you installed it from the quick installer.Note: You may have to empty your browser cache to see the effects of theproduct installation.Changelog=========0.3 (2012/04/26)-----------------* fix base which was not copied from content.0.2 (2011/08/26)-------------------* Initial release
Package: collective.tileindex
collective.tileindexAn add-on for PloneFeaturesCatalog index that tells you which tiles are in use.
Think of Mosaic or collective.cover, or any package that builds onplone.app.blocks.tile-types-viewfor a page, showing which tiles this page uses.tile-types-overviewfor the Plone site root, with a total for the whole site, including search results for individual tiles.DocumentationThe documentation is this README file.TranslationsThis product has been translated intoDutchInstallationInstall collective.tileindex by adding it to your buildout:[buildout]

...

eggs =
    collective.tileindexand then runningbin/buildout.
Go to the Add-ons control panel to activate it.
This goes through the whole Plone Site and updates the index for items with theplone.layoutawarebehavior.AuthorsFred van Dijk (Zest Software)Maurits van Rees (Zest Software)ContributeIssue Tracker:https://github.com/collective/collective.tileindex/issuesSource Code:https://github.com/collective/collective.tileindexSupportIf you are having issues, please let us know.
We have a mailing list located at:project@example.comLicenseThe project is licensed under the GPLv2.ContributorsZest Software,info@zestsoftware.nlChangelog1.0.0a2 (2023-11-21)Add controlpanel link to the tile types overview. [fredvd]Show published and Private/other counts when using the tile_types_overview and
clicking on individual tiles to see the found mosaic pages.
[fredvd]1.0.0a1 (2023-11-16)Initial release.
[fredvd, maurits]
Package: collective.tiles.advancedstatic
A tile that shows html text, allowing to add some defined styles, class and other optionFeaturesEmulates the old text portlet with some extra fieldsCustomizable footer labelCustomizable “read more” linkCustomizable header background imageCustomizable additional css classesSelect a Preset style from listMosaic-readyInstallationInstall collective.tiles.advancedstatic by adding it to your buildout:[buildout]
...
eggs =
    collective.tiles.advancedstaticand then runningbin/buildoutUsageYou can’t use this tile without a tile manager (or maybe, you can if you create
new tiles manually in some specific context) likeMosaicorredturtle.tiles.managementPreset stylesIf you need to give users the
This is just select with a list of css classes with user-friendly names that will be appended to the tile container.To populate this list, you need to set a series of values in a registry entry:Advanced static tiles: available CSS stylesEach value is a string with css class name and human-friendly name separated by a “|” character, like this:tile-red|tile with red background
tile-blue-no-title|tile with blue background without titlewhere tile-red and tile-blue-no-title are css classes with some specific css rules in the theme.TranslationsThis product has been translated intoItalianContributeIssue Tracker:https://github.com/collective/collective.tiles.advancedstatic/issuesSource Code:https://github.com/collective/collective.tiles.advancedstaticCreditsDeveloped with the support of:Regione Emilia-RomagnaRegione Emilia-Romagna supports thePloneGov initiative.AuthorsThis product was developed by RedTurtle Technology team.LicenseThe project is licensed under the GPLv2.ContributorsLuca Bellenghi,info@redturtle.itChangelog2.0.0 (2022-09-16)Prepare package for pip
[eikichi18]1.1.0 (2019-05-30)Python 3 compatibility
[cekk]Added more italian translations
[pnicolli]1.0.4 (2019-05-14)Added some italian translation
[eikichi18]Added support for plone.app.multilingual
[eikichi18]1.0.3 (2019-03-15)Fix problem with image height using old attributes
[lucabel, daniele-andreotti]Fix image ref navigation
[daniele-andreotti]1.0.2 (2018-08-10)Fix document outline [nzambello]Add missing dependency (plone.app.tiles)
[cekk]1.0.1 (2018-07-26)Fix tile insert in Plone 5.1 when using mosaic tiles edior. [fredvd]1.0.0 (2018-05-09)Improve readme
[cekk]1.0a2 (2017-09-13)Add mosaic support in a separate profile. If mosaic is installed, this will be installed.
[cekk]Fix tile visibility only when the product is installed
[cekk]1.0a1 (2017-03-31)Initial release.
[]
Package: collective.tiles.carousel
collective.tiles.carouselA slider tile for plone.app.mosaic based on the carousel component of Bootstrap 5.InstallationInstall collective.tiles.carousel by adding it to your buildout:[buildout]

...

eggs =
    collective.tiles.carouseland then runningbin/buildoutContributeIssue Tracker:https://github.com/collective/collective.tiles.carousel/issuesSource Code:https://github.com/collective/collective.tiles.carouselDocumentation:https://docs.plone.org/foo/barLicenseThe project is licensed under the GPLv2.ContributorsPeter Holzer,peter.holzer@agitator.comPeter Mathis,peter.mathis@kombinat.atChangelog1.0.3 (2023-11-03)Fix carousel speed “0” to stop autoplay.
[petschki]Fix image cropping when activated.
[petschki]configure withplone/meta.
[petschki]1.0.2 (2023-09-21)Update indicators markup to Bootstrap 5.x
[petschki]1.0.1 (2022-08-02)Fix tile title/description condition.
[petschki]1.0.0 (2022-08-01)Initial release.
[agitator, petschki]