Saravanan666/pypi-org huggingface dataset:
Package: collective.googleauthentication
GoogleAuthenticationAbout GoogleAuthenticationGA takes care of the user authentication upon Google Docs service, so that the Plone
application can access the documents stored on Google servers.To let the Plone application access the documents stored on Google servers, it is necessary
to complete the authentication procedure for Web applications provided by Google Docs. The
procedure allows Web applications to authenticate users through their Google accounts. For
security reasons, the application acquires an authentication token which will later be used
to dowload or upload documents from Google servers without explicitly providing the user’s
credentials. The Plone user is redirected to a Google page that invites him to insert his
credentials. Once he logs in with his Google account, the user is asked to authorize the
Plone application to access his documents. Then, if the user grants access, he is pointed
again to the Plone site. The URL of the last redirection embeds the authentication token
which, as mentioned above, allows the Plone application to access the user’s documents on
Google servers for the following requests.GA inititates the authentication procedure upon Google Docs immediately after the user has
logged into the Plone application. The procedure will be executed just once, as when the
Plone application obtains the authentication token, it will store as an attribute,
google_token, in the user profile.Copyright and licenseCopyright (c) 2009 Federica D’EliaThis 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 PURPOSESee theLICENSEfile that comes with this product.Requirementsgdata-1.3.0 must be correctly installed.InstallationWith buildoutThis example speaks of itself:[buildout]
...
eggs =
    ...
    collective.googleauthentication
    ...
...
zcml =
    ...
    collective.googleauthentication
    ...
...CreditsMain developer: D’Elia Federica <federica.delia@redturtle.it>Changelog1.0.0Initial release
Package: collective.googlecloudlogging
This library connects to Python’s standard logging module and will log to Googles Cloud Logging via API. More information athttps://cloud.google.com/logging/docs/setup/python#connecting_the_library_to_python_loggingConfigurationWithin Google Cloud no extra configuration should be needed.If you want to use the Cloud Logging outside of Google Cloud, you have to supply your Google Cloud project ID and appropriate service account credentials.NoteAs soon as it’s loaded, and only then, it will remove the StreamHandler from root logger and no longer write to stdout.
If you want no instance logging to stdout at all in your Google Cloud Logs, you have to disable it in yourwsgi.ini:[logger_root]
level = INFO
handlers = console, eventlogRequirementsPlone 5.2Python 3.7InstallationInstall collective.googlecloudlogging by adding it to your buildout:[buildout]

...

eggs =
    collective.googlecloudloggingand then runningbin/buildoutMaintainersPeter HolzerContact:dev@bluedynamics.comContributeIssue Tracker:https://github.com/collective/collective.googlecloudlogging/issuesSource Code:https://github.com/collective/collective.googlecloudloggingLicenseThe project is licensed under the GPLv2.ContributorsPeter HolzerErico AndreiChangelog1.0 (2021-08-05)Initial release.
[agitator]
Package: collective.googledocsviewer
IntroductionGoogle docs viewer is a service provided by google tm:https://docs.google.com/viewerThis add-on add a view on the File content type.  It display the file with the
embed viewer. You can find a live demo at toutpt.makina-corpus.org/add-ons/collective.googledocsviewer/cv-jeanmichel-francois-fr/viewHow to use itAdd a file content in your Plone site, make it publicly available (publish it) and
select the google docs ‘Google Docs viewer’ view in the display drop down menu.Next you can use the the ‘Configure view’ action provided at the bottom of the page
to configure the size of the viewer you want to use.How it worksIt display an iframe built from your file’s url.For example,http://example.com/myfile/viewwill become<iframe src="http://docs.google.com/viewer?url=http%3A%2F%2Fexample.com%2Fmyfile&embedded=true" width="600" height="780" style="border: none;"></iframe>Sizes are stored on site level in plone.app.registry or on context level with annotations.CreditsCompaniesPlanet Makina CorpusContact usAuthorsJeanMichel FRANCOIS aka toutpt <toutpt@gmail.com>ContributorsChangelog1.0b1 (2011-06-25)Initial release
Package: collective.googleforms
IntroductionGoogle provides a service which let you createforms. This add-on let you display
a form from this service in your Plone site.How it worksThis add-on parse the html of the form you have built in google doc withbeautifulsoup.It build a form with the same html markup as archetypes one, so the form seems to be a plone one.The action is the google doc one, so you are redirected to it when submiting.CreditsCompaniesPlanet Makina CorpusContact usAuthorsJeanMichel FRANCOIS aka toutpt <toutpt@gmail.com>ContributorsChangelog1.0a1 (2011-04-23)Initial release
Package: collective.googlelibraries
IntroductionFrom GoogleLibraries:
The Libraries API is a content distribution network and loading architecture for
the most popular, open-source JavaScript libraries.This add-on integrate that google service into PloneHow to useAdd this add-on to your setup configuration and install it as usual:http://plone.org/documentation/kb/add-ons/installingA control panel is provided in the backoffice to let you setup your google
api keys and to choose what libraries you want to include.This add-on serialize the configuration throw the portal_properties. So you can
also configure it throw a generic setup profile.How it worksIt overrides throw a browserlayer the plone javascript resources
iterator. It first add the jsapi if you have a api key setup for your host.The jsapi and libraries are included only if you have provided akey.
A default key is initialized for localhost:8080 and for testing:8080 domainsChangelog1.0b1 (2010-12-08)Initial release
Package: collective.googleloader
IntroductionFrom google:In order to use the Google APIs, you must import them using the Google API
loader in conjunction with the API key. The loader allows you to easily import
one or more APIs, and specify additional settings (such as language, location,
API version, etc.) applicable to your needs.In addition to the basic loader functionality, savvy developers can also use
dynamic loading or auto-loading to enhance the performance of your application.This add-on provide integration of the google loader (aka jsapi) into Plone.
It provides autoupdate of javascript registry depend on hostname. API keys are
stored into plone.app.registry, so you can use the provided control panel to
configure it (adding API keys)Changelog1.0b1 (2011-05-03)Initial release
Package: collective.googlemodifycontent
GoogleModifyContentAbout GoogleModifyContentGMC extends the Plone content Edit function by adding the GoogleModify operation,
which only applies to documents stored on Google servers.GMC embeds the Google Docs application inside the Google Modify panel, allowing Plone users
to edit their documents directly from the Plone application.Copyright and licenseCopyright (c) 2009 Federica D’EliaThis 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 PURPOSESee theLICENSEfile that comes with this product.RequirementsFileSystemStorage, GoogleAuthentication, GoogleSystemStorage and gdata-1.3.0
must be correctly installed.InstallationWith buildoutThis example speaks of itself:[buildout]
parts =
   ...
   fss

...

eggs =
    ...
    collective.googlesystemstorage
    collective.googleauthentication
    collective.googlemodifycontent
    iw.recipe.fss
    iw.fss
    ...

...

zcml =
    ...
    collective.googlesystemstorage
    collective.googleauthentication
    collective.googlemodifycontent
    iw.fss
    iw.fss-meta

...

[fss]
recipe = iw.recipe.fss
zope-instances =
     ${instance:location}

storages =
    global / flat
    portale /portale site1 ${buildout:directory}/var/portale_fss_storage ${buildout:directory}/var/portale_fss_backupCreditsMain developer: D’Elia Federica <federica.delia@redturtle.it>Changelog1.0.0Initial release
Package: collective.googlesharing
GoogleSharingAbout GoogleSharingGS manages the sharing of documents stored in the Google servers and their synchronization
from the Plone application to Google Docs service. In this way, when a Plone user changes
the roles of other users on a specific document, for instance to share the document with
them or to restrict their access to the document, GS changes the document sharing attributes
in the Google Docs service accordingly. So, if a Plone user assigns another user the Editor
role on one of his documents, the other user will be able to read and modify that document
through his Google account.To associate Plone and Google accounts, GS assumes that the email address attribute of Plone
users corresponds to their Google account.The mapping of roles, on each specific document, from Plone to Google Docs is based on the
following rules: Plone users who have both the Editor and the Reader roles on a specific
document are assigned the writer role on the correspondent document on Google servers; Plone
users who have the Editor or the Reader roles are assigned the writer or reader role,
respectively, on the correspondent document on Google servers. The Collaborator and Reviewer
roles have not been considered.Copyright and licenseCopyright (c) 2009 Federica D’EliaThis 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 PURPOSESee theLICENSEfile that comes with this product.RequirementsFileSystemStorage, GoogleAuthentication, GoogleSystemStorage and gdata-1.3.0
must be correctly installed.InstallationWith buildoutThis example speaks of itself:[buildout]
parts=
  ...
  fss

...
eggs =
  ..
  collective.googlesystemstorage
  collective.googleauthentication
  collective.googlesharing
  iw.recipe.fss
  iw.fss
  ...
...
zcml =
  ...
  collective.googlesystemstorage
  collective.googleauthentication
  collective.googlesharing
  iw.fss
  iw.fss-meta
  ...
...

[fss]
recipe = iw.recipe.fss
zope-instances =
     ${instance:location}

storages =
    global / flat
    portale /portale site1 ${buildout:directory}/var/portale_fss_storage ${buildout:directory}/var/portale_fss_backupCreditsMain developer: D’Elia Federica <federica.delia@redturtle.it>Changelog1.0.0Initial release
Package: collective.googlesystemstorage
GoogleSystemStorageAbout GoogleSystemStorageGoogleSystemStorage (GSS) is an extension of FileSystemStorage (FSS).GSS transparently to the user, saves the document types supported by the Google Docs service
on the Google servers, while storing all the other files in the local filesystem.GSS permits Plone users to access their files from both the Plone application and their
Google Docs account.In addition, GSS permits to overcome the problem of ZODB size growth, and the consequent
performance penalties, when many files with large size are used.Copyright and licenseCopyright (c) 2009 Federica D’EliaThis 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 PURPOSESee theLICENSEfile that comes with this product.RequirementsFileSystemStorage, GoogleAuthentication and gdata-1.3.0
must be correctly installed.InstallationWith buildoutThis example speaks of itself:[buildout]
parts =
    ...
    fss

...

eggs =
  ...
  collective.googlesystemstorage
  collective.googleauthentication
  iw.recipe.fss
  iw.fss
  ...

...

zcml =
    ...
    collective.googlesystemstorage
    collective.googleauthentication
    iw.fss
    iw.fss-meta

...

[fss]
recipe = iw.recipe.fss
zope-instances =
     ${instance:location}

storages =
    global / flat
    portale /portale site1 ${buildout:directory}/var/portale_fss_storage ${buildout:directory}/var/portale_fss_backupCreditsMain developer: D’Elia Federica <federica.delia@redturtle.it>Changelog1.0.0Initial release
Package: collective.greybox
Simple python package for Plone, whiches makes the gre(a)ybox available for imagesINSTALLwatch docs/INSTALL.txtTESTED WITHPlone 3.x
Zope 2.10.5CONTACTinfo (a) 4teamwork.ch
m.leimguber (a) 4teamwork.chHISTORY0.4updated package metadata [mathias.leimgruber]0.3fixes0.2create marker interface for the greybox view
using js and css registry. [mathias.leimgruber]implemented new css for the plone listing looks much better.
[espen@medialog.no]0.1rc1Initial release [mathias.leimgruber]use plone default viewlet Manager
(instead of deprecated slots) [mathias.leimgruber]
Package: collective.gridlisting
collective.gridlistingAdds a Behavior to manipulate various listing appearance settings
using Bootstrap 5 (column layout) and patternslib (masonry).This behavior is automatically enabled for “Folder” and “Collection” when you install it.FeaturesAdds new view template “Grid listing” for “Folder” and “Collection”You get a new “Grid listing” tab when editing a Folder or a Collection where
you can set various options for the listing template.Get startedInstallcollective.gridlistingin the Add-ons controlpanelGo to a folder and selectGrid listingfrom theDisplaymenuEdit the folder and go to theGrid listingtabYou can enter CSS classes for the grid items and/or enableMasonry layout.Grid setupThe grid structure is set up as follows:Container rowColumnColumn contenttextimageYou can define css classes for each of those containers.For example if you simply want a responsive 4/2/1 column layout you can set theContainer row CSS classto:row-cols-1row-cols-lg-2row-cols-xl-4You can also define borders, margins and paddings for the column content withColumn content CSS Class:borderborder-primarym-2p-2And you can further experiment with gutters or backgrounds.Inside the column, the text and image information can be defined separately.
You can for example simply switch the order of text/image with:Column content text: colorder-2Column content image: colorder-1or put the image above the text with:Column content text:col-12order-2Column content image:col-12order-1For more information on the CSS definitions see the Bootstrap documentation:https://getbootstrap.com/docs/5.3/layout/grid/Special Example: Card listingThe following values gives you a listing with cards, cell height 100% and image at the top:Container row:row-cols-3(3 columns)Column:pb-3(spacing below card)Column content:cardh-100(card outline, 100% cell height)Column content text:order-2card-body(text below image)Column content image:order-1card-img-top(image above text)et voila!NOTE: If you enableMasonry layoutyou have to removeh-100fromColumn contentand you have a masonry card listing like shown here:https://getbootstrap.com/docs/5.3/examples/masonry/TranslationsThis product has been translated intoEnglishGermanInstallationInstall collective.gridlisting by adding it to your buildout:[buildout]

...

eggs =
    collective.gridlistingand then runningbin/buildoutCompatibilityPlone 6, Python 3.8 - 3.11ContributeIssue Tracker:https://github.com/collective/collective.gridlisting/issuesSource Code:https://github.com/collective/collective.gridlistingDocumentation:https://github.com/collective/collective.gridlisting/docsLicenseThe project is licensed under the GPLv2.ContributorsPeter Mathis,peter.mathis@kombinat.atChangelog1.0.0 (2023-06-28)Initial release. See REAMDE.rst
[petschki]
Package: collective.groupdashboard
IntroductionThis package adds the ability to manage dashboard portlets on a per-group
basis. Once installed, a site manager will be able go to the “Group Portlets”
tab when editing a group and then click the “Edit group dashboard portlets”
link. From here, group dashboard portlets can be assigned as normal.Any member in that group will then see the relevant portlets on their
dashboard. Note that group portlets will appear below the user’s own portlets.To make it easier to lock down the dashboard, the view and edit permissions
have been separated. You can take away the “Portlets: Manage own portlets”
permission to let users view the dashboard without the ability to edit it.InstallationInstall as normal. You will need to load a ZCML slug unless you are using
Plone 3.3, in which case it should be loaded automatically.If you get a version conflict in zope.component or similar, add this to
your versions block:[buildout]
...
versions = versions
...

[versions]
...
zope.component = 3.4.0
zope.securitypolicy = 3.4.0
...Changelog1.0b2 - 2009-04-15Fix a bug related to the ability to remove or re-order portlets.Update templates to properly set the region-content id1.0b1 - 2009-03-25Initial release
Package: collective.groupdelegation
Group DelegationA customization of some Plone Groups Management screens, and some new templates
and scripts added, providing the delegation of Groups management in Plone for any
member without ‘Manager’ role.This code was originally published by Ingeniweb in Grufspaces product and has been
upgraded for plone3.x compliance, some tests have also been added.How to use this product :add collective.groupdelegation to your buildout (see docs/INSTALL.txt for more information)Intall “Group Delegation” in your plone site using portal_quickinstallerGo to Users/Groups management control panels,  Create a group and some users.Choose the group you want to delegate managementClick on “Group Managers” tabSearch for, and choose the user you want delegate the group management to.Connect to your site with this user credentialsA “My groups” tab will appear in personal tools, click on this linkThe group will appear in listClick on this group link, now you can manage it without Manager rights.TODO : Security issuesAt this time no special zope security or role is needed to manage groups in Plone. The
process is only protected by a condition “chekPermission(‘Manage portal’)”” inside
templates.This product is following the same logic, it’s just a skin product ,
the only thing done to allow/disallow groups management is a new property added to groups.To improve security it could be useful to add a new specific zope security
“Manage groups”, only allowed to a “Group manager” new role.Then, when choosing the group manager, could it be possible to allow/disallow the local role
to a specific user on a specific group ? i don’t know.TODO : template and python scripts redesignAt this time this product is using actual Plone groups management templates and scripts because
it is using the same methods to search/add/remove groups members, redesigning
this product would mean first a complete redesign of plone templates, a big work that could
be done in future …For more information read the doctest (readme.txt) inside product.Changelog0.4 - 2010/07/22fix docs folder is missing in package0.3 - 2009/07/10Updated french translation.
[vincentfretin]Added entry point to declare the product as plone plugin.
[vincentfretin]Added profiles/default/groupdelegation_marker.txt to avoid to reexecute setupGroupDataDelegation when another product is installed.
[vincentfretin]Synced with latest Plone 3.3 templates.
[vincentfretin]0.2 - 2009-06-26context/@@authenticator was missing in prefs_group_members overload (used in last plone 3.x versions)
[macadames]prefs_group_members overload uses the same presentation as last plone 3.x template
[macadames]link to controlpanel removed in prefs_delegated_groups_overview.cpt template
[macadames]0.1 - 2009-06-18Initial release
[macadames]
Package: collective.groupmail
Introductioncollective.groupmail is a way to send an email to all users in the group. It
overrides the Member search (in the Users folder) to also return groups, and
adds the group details view so that it contains the same type of contact form
that the user overview does. This enables you to send an email to the whole
group.If the group has a configured email-address, that adress will be used. If
not, each member will have their email address looked up, and the email sent
to that member.Separate emails are sent, so that the reply will go only to the sender and
not to everyone. If you want it to go to everyone, you need to set up a
mailing list, and add the address of that list to the group properties.InstallationAdd collective.groupmail to the eggs= list in your buildout. Re-run buildout,
restart the server. All sites in the server will get this functionality. In
the future it is planned to add a layer so that you need to install the
product, but because of lack of time this will wait to a future release.LicenseGPL, see docs/LICENSE.GPLContributorsLennart Regebro,regebro@gmail.comChangelog1.1 (2013-08-22)Added number of members to member view.1.0.1 (2013-06-25)Re-release.1.0 (2013-06-25)List group members on group contact page.1.0a3 (2012-09-23)Use a separate view to view groups, that only requires the “View Groups” permission. [regebro]1.0a2 (2012-09-21)First release to Cheeseshop. [regebro]1.0a1 (2012-09-21)Initial release. [regebro]
Package: collective.groupspace.content
IntroductionImplements a folderish content type that implements the ILocalGroupSpacePASRoles
interface, This interface allows managemment of dynamic roles for users and groups
in a context, and is implemented in collective.groupspace.roles.This package is part of the collective.groupspace suite, whose components should
be installed as needed:collective.groupspace.workflowcollective.groupspace.rolescollective.groupspace.mail1.0.2 (2011-07-02)FeaturesAdded FR translations for content type GroupSpace (title & description) (jstegle)Internaladd a zope2 permission because real install failed in plone3.3.5 (yboussard)fix text1.0.1 (2010-01-10)FeaturesChanging GroupSpace logo to group.gifInternalSet typesLinkToFolderContentsInFC for GroupSpace to support FCKEditorUnit test coverage increased1.0 (2009-11-07)Initial release.
Package: collective.groupspace.mail
IntroductionImplements a mail tab for any content type implementing the ILocalGroupSpacePASRoles
interface, This interface allows managemment of dynamic roles for users and groups
in a context, and is implemented in collective.groupspace.roles. An example content
type providing a mail tab is contained in collective.groupspace.content.The tab looks like the standard Plone “Send this page to someone” interface, but
instead of manually filling in an email address, you can choose the recipients of
the message from a list of participants that have a role in the context of
your content type.This package is part of the collective.groupspace suite, whose components should
be installed as needed:collective.groupspace.contentcollective.groupspace.rolescollective.groupspace.mail1.0.1 (2011-07-02)FeaturesAdded FR translations. (jstegle)spanish translation (enriquepablo)get request from event rather than from objectBug FixesChanged roles.py for Plone 4.0 Compatibility (there was an AttributeError on context.request) (jstegle)Translation of groupmail portlet title wasn’t working correctly. (jstegle)ignore.egg-infoto not makemr.developerthink of dirty packages too much (witsch)1.0 (2009-10-28)Initial release.