Saravanan666/pypi-org huggingface dataset:
Package: collective.ploneseltest
IntroductionThis package provides a PloneTestCase-like class for running Selenium tests.It requires that you have Selenium RC (http://selenium-rc.openqa.org) running whilst the tests are running. The current version of the Python ‘selenium’ library (which is an automatically installed dependency of this package) seems to work best with Selenium RC 0.9.2. Once downloaded, run it with:$ java -jar selenium-server.jarSee test_example.py for an example of a test that sets up a Plone site and runs a simple test.See testcase.py for more information about the convenience methods contained in the SeleniumTestCase base class and the layer it uses to configure Selenium. You may want to use a custom layer derived from this one if you need to manage the Selenium Server information more carefully.Note that you can set the following environment variables to affect where the Selenium driver looks for the Selenium RC server:SELENIUM_HOST, the hostname (default to “localhost”)SELENIUM_PORT, the hostname (default to “localhost”)SELENIUM_BROWSER, the browser to launch (defaults to “*chrome”)UsageA simple test case may look like this:from collective.ploneseltest import SeleniumTestCase

class DocumentTestCase(SeleniumTestCase):

    def afterSetUp(self):
        """Setup for each test
        """
        self.setRoles(['Manager'])
        self.login_user()

    def test_create_document(self):
        self.selenium.click("//dl[@id='plone-contentmenu-factories']/dt/a/span[1]")
        self.selenium.click("document")
        self.wait()
        self.selenium.type("title", "Some document")
        self.selenium.click("name=form_submit")
        self.wait()
        self.failUnless(self.selenium.is_text_present("Some document"))The usual test setup and suite boilerplate has been omitted.Seehttp://selenium-rc.openqa.org/python.htmlfor more information about available client commands. You may also be interested inhttp://selenium-ide.openqa.org.GotchasIt is possible to set up state in an afterSetUp() method, e.g.:def afterSetUp(self):
    self.setRoles(['Manager'])
    ...However, you should explicitly commit all changes before starting to run Selenium commands:import transaction ; transaction.commit()To make this easier, there is a convenience self.open() method. This will open up the Plone site or a page within it. It will perform a commit before doing so, in case there are uncommitted changes.Note that self.open() is used by self.login_user(), thus to start each test as a logged-in Manager user, you would do:def afterSetUp(self):
    """Setup for each test
    """
    self.setRoles(['Manager'])
    self.login_user()Changelog1.0b2fixed a bug when selenium would start two times [Domen Kozar]1.0b1Initial release
Package: collective.ploneslimbar
ContentsIntroductionChangelog1.1 (2013-04-12)1.0 (2012-10-02)IntroductionPlone Slimbar puts a tiny bar listing all the local communities sites on top of your plone portal.
Contributors
============Maurizio Delmonte, Abstract, Author
Giorgio Borelli, Abstract, LaborerChangelog1.1 (2013-04-12)added plone.ro website [hman]1.0 (2012-10-02)added plone.nl website [gborelli]Fixed js registry entryReordered viewletsChanged stylesAdded browser layerAdded buildout config
[gborelli]Package created using zopeskel
[Maurizio Delmonte, Abstract]
Package: collective.pluggablelogin
Introductioncollective.pluggableloginoverrides the standard Plone login form
with a template using a portlet manager, so that various login
components can be configured.ConfigurationGo to the Addons control panel and activate “Pluggable Login Page.”Now if you go to/loginwhile logged in as a Manager, you’ll see a
“Manage portlets” link which you can use to manage the available
login portlets. By default, the standard login portlet and a
registration form portlet are enabled (the latter is only shown
if self registration is enabled for the site).As well as manual assignment via the web interface, the pluggable login
page can also be assigned portlets via GenericSetup, in the same way
as Plone’s other portlet managers can. For example, to register a custom
porlet on the pluggable login page, use this an example withinportlets.xmlinside a GenericSetup profile:<portletsxmlns:i18n="http://xml.zope.org/namespaces/i18n"i18n:domain="plone"><assignmentname="navigation"category="context"key="/"manager="collective.pluggablelogin"type="my.product.portlets.CustomLoginPortlet"insert-before="*"visible="True"><propertyname="title">string:Loginportlettitle</property><propertyname="description">string:Exampleproperty</property></assignment></portlets>CreditsDeveloped by David Glick andGroundwire Consulting. Sponsored by theInnocence Project.To-doRefactor inline styles on the logged in or out views.Changelog1.2.1 (2015-05-20)Avoid double form tags and invalid markup on the registration portlet with
new-style z3cforms.
[davidjb]1.2 (2015-03-23)Allow the registration portlet to work with both new (z3cform) and
old-style (zope.formlib) register forms.
[davidjb]1.1 (2014-01-30)Add id to the login-portlets div, ensuring the element can be selected
on the page.
[davidjb]Improve styles for login page, normalising with logged out page.
[davidjb]Add logged out page templates to display pluggable login.
[davidjb]Improve styles and formatting for login page.
[davidjb]Fix issue with empty <div> generated on login page after trailing </html>
end tag.
[davidjb]1.0 (2012-05-10)Initial implementation
[davisagli]
Package: collective.portlet.accuweather
This portlet displays the current weather in one or more locations.It relies on an RSS feed from AccuWeather.com, and uses various icon
sets from AccuWeather.com and elsewhere.Most of the feed parsing code is shamelessly stolen from
collective.portlet.feedmixer, written by Wichert Akkerman.
Changelog
=========1.0b2 (2009-09-11)Be more robust if the response is empty.
[optilude]1.0b1 (2009-08-27)Initial release
Package: collective.portlet.adsense
A Plone3 style portlet to use Google AdSense in a Plone site.FeaturesPortlet AdSense allows to easily insert Google AdSense code in a Plone site
using a dedicated portlet.It also provides configuration options to:use a pre-built Google AdSense slot code
customize Ad colors
customize PSA behaviour
set test mode onRequirementszope 2.10.xplone 3.xRelease notesTested on Plone 3.1. It should run on any Plone 3.xInstallingInstalling without buildoutYou can install this package in either your system path packages or in the
lib/python directory of your Zope instance. You can do this using either
easy_install or via the setup.py script.After installing the package it needs to be registered in your Zope
instance.  This can be done by putting a
collective.portlet.adsense-configure.zcml file in the etc/pakage-includes
directory with this content:<include package="collective.portlet.adsense" />or, alternatively, you can add that line to the configure.zcml in a
package or Product that is already registered.Installing with buildoutIf you are usingbuildoutto manage your instance installing
collective.portlet.adsense is even simpler. You can install it by adding
it to the eggs line for your instance:[instance]
eggs = collective.portlet.adsense
zcml = collective.portlet.adsenseThe last line tells buildout to generate a zcml snippet that tells Zope
to configure collective.portlet.adsense.If another package depends on the AdSense portlet egg or includes its zcml
directly you do not need to specify anything in the buildout 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.Usage notesAdSense code and Size are always mandatory.
AdSense slot code is optional; if an ad sense slot code is used its size and
format should match the one
choosen in the Size field.Custom colors will override other choicesAlternate color and Alternate URL fields can be used to customize the Ad space
behaviour in the event that Google is unable to serve targeted ads.Full information on Google AdSense can be found in the Google AdSense documentation:https://www.google.com/adsense/supportKnown bugsNo known bugsCreditsPortlet AdSense developement by Francesco Merlo -francesco.merlo@reflab.comPortlet AdSense contributions by Eleonora Borelli -eleonora@reflab.comLicenseSee docs/LICENSE.txt
Package: collective.portletalias
IntroductionInstallation@@portlet-data helper viewSetting up aliasSource codeAuthorChangelog1.1 (2012-11-21)1.0 (2012-11-21)Introductioncollective.portletaliasallows “alias” portlets from
other locations to show on the current content inPlone CMS.
This is useful if you need to have the same portlet to be visible in different unrelated locations
and have only one copy where the portlet content is edited and maintaned.InstallationInstall package ascollective.portletaliasand then install in Add on setup.http://plone.org/documentation/kb/installing-add-ons-quick-how-to/NotePlone 4.1+ and Python 2.7 required. Easy to backport for earlier versions if needed.@@portlet-data helper viewAdd/@@portlet-datato URL of any content item to
show debug information about the portlets assigned there.
Admin priviledges needed.NoteIf you have a default item set (like front-page) for the content append
/front-page/@@portlet-data to URL to see all the portlets.Setting up aliasGo to Manage portlets view in the target folderChooseAdd new portlet…Alias PortletEnter the path to the source folderEnter the portlet id of the source portlet. Use @@portlet-data view (above) to
find out portlet assignment nameSource codehttps://github.com/collective/collective.portletaliasAuthorMikko OhtamaaChangelog1.1 (2012-11-21)Fixed setup.py pointers1.0 (2012-11-21)Initial release
Package: collective.portlet.banners
Introduction============collective.portlet.banners provides a portlet to display rotating images,such as sponsor logos, which may be hyperlinked. The images and correspondingURLs are stored in a custom content type called a Portlet Banner. Since bannerimages are stored as blobs, collective.portlet.banners requires that the sitebe using plone.app.blob and plone.app.imaging.Installation============To install collective.portlet.banners, first ensure that your site is usingplone.app.blob and plone.app.imaging. Then add collective.portlet.bannersto the eggs section of your buildout. If you are using Plone 3.2 or earlier,you also need to add a ZCML slug. Then re-run buildout and restart Zope.You can now install the product in your Plone site using the Add/RemoveProducts control panel.Basic Use=========After installing the product, you should see the Portlet Banner type in theAdd New menu. You can add portlet banners anywhere on your Plone site, butall the banners that you want to display on a particular portlet need to bein the same folder. As with all Plone content, portlet banners are only visibleto anonymous users when they are published. If you save a portlet banner andthe image is not displayed, you need to install plone.app.blob andplone.app.imaging from the Add/Remove Products control panel.After creating the banners that you want to display, you can use the bannersportlet. Add the portlet by clicking on Manage Portlets and selecting BannersPortlet from the drop-down menu. Then fill in the form, selecting for thebanner folder the folder where you created the banners. Be sure to also setthe title of the portlet, the delay (in seconds) between images, the fadespeed, the portlet width, and the order of the banners. Note that the widthsetting **does not** resample the images, so it still important to resize andoptimize the images before uploading them.Credits=======Development-----------* `Matt Yoder <mattyoder@groundwire.org>`_Changelog=========1.1 - 2013-09-11----------------- more 4.3 fixes[senner]1.0 - 2013-09-11----------------- use $ instead of jq[lepri]- zope.component.hooks import fix for plone 4.3[senner]- provide ability to not use catalog results for banners. Will beslower but might fix some cases.[vangheem]- fix cataloging banner info. Only index relative urls since absolutewon't work if edit site is different than production and ssl/non-ssl[vangheem]1.0a3 - 2011-06-07------------------- changed the portlet permission to plone.app.portlets.ManagePortlets[vangheem]- fix call to get banners.[vangheem]1.0a2 - 2010-04-02------------------- Removed conditional comment attribute from jsregistry for compatibility witholder versions of Plone.[2010-04-02 - yomatters]- Fixed links to portlet banners in folder contents and added upgrade step.[2010-04-01 - yomatters]1.0a1 - 2010-03-31------------------ Initial work on portlet and content type.[2010-03-18 - yomatters]
Package: collective.portlet.bilingualtext
IntroductionA text portlet with an additional language field. The portlet
will only be show if the current request language matches the
language field.ContactZOPYX Ltd. & Co. KGc/o Andreas Jung,Charlottenstr. 37/1D-72070 Tuebingen, GermanyE-mail: info at zopyx dot comWeb:http://www.zopyx.comChangelog0.3.1 (2008-11-06)i18n fixes0.3.0 (2008-11-04)switching to a one-portlet-per-language implementation0.2.0 (2008-10-31)now support for up to 3 different languages0.1.0 (2008-10-28)Initial release
Package: collective.portlet.calendar
Table of ContentsExtended Calendar PortletOverviewScreenshotRequirementsInstallationContributingSponsoringCredits0.6 (2011-05-19)0.5 (2011-05-06)Extended Calendar PortletOverviewThis package provides a configurable implementation of a Calendar Portlet.It is possible to give the calendar portlet a header, to search only for events
with given keywords and constrain its results to only an area of your site.Even though Plone’s default Calendar Portlet implementation is useful for most
sites if you want to segment calendar’s events or to provide more than one
calendar per page, Extended Calendar Portlet comes to rescue.ScreenshotRequirementsPlone >= 3.3.x (http://plone.org/products/plone)InstallationTo enable this product,on a buildout based installation:Edit your buildout.cfg and addcollective.portlet.calendarto the list of eggs to install[buildout]
...
eggs =
     collective.portlet.calendarAfter 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 only
if you installed it from the quick installer.Note: You may have to empty your browser cache and save your resource registries
in order to see the effects of the product installation.ContributingCode repository and isssue tracker can be found atBitBucketSponsoringDevelopment of this product was sponsored byTRT13.CreditsSimples Consultoria (products at simplesconsultoria dot com dot br) -
ImplementationChangelog0.6 (2011-05-19)Now also Plone 3.3 compatible
[keul]Added Italian translation
[keul]Added Brazilian Portuguese translation
[erico_andrei]Change the translation domain, fixing all the i18ndude stuff
(that were not working), because while using the “plone” ones was not possible
to translate anything.
[keul]Selecting a collection, all other filters are ignored
(if you want a review_state or Subject filter, put it in the collection
itself).
[keul]added and fixed tests
[keul]Minimal pyflakes changes
[keul]0.5 (2011-05-06)Providing a base css to our portlet
[erico_andrei]Allows restricting the results to only a subset of the site
[erico_andrei]Adding portlet name/title
[erico_andrei]Initial release
[erico_andrei]
Package: collective.portlet.carousel
collective.portlet.carouselA portlet to be used within panels (see collective.panels) for creating carousels.The carousel supports the following features:The carousel can be added to any page on the site, by just creating a panel, and
then add the carousel to the panel. In theory, the carousel could also be placed
in the left or right columns.The carousel supports several renderings. By default a dexterity behavior should
be used for creating carousel elements. The behavior can be added to any type,
i.e. a carousel can have elements of any time. Carousel elements can also
be marked using the carousel marker interface, in this case the “Dublin Core”
renderer will be used, but can be customized by registering a “carousel-renderer”
view (for the marker interface should work).The source of the elements in the carousel can vary. Currently, collections and
references can be used as a source of the elements.TODOBasic styling of the different renderings.Better documentation.AuthorsBo Simonsen <bo@headnet.dk>Thomas Clement Mogensen <thomas@headnet.dk>Sune Brøndum Wøller <sune@woeller.dk>Asko Soukka <asko.soukka@iki.fi>Changelog1.1.3 (2018-01-31)Fixes:Fix packaging
[sunew]1.1.2 (27-11-2017)Added MANIFEST to include CHANGES.rst1.1 (22-11-2017)Features:add option to specify an external uri in portlet.
External link will override reference.
[tmog]add option to set timeout in portlet.
[tmog]add new widgets from plone.app.widgets
[datakurre]Fixes:only do rotation if we have more
than one item
[tmog]allow picking old style Topics
[tmog]add BBB for ATTopic
[tmog]add Finnish localization
[datakurre]1.0 (30-12-2013)Initial public releaseFixes:included the plone.behavior meta.zcml file,
so that we get access to the <plone:behavior /> ZCML directive.
[bogdangi]work with plone:master p.a.portlets
[tmog]
Package: collective.portlet.categories
Introduction============This addon provide a portlet to display categories defined bycollective.categories_.How to install==============This addon can be installed has any other addons. please follow officialdocumentation_Credits=======Companies---------|cirb|_ CIRB / CIBG* `Contact CIRB <mailto:irisline@irisnet.be>`_|makinacom|_* `Planet Makina Corpus <http://www.makina-corpus.org>`_* `Contact Makina Corpus <mailto:python@makina-corpus.org>`_People------- JeanMichel FRANCOIS aka toutpt <toutpt@gmail.com>.. |cirb| image:: http://www.cirb.irisnet.be/logo.jpg.. _cirb: http://cirb.irisnet.be.. _sitemap: http://support.google.com/webmasters/bin/answer.py?hl=en&answer=183668&topic=8476&ctx=topic.. |makinacom| image:: http://depot.makina-corpus.org/public/logo.gif.. _makinacom:  http://www.makina-corpus.com.. _documentation: http://plone.org/documentation/kb/installing-add-ons-quick-how-toChangelog=========1.0 (2013-02-15)----------------- Initial release
Package: collective.portlet.collectionbysubject
Collection by Subject Portlet~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Concept - David Bain (david.bain@alteroo.com)Implemented by Rok Garbas (big ups to Rok).Introduction============This portlet makes it possible to present collections grouped by different criteria including:* by Author* by Keyword* by Type* by Location (may require some tweaking)Usage=========Click "manage portlets" and add a new "Collection by subject".Settings include:Portlet header - the title of the portletTarget collection - the collection that the portlet will useGroup by - the subject that you would like to group the items byCache duration - the lenghth of time the results should be cachedThe output looks similar to this::by Keywordfood (4)green (2)drink (4)well (2)sleep (1)Changelog=========0.3 - 2011-12-09----------------* Fix permission used.[vangheem]0.1 - Initial release----------------* FEATURE: [garbas]* FEATURE: [garbas]
Package: collective.portlet.collectionfilter
collective.portlet.collectionfilterFaceted navigation filter for collection results.This portlet allows you to filter collections results for additional catalog
metadata.  For example, you can add a subject filter, but also a filter for
authors or portal types. The “Collection Filter” portlet can be used to build
tag clouds.The filter types can be extended (see:collective.portlet.collectionfilter.vocabularies).Besides the “Collection Filter” portlet there is also a “Collection Search”
portlet for doing a fulltext search on the collection results.This package is a fork ofcollective.portlet.collectionbysubjectby Rok
Garbas.Changelog1.5 (2019-06-27)Don’t break, if no collection is available.
[thet]Update AJAX selectors to content-core and default value for caching
[agitator]1.4.1 (2016-02-04)Fix AJAX loading of collectionfilter result to use the #content node instead of whole document.
[thet]1.4 (2015-12-17)Set the ‘selected’ class on clicked collectionfilter link via JavaScript.
[thet]1.3 (2015-12-15)Plone 5 compatibility.
[agitator]Ajaxification with mockup, if available.
[agitator]1.2 (2015-12-14)Make cache time configurable and set it to 60 seconds instead of an hour.
0 is no caching.
Remove profiling code.
[thet]1.1.3 (2015-09-25)Fix brown bag release.
[thet]1.1.2 (2015-09-25)In the collection filter portlet, don’t count empty values. These cannot be
searched via the catalog. Use an empty marker instead (for an example on theSubjectindex, see the indexer module).
[thet]1.1.1 (2015-09-25)Fix error with rendering the portlet and having an empty subject.
[thet]1.1 (2015-09-25)Add a subject indexer, which adds EMPTY_MARKER to the index, where no subject
is set. Make sure, the EMPTY_MARKER is translated in the portlet.
[thet]1.0 (2015-07-15)Fork from collective.portlet.collectionbysubject and complete refactoring.
[thet]