Saravanan666/pypi-org huggingface dataset:
Package: collective.transform.txt2tags
IntroductionThis package gives Plone users the ability to use txt2tags syntax in their Plone site.Txt2tags documentation can be found inhttp://txt2tags.sourceforge.net.In this transform the first three lines of txt2tags files are ignored letting Plone setting the title, author, etc.InstallTo install collective.transform.txt2tags with buildout do the following:[instance]
eggs = collective.transform.txt2tags
zcml = collective.transform.txt2tagsTo write content in txt2tags format you must do the following:Run the ‘Txt2tags Transform Install’ profileGo to Site setup -> markupMake sure the text/x-txt2tags transform is enabledSet your default editor to ‘Plain Text’To uninstall, run the ‘Txt2tags Transform Uninstall’ profile and remove the package from your buildout.Changelog1.1Add support for plone 4.1Improve txt2tags calls based on module-body.py sampleBugfixes
[shagi]1.0Initial release
[shagi]
Package: collective.traverse
IntroductionThis product provides a utility that returns a object which provides
a given interface. The returned object could be the given object or
any object down the path towards the root.>>> from collective.traverse.interfaces import ITraverse
>>> from somewhere import IMyInterface
>>> root_traverser = getUtility(ITraverse, name="rootTraverser")
>>> myType = root_traverser(self.context, IMyInterface)InstallationAdd this to your buildout:[buildout]eggs = collective.traverse[instance]zcml = collective.traverseAnd then run buildout.Changelogcollective.traverse - 1.1 [20090605]Fixed a recursion bug when using portal_setup. There, somehow parent == context ;) [Daniel Kraft]collective.traverse - 1.0 UnreleasedInitial package structure.
[zopeskel]
Package: collective.twitter.accounts
Table of ContentsOverviewUsageTwitter ApplicationsActually posting or getting to/from TwitterInstallationContributorsChangelog1.0.3 (2012-04-10)1.0.2 (2012-04-10)1.0.1 (2011-07-26)1.0.0 (2011-07-25)OverviewThis product allows you to addTwitteraccounts to a Plone site.It uses oAuth authentication.UsageGo to the “Site Setup”, then to the “Twitter” tool.Choose wether to use Plone’s default twitter application (PloneTweet) or a
custom one.If you choose to use a custom Twitter application, enter your consumer key
and secret for it.Click on “Request Twitter token”.A new link should’ve appeared below “Allow permission to your account”.
Click it in order to allow the app to use your Twitter account.Copy the given token into the “Token” input field.Click “Add”.If something went wrong, you need to click on “Request Twitter token” and
the following link to get a new token and try again.Done.If you want to remove an account, simply click on its red cross next to its
name. Be carefull, it will delete the account without confirmation, and it
cannot be undone.Twitter ApplicationsIn order to allow external access to a twitter account, you need to register
an “Application” inhttps://dev.twitter.com/There’s already a “PloneTweet”
application registered that can be used, but if you want to use your own, just
regiter it there.Actually posting or getting to/from TwitterThis product just saves the needed data in order to post tweets or read them.
You’ll need additional products in order to do so, for examplecollective.twitter.actionorcollective.twitter.portlets.InstallationTo enable this product in a buildout-based installation:Edit your buildout.cfg and addcollective.twitter.accountsto the list
of eggs to install[buildout]
...
eggs =
    collective.twitter.accountsAfter updating the configuration you need to run ‘’bin/buildout’’, which will
take care of updating your system.Go to the ‘Site Setup’ page in a Plone site and click on the ‘Add-ons’ link.Check the box next to ‘’collective.twitter.accounts’’ and click the
‘Activate’ button.Note: You may have to empty your browser cache and save your resource
registries in order to see the effects of the product installation.ContributorsFranco Pellegrini (frapell@gmail.com)Héctor Velarde (hector.velarde@gmail.com)Development sponsored by Menttes.Changelog1.0.3 (2012-04-10)Fixed distribution. [hvelarde]1.0.2 (2012-04-10)Updated tests. [hvelarde]PEP8/Pyflakes. [hvelarde]Updated documentation. [hvelarde]Updated package classifiers. [hvelarde]Moved to GitHub. [frapell]Refactored the package to give its own dev/test buildout. [frapell]Separated profiles for initial and default. [frapell]Added an uninstall profile. [frapell]Added some tests. [frapell]Improved usability with a pop-up to authorize app. [frapell]1.0.1 (2011-07-26)Added Spanish internationalization. [frapell]1.0.0 (2011-07-25)Created a configlet to add and remove twitter accounts. [frapell]Initial release.
Package: collective.twitter.action
IntroductionThis product provides a content rule action that will tweet an object’s title and a short URL for it.UsageSimply add this product to your buildout and the new action should be available.
You need to have at least one twitter account authorized for the current site, to do so, read the documentation for a dependency of this packagehttp://pypi.python.org/pypi/collective.twitter.accountsChangelog1.0.1Added spanish internationalization [frapell]1.0.0Added a content rule action that will use an account created using collective.twitter.accounts [frapell]Initial release
Package: collective.twittercards
IntegrateTwitter Cardsto Plone.PrerequiresitesPlone 4 (tested with Plone >= 4.3.x)Supported card typesSummary CardSummary Large Image CardPhoto CardRoadmapSome of the upcoming/in-development features/improvements are:All card types (Summary Card with Large Image, Photo Card,
Gallery Card, App Card, Player Card, Product Card).Per content item configurable twitter cards.InstallationBuildout>>> [instance]
>>> eggs +=
>>>     collective.twittercardsZMIZMI -> portal_quickinstallerFirst make sure you have thecollective.z3cform.datagridfieldinstalled.Then choose “collective.twittercards” and install it.Configuration optionsApp control panel can be accessed athttp://your-plone-site.com/@@twittercards-settingsContributorsNote:  place names and roles of the people who contribute to this packagein this file, one to a line, like so:Kenneth Veldman, Original AuthorPeter Uittenbroek, valuables improvements/fixes.Artur Barseghyan, documentation and packaging improvements.Changelog0.1.3 (2015-03-03)Added support for Summary Large Image and Photo Cards.0.1.2 (2015-02-03)Documentation added.0.1.1 (2015-02-02)Added twitter viewlet and various settings to be able to select what type of
card should be used for a certain content type.0.1 (2015-01-30)Initial release.
Package: collective.twitterportlet
IntroductionA Twitter portlet for Plone. This portlet allows you to track the ‘tweets’ of a
particular user. You can add as many portlets as you like. The tweets are cached
for one minute.Add to your buildout:eggs =
    collective.twitterportlet
....
zcml =
    collective.twitterportletInstall this portlet into your Plone site using the Add products in Site Setup.
Add Twitter portlets wherever you need, using the ‘Manage portlets’ interface.The above ‘zcml’ step is not required in Plone 3.3+Changelog0.10 - 2011-03-19When having a tweet with an link containing a mixture of “&?=” the regular
expression in expand_tweet creates invalid html. A failing test for that is
added.
(Pelle Krøgholt - @pellekrogholt - irc:pelle_)Generate proper links for URLs that contain the symbols “&?=#!”. This fixes
the failing test mentioned above.
(Emanuel Sartor - @esartor)Added ability to include native retweets in addition to the standard stream
of tweets.
(Emanuel Sartor - @esartor)0.9 - 2010-05-26Added simple RAM caching of the feed results for at most 100 seconds or the
cache timeout of the ram cache.
(Hanno Schlichting - @hannosch)Added logging on the info level to all exception cases.
(Hanno Schlichting - @hannosch)Handle the unresponsive twitter better by using a timeout on connections,
as advised inhttp://code.google.com/p/python-twitter/issues/detail?id=92.
(Hanno Schlichting - @hannosch)Remove memoize overhead for methods that are only called once.
(Hanno Schlichting - @hannosch)Catch and ignoreTwitterError.
(Hanno Schlichting - @hannosch)Adding ability to link to the user’s Twitter page as the portlet header.
(David Breitkreutz - @rockdj)0.8 - 2010-02-10Ignore all URLErrors instead of the more specific HTTPErrors. This catches
problems like ‘Connection refused’.
(Hanno Schlichting - @hannosch)0.7 - 2010-02-10Fixed reStructuredText markup of the readme file.
(Hanno Schlichting - @hannosch)0.6 - 2010-02-10The Twitter service is surprisingly often unreachable. Protect against common
HTTPErrors and show an unavailable message instead of relying on the common
portlet on-error handling.
(Hanno Schlichting - @hannosch)Removed the empty initialize method.
(Hanno Schlichting - @hannosch)0.5 - 2009-10-29Changed the limit option to push it through to the API rather than
retrieving all and then slicing
(Ben Mason - @sparcd)Added z3c.autoinclude.plugin entry point, so in Plone 3.3+ you can avoid
loading the ZCML file.
(Hanno Schlichting - @hannosch)Portlet displays the error message if there is a problem accessing the API.
(Ben Mason - @sparcd)Links are now hyperlinked using regex.
(Ben Glynn - @Open_Comms)0.4General bug fixes
(Ben Mason - @sparcd)0.3General bug fixes
(Ben Mason - @sparcd)0.2Problems with the egg, so repackaged and re-released
(Ben Mason - @sparcd)0.1Initial Release
(Ben Mason - @sparcd)
Package: collective.twitter.tweet
========================collective.twitter.tweet========================.. contents:: Table of ContentsOverview--------This product provides a twitter action to be used with content rules.Prerequisites-------------This product depends on `collective.twitter.accounts`_.Usage-----Just add this product to your buildout, and you should get the action to be used in the content rules.Optionaly, you can specify a separate URL to be used as the beginning of the link.Example-------- Go to the content rules, and add the "Tweet new content's title and url".- Select the account you want to use, or just choose "First valid account"- If you have a separate site for your public site, you can specify it in the "separate host" field.example: your public site is http://my-site.com/ and your editing one ishttp://another-host:8080/Plone and you want tweets to use the public host, specify it here... _`collective.twitter.accounts`: http://pypi.python.org/pypi/collective.twitter.accountsInstallation------------To enable this product in a buildout-based installation:1. Edit your buildout.cfg and add ``collective.twitter.tweet`` to the listof eggs to install ::[buildout]...eggs =collective.twitter.tweetAfter updating the configuration you need to run ''bin/buildout'', which willtake care of updating your system.Go to the 'Site Setup' page in a Plone site and click on the 'Add-ons' link.Check the box next to ''collective.twitter.tweet'' and click the'Activate' button.Note: You may have to empty your browser cache and save your resourceregistries in order to see the effects of the product installation.Contributors------------* Franco Pellegrini (frapell@ravvit.net)Development sponsored by Open Multimedia.Changelog---------1.0 (unreleased)^^^^^^^^^^^^^^^^- Initial release.
Package: collective.typecriterion
IntroductionThis product will add to your Plone control panel a new entry: “Type criterion settings”.From this panel you can add a set of definition about general content types, which are defined using
a group of existing Plone native types.For example: you can define a new general type called “Textual contents” that is defined by grouping
Pages, News and Events.All those definitions can be used in Plone collections by using the new “General type” criteria.In brief: searching for new general types defined means take a search onto all grouped native types.MotivationI found a lot of Plone users that hardly learn the difference between content types.
For example: the difference between a Page and a File is often too tiny in the mind of the site contributor.
In other situations a grouping feature (like: “look for all multimedia type”) can be useful.With this approach users can only care about some general family on types that a power user defined.Finally 3rd party products could extend an existing list on types, and when a content type change (because it
has been replaced by another, better product) you only care about reconfiguring the general type, not all
the collections in the site.CompatibilityThis product has been tested on Plone 4.3.2, but requiredplone.app.querystring 1.2or better.If you have problems installing this add-on, try to pin plone.app.querystring to version 1.2:[buildout]
...
versions=versions
...
[versions]
plone.app.querystring = 1.2.0
...TODOA Generic Setup import step for configuring types.Changelog0.1.0 (2014-04-11)Initial release
Package: collective.types.citation
collective.types.citationOverviewThe collective.types.citation packageThis type is for citations.  Put in the applicable information and change the display depending on what type of citation it is.  Works with or without Collage.StatusThis release is currently in Beta.
Changelog for collective.types.citationcollective.types.citation - 9.01 BetaInitial package structure. (Liz Dahlstrom)collective.types.citation InstallationTo install collective.types.citation into the global Python environment (or a workingenv), using a traditional Zope 2 instance, you can do this:When you’re reading this you have probably already runeasy_install collective.types.citation. Find out how to install setuptools
(and EasyInstall) here:http://peak.telecommunity.com/DevCenter/EasyInstallIf you are using Zope 2.9 (not 2.10), getpythonproductsand install it
via:python setup.py install --home /path/to/instanceinto your Zope instance.Create a file calledcollective.types.citation-configure.zcmlin the/path/to/instance/etc/package-includesdirectory.  The file
should only contain this:<include package="collective.types.citation" />Alternatively, if you are using zc.buildout and the plone.recipe.zope2instance
recipe to manage your project, you can do this:Addcollective.types.citationto the list of eggs to install, e.g.:[buildout]
...
eggs =
    ...
    collective.types.citationTell the plone.recipe.zope2instance recipe to install a ZCML slug:[instance]
recipe = plone.recipe.zope2instance
...
zcml =
    collective.types.citationRe-run buildout, e.g. with:$ ./bin/buildoutYou can skip the ZCML slug if you are going to explicitly include the package
from another package’s configure.zcml file.
Package: collective.types.topicgroup
collective.types.topicgroupOverviewThe collective.types.topicgroup packageThis type is for topicgroups.  A topicgroup is a special type of folder that only allows certain types to be added to it.  It was originally created to cut down on new user confusion with Collage.StatusThis release is currently in Beta.
Changelog for collective.types.citationcollective.types.citation - 9.02 BetaInitial package structure. (Liz Dahlstrom)collective.types.topicgroup InstallationTo install collective.types.topicgroup into the global Python environment (or a workingenv), using a traditional Zope 2 instance, you can do this:When you’re reading this you have probably already runeasy_install collective.types.topicgroup. Find out how to install setuptools
(and EasyInstall) here:http://peak.telecommunity.com/DevCenter/EasyInstallIf you are using Zope 2.9 (not 2.10), getpythonproductsand install it
via:python setup.py install --home /path/to/instanceinto your Zope instance.Create a file calledcollective.types.topicgroup-configure.zcmlin the/path/to/instance/etc/package-includesdirectory.  The file
should only contain this:<include package="collective.types.topicgroup" />Alternatively, if you are using zc.buildout and the plone.recipe.zope2instance
recipe to manage your project, you can do this:Addcollective.types.citationto the list of eggs to install, e.g.:[buildout]
...
eggs =
    ...
    collective.types.topicgroupTell the plone.recipe.zope2instance recipe to install a ZCML slug:[instance]
recipe = plone.recipe.zope2instance
...
zcml =
    collective.types.topicgroupRe-run buildout, e.g. with:$ ./bin/buildoutYou can skip the ZCML slug if you are going to explicitly include the package
from another package’s configure.zcml file.
Package: collective.ui.ie6nomore
collective.ui.ie6nomoreOverviewEnough is enough. Microsoft Internet Explorer 6 was released in late 2001.
For its time, it was a decent browser, but in 2009, it is still in use by a
significant portion of the web population, and its time is now up.This is a Plone 3 implementation of the code available athttp://www.ie6nomore.com/.Embrace this campaign, support this noble cause.RequirementsPlone 3.3.x (http://plone.org/products/plone)Plone 3.2.x (http://plone.org/products/plone)Plone 3.1.x (http://plone.org/products/plone)Plone 3.0.x (http://plone.org/products/plone)InstallationTo use this package, on a buildout based installation:1. Unpack collective.ui.ie6nomore package to src/ folder of your
buildout
2. Edit your buildout.cfg and add the following information:[buildout]
...
eggs =
    collective.ui.ie6nomore

[instance]
zcml =
    ...
    collective.ui.ie6nomoreThe last line tells buildout to generate a zcml snippet that tells
Zope to configure collective.ui.ie6nomore.If another package depends on the collective.ui.ie6nomore 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.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 to see the effects of the
product installation.Browsers and OS’sInternet Explorer 6.0 (WinXP/Vista) ()Internet Explorer 8.0 (WinXP/Vista)Internet Explorer 7.0 (WinXP/Vista)Firefox 3 (WinXP/Vista/MacOSX)Safari 3 (WinXP/Vista/MacOSX)CreditsErico Andrei (products at simplesconsultoria dot com dot br) - PackagingChangelog1.0 - (2009-08-04)Localization support
[erico_andrei]Based on sniplet available athttp://www.ie6nomore.com/[erico_andrei]Initial release of collective.ui.ie6nomore
[erico_andrei]
Package: collective.unresettableuser
IntroductionThis product add to the Plone administrator a new flag on the user profile: “Block user password reset”.
This check will mark a specific user as unable to change his own password.The Plone administrator can still reset the user password from the “Users and Groups” control panel.When you can need thisThis can be useful only in some rare situation, when you need to share a single user account to a set of
users (giving them all the same userid and password), and for whatever reason you can’t/don’t want create
multiple users.
Obviously you don’t want that an evil guy inside this set of users can change the password.Plone securityKeep in mind that Plone can handle change password using its own security, playing withSet own passwordpermission.Use this product only if you need to control the change password behavior only for specific(s)
users.CompatibilityThis product has been tested onPlone 3. It will not work on Plone 4, due to deep changes
in the user data infrastructure.AuthorsThis product was developed by RedTurtle Technology team.Changelog0.2.0 (2012-02-03)removed from the user preferences theblock_password_resetfield
(even if readonly, is not useful) [keul]user was able to reset his own password, so technically bypass the scope of this
product. [keul]0.1.0 (2011-06-21)Initial release
Package: collective.unslider
ContentsIntroductionChangelog1.4 (2014-08-27)1.3 (2013-07-15)1.2 (2013-07-15)1.1 (2013-07-03)1.0 (2013-06-25)IntroductionThis addon provides a simple user friendly slider portlet using unslider.js and
collective.sliderfields.Changelog1.4 (2014-08-27)Nothing changed yet.1.3 (2013-07-15)Swap width/height of placeholder image [izhar]added wrapper div around unslider content [izhar]1.2 (2013-07-15)Missing definition of height/width variable when image is not set [izhar]1.1 (2013-07-03)Fixed a very silly bug, forgot to link slide to its content [izhar]1.0 (2013-06-25)Initial package generated using inigo.templer
Package: collective.updatelinksoncopy
IntroductionA drop in package for Plone that improves the copy and paste operation
of folder structures. Reference fields (e.g. relatedItems) and UID
inline links in text fields are rewritten if they reference any of the
content within the folder structure being copied so that they now link
to the copied content.Developmentthe buildout in this package will create a test stub which can be run
with:./bin/test -s collective.updatelinksoncopySee the doctests for more information of what this package does.Edit buildout.cfg to point to eitherbuildouts/buildout-plone3.cfgorbuildouts/buildout-plone4.cfg. Don’t forget to rerun
bootstrap.py with python2.4 or python2.6 for plone 3 and plone 4
respectively.CreditsInitial development byMatt Halsteadsponsored byInnovationz.Addition of reference field handling byMatt Halsteadsponsored byInformaat.InstallationThis package requires Plone 3.x or later (tested on 3.3.x).If you are using zc.buildout and the plone.recipe.zope2instance recipe
to manage your project, you can addcollective.updatelinksoncopyto the list of eggs to install, e.g.:[buildout]
...
eggs =
    ...
    collective.updatelinksoncopy(If you are working with a version of Plone < 3.3 then you’ll also
need to install a ZCML slug.)Changelog1.0 (2011-08-10)Gracefully handle unusual reference fields and missing uids.Adjust tests to run with GenericSetup 1.6.3+1.0b5 (2010-04-05)edgecase bugfix1.0b4 (2010-03-16)provide buildout for testing in plone 4 as well as 3clean up use of field accessor/mutator in testsupdate tests to work with plone 41.0b3 (2010-03-16)1.0b2 (2010-03-12)Update reference fields which point to objects within the copy tree.
For example, the default relatedItems field on Archetype Document,
or custom reference fields.1.0b1 (2010-02-05)Initial release [Matt Halstead]
Package: collective.updatemimetype
This Plone add-on can be used to update broken mimetypes of Blob fields.When a file or an image is uploaded to a Blob field, its mimetype is computed
based on information from themimetypes_registry.If that registry misses some information, the computed mimetype can be wrong
or too general.For instance, prior to version 2.0.7 ofProducts.MimetypeRegistry,
the defaultmimetypes_registryof a Plone portal did not
know of OpenXML mimetypes. Those files would getapplication/zipmimetype instead of their proper mimetypes.As computation of mimetype happens only at load time, upgradingProducts.MimetypeRegistryis not enough to fix broken mimetypes.The functioncollective.updatemimetype.migratewalks over content, looks
for blob fields that would get different mimetype if they would be uploaded again,
and updates those field mimetypes.
It can be called from a GenericSetup upgrade step with:from collective.updatemimetype import migrate

migrate(portal)Caution!The update can demand a lot of memory and take a long time if your portal holds
a lot of content.If you want to limit migration to specific content items, you can pass aqueryargument to themigratefunction. For instance, while the code above updates bothFileandImagecontent items of a default Plone site, the code below would
only updateFilecontent items:from collective.updatemimetype import migrate

catalog_query = {'portal_type': 'File'}

migrate(portal, catalog_query)There is also a view registered on the portal. Call it with:http://my_domain/my_portal/updatemimetypeThe view can also be called with aqueryparameter. To limit update toFileitems, call the view with:http://my_domain/my_portal/updatemimetype?query.portal_type:record:string=FileContributorsGodefroid Chapelle,gotcha@bubblenet.be, funded by KULeuvenChangelog0.1.2 (2015-07-06)Fix limiting update to the results of a catalog query.
And document how to do it.
[gotcha]0.1.1 (2015-06-30)Fix classifier
[gotcha]0.1 (2015-06-29)Initial release.
[gotcha]