Modified items

All recently modified items, latest first.

collective.twitter.portlets-1.0b5-1.lbn25.noarch: Usage Twitter profile portlet * Add a "Twitter profile Portlet" wherever you want. * Enter a header (if you want one). * Choose the Twitter account to use from the drop-down (see Prerequisites). * Enter the user you want to get the feed from. (username can be with @ or not). * Mark the checkbox for showing the avatars next to the username, or leave it unmarked for not. * Choose the maximum results you want to show each time. Twitter search portlet * Add a "Twitter search Portlet" wherever you want. * Enter a header (if you want one). * Choose the Twitter account to use from the drop-down (see Prerequisites). * Enter the search string you want to use. * Mark the checkbox for showing the avatars next to the username, or leave it unmarked for not. * Choose the maximum results you want to show each time. Extras From any portlet, you can: * Click on a "#" starting word (hashtag) to go to Twitter and get further results * Click on an "@" starting word (usernames) to go to the user profile in Twitter.

collective.twitter.action-1.0.1-2.lbn25.noarch: Introduction This product provides a content rule action that will tweet an object's title and a short URL for it. Usage Simply 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 package http://pypi.python.org/pypi/collective.twitter.accounts

collective.twitter.accounts-1.0.3-1.lbn25.noarch: Introduction This product allows you to add twitter accounts to a Plone site. It uses oAuth authentication. Usage * Go 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 Applications In order to allow external access to a twitter account, you need to register an "Application" in https://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 Twitter This 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 example http://pypi.python.org/pypi/collective.twitter.action

collective.transmogrifier-devel-1.5.2-1.lbn25.noarch: collective.transmogrifier development suite (for tests)

collective.transmogrifier-1.5.2-1.lbn25.noarch: A "transmogrifier pipeline" refers to a description of a set of pipe sections, slotted together in a set order. The stated goal is for these sections to transform data and ultimately add content to a Plone site based on this data. Sections deal with tasks such as sourcing the data (from textfiles, databases, etc.) and characterset conversion, through to determining portal type, location and workflow state. Note that a transmogrifier pipeline can be used to process any number of things, and is not specific to Plone content import. However, it's original intent is to provide a pluggable way to import legacy content.

collective.transcode.star-0.21-1.lbn25.noarch: collective.transcode.* or transcode.star for short, is a suite of modules that provide transcoding services to Plone sites. Both the naming scheme and the basic design priciples were inspired by collective.blog.star. Namely: Be modular. Not everyone wants everything your software has to offer. Be flexible. Don't assume that people want to use your software in one way. Be simplistic. If there is a simple way of doing it, do it that way. Be Ploneish. Plone already has 90% of what we need built in. Use it. It works out of the box with standard Plone Files, providing transcoding services to web friendly formats (mp4, ogv) when uploading video content. Additionally, a jpeg thumbnail is being extracted from the 5th second of the videos and a flowplayer viewlet pointing to the produced mp4 file will be displayed inside the IAboveContentBody viewlet manager when transcoding is complete. Transcode.star can be easily configured through the Plone Control Panel to work with any custom AT content type, as long as there is a File field in the schema. In the Transcode Settings panel you can enter a new line in the supported portal types, following the format customPortalType:fileFieldName where customPortalType the name of your portal_type and fileFieldName the name of the file field that you need transcoding for. Support for Dexterity content types is planned for the coming versions. For the transcoding to work you need to start the transcodedaemon instance provided in the buildout. If your transcoding needs are high, you can configure several transcode daemons in a load balanced setup. Transcode.star will select the daemon with the minimum transcoding queue length. All communication between transcode.star and transcode.daemon is encrypted using symmetric encryption by the pycrypto module so that the transcode server(s) transcode videos sent by the Plone site only, preventing abuse by third parties. Also extra care has been taken to transcode videos in private state (typical senario for a Plone site, when users upload a file) by using the same secure channel.

collective.tinymceplugins.imagebrowser-1.0b6-1.lbn25.noarch: A TinyMCE plugin to provide thumbnail image browsing and a ressource library

collective.tinymceplugins.codemagic-1.1-1.lbn25.noarch: Integration of the CodeMagic TinyMCE plugin with Plone

collective.tinymceplugins.advfilelinks-1.2.1-1.lbn25.noarch: An advanced Plone TinyMCE plugin for handling links to files

collective.themefragments-1.0.0-1.lbn25.noarch: Diazo Rules may operate on content that is fetched from somewhere other than the current page being rendered by Plone, by using the href attribute to specify a path of a resource relative to the root of the Plone site:  <after css:theme-children="#leftnav" css:content=".navitem" href="/@@extra-nav" /> The href attribute can be used with any rule apart from <drop /> and <strip />, and can reference any URL, for example to an existing browser view configured for your site. However, it is often desirable to generate some dynamic content specifically for the purpose of constructing a particular theme. In this scenario, you can use fragments.

collective.testcaselayer-1.6.1-1.lbn25.noarch: The support for layers provided by zope.testing helps to lessen the amount of time consumed during test driven development by sharing expensive test fixtures, such as is often requires for functional test. This package provides several well tested facilities to make writing and using layers faster and easier. The collective.testcaselayer.common.common_layer, used in the Quick Start, also includes some commonly useful test fixtures: a mock mail host remove ‘Unauthorized’ and ‘NotFound’ from error_log ignored exceptions puts the resources registries in debug mode (portal_css, portal_javascripts, portal_kss)

collective.templateengines-0.3.4-2.lbn25.noarch: collective.templateengines is an template engine abstraction layer for Python. It defines generic Zope interfaces for communicating with various Python template engines to achieve higher code reuse value. This package is still much in development. All contributions and comments are welcome. Features collective.templateengines helps you to achieve * Easy, pluggable, template language switching. Write template tag code only once and use it across all template engines using abstracted tag plug-ings * Clean your codebase from template engine dependencies * Generic error and warning reporting mechanism across template engines * EGG deployment and easy_install support from PyPi repository * Interfaces defined using standard Zope interfaces package * Backends for Django template Language, Cheetah and Jinja2 * Unit tests

collective.tabr-1.2-1.lbn25.noarch: A simple package to add jQuery Tools Tabs UI support to Plone

collective.sylvester-0.2-2.lbn25.noarch: collective.sylvester (Sylvester for short) is a twitter client for Plone. It aims to make tweeting and twitter account management available from within a Plone site. Overview ======== Sylvester has a pluggable dashboard. All other views are loaded via ajax into the dashboard. These pages are currently available: - The main feed. Eerily similar to the homepage on twitter.com. - Friends page. Shows people your are following as tiled portlets. - Replies. Shows messages where you are mentioned. These actions are currently available: - Publish to twitter. Tweet about Plone content on twitter. The URL is shortened by tinyurl.com. - A "Twitter Dashboard" link appears in your personal bar.

collective.sugarcrm-1.2-1.lbn25.noarch: Introduction SugarCRM is an open-source software-solution vendor which produces the Sugar Customer Relationship Management (CRM) system. This add-on provide components to use SugarCRM in Plone. Status Useable in production tests Integration tests are run with a trial URL If it is not available, please fill the demand for a new demo at http://www.sugarcrm.com/crm/ondemand_eval.html and export the URL into environnement: export SUGARCRM_SOAP_URL="NEW TRIAL URL" you can exclude integration tests with sugarcrm by using use ./bin/test -t UnitTest Components pasplugin A PAS plugin has been implemented. You can logged into Plone with sugarcrm credentials. webservice suds has been used to provide a simple api over soap's sugarcrm. >>> webservice = ISugarCRM(context) >>> results = webservice.search(query_string='JeanMichel') source z3c.formwidget.query.interfaces.IQuerySource for contacts and accounts are provided. password A utility is available to crypt password for using with webservice (sic) portlet contact With a condition on collective.portlet.contact installed, it provides a backend from your sugarCRM contact address book to the contact portlet

collective.splashdancing-1.1a-3.lbn25.noarch: SplashDancing aka Sensible Defaults Aims to add some "sensible defaults" to the Singing And Dancing Product The features include: ------------------------ - pictures sent with news items - A control panel for "zapping" HTML ids and classes that should not show up in newsletters More detail ------------------ This product registers an adapter for the Singing and Dancing newsletter product that detects if a news item has a picture and sends the picture along with the news item. It also provides a "through the web" (TTW), control panel where a user can list ids and classes that should not be sent in a newsletter. An Out of the box S&D newsletter does not allow newsitems to "travel" with their pictures and instead has a very basic representation of newsitems.

collective.solr-3.0b5-2.lbn25.noarch: collective.solr integrates the Solr search engine with Plone. Apache Solr is based on Lucene and is the enterprise open source search engine. It powers the search of sites like Twitter, the Apple and iTunes Stores, Wikipedia, Netflix and many more. Solr does not only scale to any level of content, but provides rich search functionality, like facetting, geospatial search, suggestions, spelling corrections, indexing of binary formats and a whole variety of powerful tools to configure custom search solutions. It has integrated clustering and load-balancing to provide a high level of robustness. collective.solr comes with a default configuration and setup of Solr that makes it extremely easy to get started, yet provides a vastly superior search quality compared to Plone's integrated text search based on ZCTextIndex.

collective.singing-0.7.5-1.lbn25.noarch: Singing is a Zope 3 library for sending notifications and newsletters.

collective.responsivetheme-1.2.2-1.lbn25.noarch: This Responsive Theme product will give your Plone a responsive theme on install. But you can also include collective.responsivetheme to the custom theme you are making.

collective.recipe.template-2.0-1.lbn25.noarch: Buildout recipe to generate a text file from a template

« Previous 20 items Next 20 items » 1 ... 668 669 670 671 672 673 674 ... 2449


	Copyright © 2000-2026 Corporation of Balclutha Inc. All rights reserved.

Sections

Modified items