Search results

collective.dancingnotlikely-1.0.2-1.lbn25.noarch

This product patches the elements that shouldn't been show in newsletter with Singing and Dancing. It add content-history id and DocumentByLine class to the list.

collective.datagridcolumns-0.7.0-1.lbn25.noarch

Additional columns for Plone and DataGridField

collective.dexteritytextindexer-2.1.0-1.lbn25.noarch

collective.dexteritytextindexer provides a dynamic SearchableText indexer for dexterity content types. It makes it possible to index fields of multiple behaviors as SearchableText.

collective.diazo.readheaders-0.1-1.lbn25.noarch

This package extends the standard theming middleware of Diazo to add the ability to read the location of a rules XML file from the WSGI environment. This means, amongst being able to read a rules location from the environment for the local user, that an upstream service (such as a web server, reverse proxy, caching proxy, etc) is able to control the theme the middleware is using – and change this for any given request. This contrasts with the configuration-based approach taken by Diazo’s standard middleware, which requires a fixed path to be specified for the middleware. So, this means with the right WSGI configuration, you could conceivably have one Diazo instance serving any number of themes without needing to explicitly configure paths, urlmaps or the like. If you combine this with a suitable front-facing tool (such as a configurable web server like Apache, Nginx, Cherokee, or any other), then you can have this one Diazo instance theming any number of applications, and theming differently based upon any condition your web server supports – such as incoming host name, HTTP vs HTTPS, specific URLs or regex, headers, IP addresses, and more. To achieve this, all you need to do is set the right HTTP header – which is the path to your rules file – and ensure this is sent to your middleware based upon your various conditions.

collective.documentviewer-2.2.1-1.lbn25.noarch

This package integrates documentcloud's viewer and pdf processing into plone. Example viewer: https://www.documentcloud.org/documents/19864-goldman-sachs-internal-emails Features * very nice document viewer * OCR * Searchable on OCR text * works with many different document types * plone.app.async integration with task monitor * lots of configuration options * PDF Album view for display groups of PDFs Works with Besides displaying PDFs, it will also display: * Word * Excel * Powerpoint * HTML * RTF Install requirements * docsplit: http://documentcloud.github.com/docsplit/ * graphicsmagick * ghostscript * poppler * tesseract * pdftk * openoffice(for doc, excel, ppt, etc types) * md5 or md5sum command line tool Async Integration It it highly recommended to install and configure plone.app.async in combination with this package. Doing so will manage all pdf conversions processes asynchronously so the user isn't delayed so much when saving files.

collective.doormat-0.1-2.lbn25.noarch

collective.doormat

collective.dynatree-1.3.4-1.lbn25.noarch

collective.dynatree provides the basic integration of the jQuery plugin jquery.dynatree.js (at google-code). Optional it also provides a full-featured Archetypes Widget with full ATVocabularyManager support, including hierachical VDEX-vocabularies.

collective.easyslider-1.4.1-1.lbn25.noarch

The product will allow you to apply an easyslider to any page with the ability to create each slide using a WYSIWYG editor. It also provides a slider view for Folders and Collections.

collective.easytemplate-0.7.10-2.lbn25.noarch

Easy Template (collective.easytemplate) products brings easy dynamic texts to Plone. You don't need to create full blown product just for few dynamic pages anymore - the most simplest things can be typed straight from the visual editor. Templating is a way to add simple programming logic to text output. This products adds or enhances templating supports on various parts of Plone site.

collective.elasticindex-1.2.5-1.lbn25.noarch

This extension index Plone content into ElasticSearch. This doesn’t replace the Plone catalog with ElasticSearch, nor interact with the Plone catalog at all, it merely index content inside ElasticSearch when it is modified or published. In addition to this, it provides a simple search page called search.html that queries ElasticSearch using Javascript (so Plone is not involved in searching) and propose the same features than the default Plone search page. A search portlet let you redirect people to this new search page as well. This extension have been built for Plone 4, but might work with Plone 3. Usage After adding this extension to your buildout (including the zcml), you can install the extension in Plone. A configuration screen is available inside site setup. It will let you configure the URLs of the ElasticSearch servers to use in order to index, and search. To proceed: Fill in the ElasticSearch settings, Click on Save, Click on Create Index in order to create the ElasticSearch index, Click on Import site content in order to index already existing content in ElasticSearch. You can use the same ElasticSearch server (and probably index) for multiple Plone sites, creating a federated search that way. Security disclaimer By default is no authentication or access validation while searching or indexing content. The original purpose of this search is to be public. If you have private content that you don’t want to be searchable or viewable by unauthorized people, please be sure to check the checkbox index only published content in the configuration screen. In addition to this ElasticSearch is not secured by default, meaning there is no authentication to provide in order to index or look-up content. Be sure to hide it behind a firewall and use a proxy or Apache in order to restrict the requests made to it: you only need to allow access via POST to the sub-URL _search after the index name configured in the configuration screen. For instance, if the index name is plone, you shall allow only requests to http://your-public-es-url/plone/_search. After you configured your proxy, be sure to configure its public URL, like http://your-public-es-url in the configuration screen so the search page knows how to contact it. However if you want to allow users to search though restricted and not yet published content, you can check index security and uncheck index only published content in the configuration screen. After reindexing your content, if you check proxy search requests though Plone and apply security filter, search will work on restricted and not yet published content, but will be slower as the queries will be proxied though Plone.