Saravanan666/pypi-org huggingface dataset:
Package: collective.megaphonecicerolookup
IntroductionAzavea’sCicero APIcan be used to look up the elected officials
for a given address.collective.megaphonecicerolookupintegrates this
functionality with theMegaphoneonline advocacy tool, so that recipients
of Megaphone letters and petitions can be found via a Cicero lookup based
on the address entered by the user.NoteIf Cicero returns an e-mail address for the official, Megaphone can
deliver the message directly.  However, some officials only publicize
web forms for accepting messages. In this case, Megaphone will record
the letter but can’t deliver it.Megaphone will also record but not deliver the letter if it is unable
to find an elected official for the given address (if data is unavailable
for the given address or if Cicero cannot be reached.)Installationcollective.megaphonecicerolookuphas been tested with Plone 4.Adding to buildoutcollective.megaphonecicerolookuphas several dependencies. These should get
pulled in automatically if you add the collective.megaphonecicerolookup egg to your
buildout. _However_, you need to make sure that you get versions of the
dependencies that are compatible with your version of Plone. To do so, you may
extend the following known good set of version pins:[buildout]
extends = http://good-py.appspot.com/release/collective.megaphone/2.1?plone=4.0.1

[instance]
...
eggs =
    ...
    collective.megaphonecicerolookupOf course, you may need to adjust the specified Plone version, or create a
derivative set of version pins if the ones in this set conflict with those
recommended for some other add-on.Activating the add-onAfter running buildout and starting your Zope instance, install
collective.megaphonecicerolookup via the Add-ons control panel in Plone
Site Setup.Now go to theConfiguration registrycontrol panel and configure your
Cicero API username and password.UsageAdd a new Megaphone Action. Select the ‘letter’ type and continue through
the wizard. (Megaphone petitions do not have specific recipients.)When you reach the Recipients step of the wizard, click theAdd Recipientbutton.Ifcollective.megaphonecicerolookupis correctly installed, you can now
choose to add a recipient of theCicero lookup: address to officialtype.Configure the lookup by specifying the label that will be shown to the user
sending a letter and the type of official you want to look up.You may optionally specify a set of states for which lookups will be
performed. If you do so and the user chooses a different state, their letter
will be recorded but without a specific recipient.  If you leave this option
blank, lookups will always be attempted.Changelog1.0.1 (2011-02-15)Fix handling of WebFaults from Cicero.
[davisagli]1.0 (2011-01-11)Log a warning instead of raising an exception if the form submission is
missing required fields (street, city, state, zip).
[davisagli]1.0b2 (2010-10-18)Don’t break Megaphones without a Cicero lookup source if they are missing
fields required by the Cicero lookup source.
[davisagli]1.0b1 (2010-10-14)Initial release
[davisagli]
Package: collective.megaphonesql
IntroductionThis product integratesProducts.sqlpfgadapterintocollective.megaphone.For now, all it does is add “SQLPFGAdapter” to the addable types in a
“Megaphone Action” (megaphone 2) or “Action Letter” (megaphone < 2).In the future, the sql storage might be a step in the megaphone wizard, which
this product could provide.CompatibilityRequires Products.sqlpfgadapter >= 0.1a2.Should work on Plone 3 and Plone 4, collective.megaphone 1.x and 2.x.Tested on Plone 3.3.5 with collective.megaphone 2.0b1 and
Products.sqlpfgadapter 0.1a2.Changelog1.0 (2011-01-10)No functional change0.1a1 (2010-09-22)Initial release
Package: collective.memberapproval
collective.memberapproval provides a user interface for
pas.plugins.memberapproval. Together these products form a member approval
process, making it possible to approve or disapprove member registrations to
your website.Management viewscollective.memberapproval providess the following management views:@@usergroup-userprefs: collective.memberapproval overrides the standard
user management view with one that extends the standard view with a filter
to list only Approved, only Disapproved or All users.@@user-approval: This view will allow you to view and change the status of
a specific user. You access it with the parameter ‘userid’, iehttp://localhost:8080/Plone/@@user-approval?userid=theusername@@user-approve: This view will approve the specified user. It does not
provide any HTML view, but is usable for services such as providing
a direct link to approve users from a notification email. Example:http://localhost:8080/Plone/@@user-approve?userid=theusername@@user-disapprove: This view will disapprove the specified user. It does
not provide any HTML view, but is usable for services such as providing a
direct link to disapprove users from a notification email. Example:http://localhost:8080/Plone/@@user-disapprove?userid=theusername@@user-approved: This view will return True if the user specified is
approved, or None otherwise. It does not provide any HTML view. Example:http://localhost:8080/Plone/@@user-approved?userid=theusernamecollective.memberapproval InstallationAddcollective.memberapprovalto the list of eggs to install, e.g.:[buildout]
...
eggs =
    ...
    collective.memberapprovalRe-run buildout, e.g. with:$ ./bin/buildoutInstall the product into the Plone site from the Add-ons control panel.ContributorsRadim Novotny, AuthorLennart RegebroChange history1.0 (2014-01-31)Added support for Plone 4.3.1.0rc2 (2012-06-27)Added new registered.pt and registered_notify_template.pt templates that
includes information that the registration needs to be approved before you
can sign in.1.0rc1 (2012-06-26)There are now three states: Pending, Approved, Disapproved. You can this
way show all pending users. You can only approve or disapprove users, you
can not make them pending once they have been approved or disapproved.Having an approval link in the tabs confused the users, so I removed it.Added a “Disapprove & Delete” button at the request from users.Changed @@user_approved to @@user_approved for consistency.1.0b1 (2012-05-31)Fixed the tests. [regebro]1.0a1 (2012-05-29)Initial release
Package: collective.membercriterion
IntroductionThis package adds a new criteria type for the Collection type (aka Topic). By
default, the crtieria is available for the ‘Categories’ (aka Subject) index,
but it could be enabled for most index types.When added to a collection, the criteria is configured with a member property
that will be used to find content. The member property is based on the
properties of the current user, although it is unlikely that other users
will have different properties.When the collection is viewed, this criteria will search for content where
the index matches the value of the member property for the current user.The original use case for this functionality was to find content the user may
be interested in: the user specifies a list of “interesting” keywords in his
profile. The collection is used to show content matching his interests.Changelog1.0b3 - 2010-12-30MemberDataCriterion implements IATTopicSearchCriterion. Without this
a criterion won’t appear on a Collection’s criteria edit form.
[danjacka]1.0b2 - 2009-03-20Fix typo that crept into 1.0b1.
[optilude]1.0b1 - 2009-03-20Initial release
Package: collective.memberemails
collective.memberemails will send email notifications for the steps of
the approval process implemented by pas.plugins.memberapproval.It will send an email to a configurable administrator email address
when a user is registered, and it will also send an email to the
user when the user is approved or denied.The emails and the administrator notification address is configured
in the “Member registration email settings” control panel at the url
<yourhost>/@@memberemails-settingsContributorsLennart Regebro, AuthorChangelog1.0a2 (2012-06-26)Now handles the separation between pending and disapproved statuses.Checking the login time was not reliable, and is no longer needed.1.0a1 (2012-05-31)Initial release
Package: collective.metadataaudit
collective.metaaauditlogs metadata changes to Plone content objects transparently
(for all content types). This add-on in in particular useful when you have to answer
the question “who was doing what and when”.Install and use this add-on with care. In particular ensure that its usage is compliant
with your local privacy and data-protection legislation.Featureslogs all metadata changes (create and edit operations) for all Plone content types
(Dexterity content-types only)InstallationInstall collective.metadataaudit by adding it to your buildout:[buildout]

...

eggs =
    collective.metadataauditand then runningbin/buildoutUsageUse theLoggingentry from the Plone toolbarContributeIssue Tracker:https://github.com/collective/collective.metadataaudit/issuesSource Code:https://github.com/collective/collective.metadataauditLicenseThe project is licensed under the GPLv2.AuthorAndreas Jung (info@zopyx.com)ContributorsAndreas Jung,info@zopyx.comChangelog1.0a1 (2020-11-23)Initial release.
[zopyx]
Package: collective.metarobots
IntroductionThis addon add a tag <meta name=”robots”… /> and let you specify values
site wide depending on the hostname.More information on this meta:http://support.google.com/webmasters/bin/answer.py?answer=79812https://developers.google.com/webmasters/control-crawl-index/docs/robots_meta_tagThis addon has been created to not index content from staging webiste.Warning: this addon suffer from a Plone bug:https://dev.plone.org/ticket/13158Use casesstaging or private websiteIf you want your content not to be indexed, you just have to select
‘noindex’ and ‘nofollow’ in configuration.content with end dateIf you manage job proposal content or events, you can choose
“unavailable_after_end” in configuration.CreditsCompaniesPlanet Makina CorpusContact Makina CorpusAuthorsJeanMichel FRANCOIS aka toutpt <toutpt@gmail.com>Changelog1.1.1 (2012-09-03)Fix issues when “unavailable_after_end” not in value1.1 (2012-09-03)Add a controlpanel because ofhttps://dev.plone.org/ticket/131581.0 (2012-09-03)Initial release
Package: collective.microdata.contentlisting
IntroductionThis package is a Plone add-on for sites wherecollective.microdata.coreis installed. See the
product’s page for more information aboutmicrodataandschema.org implementation.You could like to install this product when you need to get a set of microdata informations from your
folder contents pages.However this product only provide basic views implementation for theThingvocabulary. A 3rd party
product could extend it for additional vocabularies.An implementation example could be taken from looking atcollective.microdata.eventLimitation and know issuesThis package is a bit experimental and it overrides a couple of Plone views:“Standard view” (folder_listing)“Summary view” (folder_summary_view)Also:(right now) those views can’t be used anymore for full objects (only brains).this is not working on Plone site root (original views will be loaded).How to extendInstead of directly displaying how a single content looks like, the provided view of this product will look
before for 3rd party implementations.The customized view you are using on your folder will read from the current catalog brain themicrodata_itemtypemetadata, then a view with a special name is searched.The name must be something like “VOCABULARY_URL VIEW_ID_item”.For example, if the current content is providing the Person vocabulary (http://www.schema.org/Person)
and you are listing it in the Plone “Standard view” (folder_listing), the view used for displaying the
single entry will be named “http://www.schema.org/Personfolder_listing_item”.If this view is not found, the brain will be displayed with default views, provided with the product, that
will display the content in the standard Plone way.Changelog0.1 (2012-09-08)Initial release
Package: collective.microdata.event
IntroductionInstall this package and get an alternative version of event view in your Plone site. Changes are minimal,
just to add basic HTML 5microdatainformation, taken fromschema.orgspecification.Microdata available in Web pages can be used from search engines, enhancing the quality of information indexed.This package is a proper implementation of thecollective.microdata.coreproduct. Read it’s documentation
for more information.DetailsFollow a list supported properties:nameTaken from event titledescriptionTaken from the event descriptionurlTaken from the event URL fieldattendeesTaken from Attendees field (raw data, not asPersonelements)locationTaken from event locationstartDateTaken from the start dateendDateTaken from the end datedurationTaken from the difference from end and start dateSupport for folder content listing viewsThis package supports alsocollective.microdata.contentlistingbut not depends on it
(you have to manually install that add-on yourself).Then you will be able to provide microdata information about events also when listing folders content.See it’s documentation for knowing what views are supported.Final notesProviding microdata doesn’t ensure that search engines will use it.Changelog0.2 (2012-09-08)Now requirescollective.microdata.core[keul]Moved logic to aIMicrodataVocabularyadapter [keul]Added a dependency toisodatelibrary, to be able to
generate ISO 8601 duration format [keul]Added support forcollective.microdata.contentlistingPlone catalog will now index the “Event URL” data inside thegetRemoteUrlmetadata column [keul]Adaptation must be based onIMicrodataVocabulary, for support
also non-schema.org vocabularies [keul]0.1 (2012-07-22)Initial release
Package: collective.miscbehaviors
IntroductionThis package provides several simple behaviors for dexterity which
are similar to what already provided by some plone basic contenttypesBehaviorsBody TextAdds a rich text fieldFile AttachmentAdds an attachment fieldLead ImageAdds an image field and an image caption fieldRemote URLAdds a link fieldContact InfoAdds contact name, contact email, and contact phone fieldsPaypalAdds paypal related fields and allow assigning of paypal portletStartEndDateAdds startDate and endDate fields for eventsChangelog0.2.2 (2013-01-08)added initial Finnish translation [koodamo]added default viewlet for leadimage [izhar]0.2.1remove plone.indexer registration for bodytext, as it conflicts with
dexteritytextindexer0.2Added leadimage portletEnable behavior marker interfacesAdded paypal behaviorAdded startenddate behavior0.1Initial release
Package: collective.monkeypatcherpanel
Introductioncollective.monkeypatcherpanel is the Zope 2 companion of Martin Aspeli’scollective.monkeypatchercomponent.It just add a ZMI control panel that shows what monkey patches have been applied
in case you cannot see the logs or grep through the ZCML of your Zope
instance. Open the control panel of your Zope instance and then the “Monkey
Patches” control panel.Requirementscollective.monkeypatcherpanel has been developed and tested with Zope 2.10,
Zope 2.11 and Zope 2.12. It may run on Zope 2.9 but this is untested and not
supported unless you provide a patch that keeps the tests smiling.Of course, we requirecollective.monkeypatcher. If you installedcollective.monkeypatcherpanelwith easy_install or a zc.buildout, you’re done.InstallationIn yourbuildout.cfgfile, add this:[instance]
recipe = colective.recipe.zope2instance
...
eggs =
    ...
    collective.monkeypatcherpanel
    ...
zcml =
    ...
    collective.monkeypatcherpanel
    ...Re-run your buildout then browse as Manager tohttp://<zope-root>/@@add-monkeypatcherpanelto add the control panel in your
Zope 2 instance.UninstallBrowse as Manager tohttp://<zope-root>/@@remove-monkeypatcherpanelthen
removecollective.monkeypatcherpanelfrom your buildout configuration or
file system. Otherwise you’ll keep a broken object in your Zope 2 control panel.LicenseCopyright (c) 2009-2010 - Gilles LenfantThis software is subject to the provisions of the GNU General Public License,
Version 2.0 (GPL). A copy of the GPL should accompany this distribution. THIS
SOFTWARE IS PROVIDED “AS IS” AND ANY AND ALL EXPRESS OR IMPLIED WARRANTIES ARE
DISCLAIMED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF TITLE,
MERCHANTABILITY, AGAINST INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSEThe full text of the GPL v2 license ishere.CreditsGilles LenfantMaik RoederThe icon has been stolen to theTango Desktop Project.Changelog1.0.4completed MANIFEST.in such it includes collective/monkeypatcherpanel/version.txt
(breaked setup.py)
[glenfant]added missing MANIFEST.in file
[keul]1.0.3added z3c.autoconfigure.plugin entry point
[ajung]1.0.2Unified and simplified the way to install our control panel since it seems
very different fom a Zope version to another one. See README.txt.
[glenfant]Registering the patch event handler as soon as possible in the Zope 2 start,
otherwise we’re missing some monkey patches.
[glenfant]Test removed because the control panel is not added automatically.1.0.1Really fixing for Zope 2.12
[glenfant]All (class init, icon, security, meta_type) done through ZCML
[glenfant]1.0.0Version 1.0.0-rc1 stable enough to make a final releaseNormalized indentation [glenfant]1.0.0-rc1Fix import for Zope 2.12 [maikroeder]1.0.0-alpha1Initial release
Package: collective.mosaicpage
A page with Mosaic selected as only layoutFeaturesAdds a portal_type MosaicPage.This is a Container, where you can add Images.Thelayout_viewfromplone.app.mosaicis the only possible layout.On install, the layout behaviors and views are removed from all other portal types.
We remove the layout property from all content items that havelayout_viewas layout:
they will use the default view again.Only Manager and Site Administrator can add MosaicPages.
Editors can still edit them.InstallationInstall collective.mosaicpage by adding it to your buildout:[buildout]

...

eggs =
    collective.mosaicpageand then runningbin/buildout.ContributeIf you are having issues, or want to contribute a bugfix or feature, please let us know.Issue Tracker:https://github.com/collective/collective.mosaicpage/issuesSource Code:https://github.com/collective/collective.mosaicpageLicenseThe project is licensed under the GPLv2.ContributorsMaurits van Rees,maurits@vanrees.orgChangelog1.0.0a3 (2023-08-31)Patched plone.app.mosaic.widget.LayoutWidget: do now enable on add forms.
[maurits]Add layout html for MosaicPage, and hide basic layout.  [maurits]1.0.0a2 (2023-07-21)In our typeinfo, usecontenttype/mosaicpageas icon.
We have defined this in the registry, so we can use it.
[maurits]1.0.0a1 (2023-06-23)Initial release.
[mauritsvanrees]
Package: collective.mosaictraining
This add-on creates a new unpublished folder called Mosaic User Training Guide.Uninstalling this will not remove the Mosaic User Training Guide folder.Re-installing the add-on will recreate any missing pages of the training guide without overwriting existing onesIf the Mosaic User Training Guide folder is renamed or deleted, re-installing the add-on will recreate a new folder.InstallationInstall collective.mosaictraining by adding it to your buildout:[buildout]

...

eggs =
    collective.mosaictrainingand then runningbin/buildoutContributeIssue Tracker:https://github.com/collective/collective.mosaictraining/issuesSource Code:https://github.com/collective/collective.mosaictrainingLicenseThe project is licensed under the GPLv2.ContributorsAnnette Lewis,annette@sixfeetup.comKim Nguyen,kim@sixfeetup.comChangelog1.0 (2021-09-07)Initial release.
[tkimnguyen]
Package: collective.mrwiggin
ContentsIntroductionImportantDetailed documentationToDoChangelogAuthorsMr. Tid (Graham):Now, gentlemen, we have two basic suggestions for the architectural design of
this residential block, and I thought it better that the architects themselves
demonstrate the particular advantages of their designs. Ah! That’s probably the
first architect now. Erm, Mr. Wiggin of Ironside and Malone.Mr. Wiggini(John):Good morning, gentlemen. This is a model of a 12-storey
block combining classical neo-Georgian features with the efficiencies of modern
techniques.read the rest ofArchitect’s Sketch:IntroductionLetcollective.mrwigginbe your plone site architect and provide you with
flexibility to structure your sites with the power of portlets. It also provides
you with easy plugin methods you can use to define new layouts now with Plone
3.x and later. [so you dont have to wait for Deco :P /me hides]ImportantThis is alpha release of mrwiggin. Documentation as well screencast in on its
way so please come back when package gets to out of alpha or proceed with
reading the code.Detailed documentationstill to come … but please feel free to kick my butt if i forget to fill this
space with some useful info.ToDoalso try regex expessions when comparing page to url. this would for example
provide that only edit paged will have different layouts.Changelog0.1 - not releasedinitial infrastructureAuthorsRok Garbas- garbas
Package: collective.multifilesextender
IntroductionThis package lets you add a archetypes.multifile field into any archetypes object using schemaextender.UsageInstall package by adding the egg into your buildout cfg:[instance]
...
eggs =
        collective.multifilesextender
zcml =
        collective.multifilesextenderRerun buildoutTo turn it on, mark desired type with IMultiFileExtendable marker interface. For instance the following adds multifile field into ATDocument. You can put it into any zcml that is included when you start instance:<five:implements
class="Products.ATContentTypes.content.document.ATDocument"
interface="collective.multifilesextender.interfaces.IMultiFileExtendable"
/>Start the instanceInstall it via QuickInstallerTODOAdd some testsCreditsPackage developed by Matous Horahttp://dms4u.czChangelog
=========1.1 - (2009-10-23)added danish translatation1.0 - ReleasedInitial release
Package: collective.multilanguagefields
IntroductionCaution!This package is still in a public experimentation phase.This package aims to provide a simple way to make some fields on a dexterity
content type available in more than one language (“multilanguage”).
It tries to do what raptus.multilanguagefields does for Archetypes content
types.AssumptionsIt should be possible for a site to add a new supported language without
having to migrate content.
(A modification in the code for your customer-specific package would be ok.)UsageMultilanguage text line:from collective.multilanguagefields.fields import TextLine as MLTextLine
from plone.supermodel import model

class IMyType(model.Schema):

    some_text = MLTextLine(
        title=_(u"Fieldname"),
        required=True,
    )FeaturesCompatibilityPlone 4.3 and upwards.Making Title field multilanguageYou cant use the defaultplone.app.content.interfaces.INameFromTitlebehavior.
Instead, usecollective.multilanguagefields.interfaces.INameFromMultiLanguageTitleIn addition, your content type needs to implement its ownTitle()method
which takes into account that the title attribute contains a dictionary.
Theml_valuemethod fromutils.pymight be helpful.Using multilanguage fields in templatesYou can do this as follows:<span tal:content="context/ml_value/my_field" />You can also specify a default value:<span tal:define="ml_value context/ml_value"
      tal:content="python: ml_value('my_field', 'no translation found')" />Changelog0.7 (2016-01-22)Don’t raise DefaultLanguageMissing when field is not required and no other values are given.[moverkamp]0.6 (2015-01-05)Nothing changed yet.0.5 (2015-01-05)Nothing changed yet.0.4 (2015-01-05)Nothing changed yet.0.3 (2015-01-05)Nothing changed yet.0.2 (2015-01-05)Nothing changed yet.0.1.1 (2015-01-02)Nothing changed yet.0.1 (2015-01-02)Initial release