Search results

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.singing-0.7.5-1.lbn25.noarch

Singing is a Zope 3 library for sending notifications and newsletters.

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.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.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.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.tabr-1.2-1.lbn25.noarch

A simple package to add jQuery Tools Tabs UI support to Plone

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.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.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: <!-- Pull in extra navigation from a browser view on the Plone site root --> <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.