Modified items

All recently modified items, latest first.

collective.flowplayer_toolbar-1.0.0-1.lbn25.noarch: This product use basic feature given to you from Flowplayer. You must know that installing collective.flowplayer in your Plone site give you all the Flowplayer power. Unluckily the native Flowplayer's controlsbar is not always accessible: recent releases sometimes are quite usable with keyboard, but not on every browser and not all features. There's a Flowplayer plugin gives you the power to create and handle the player with an alternative JavaScript controlsbar. This product does exactly this task. The default Flash controlsbar of the player will be disabled and a new, JavaScript based, ones will be shown providing some WAI ARIA attributes. If needed you can also enable again the native Flash controlsbar (as far as only there you can access feature like the fullscreen view of your videos, due to security reasons). To do this, put to True the toolbar_flash_controlsbar property in the flowplayer_properties property sheet. The controlsbar plugin provided is not the original one you can find on Flowplayer site, but is fixed to be more accessible and fully usable using keyboard. You can move around using the TAB key (and SHIFT+TAB for moving backward) and trigger button with ENTER. When the focus is on the slider that indicate the video progress, you can: move forward/back for 5 seconds with right/left keys move forward/back for 1 minute with PAGE DOWN/PAGE UP keys move at the beginning of the video with HOME key move at the end of the video with END key If you don't care about accessibility of your videos, you don't need this package (but obviously you are a bad guy).

collective.flowplayer-4.2.1-2.lbn25.noarch: collective.flowplayer integrates the GPL version of Flowplayer with Plone 4.x. It can play .flv Flash Video files, mp4 files or links as well as .mp3 files or links.

collective.flexitopic-0.7-1.lbn25.noarch: Flexitopic integrates the easy use of plone collections with a Flexigrid AJAX view. The criteria from the topic are taken to construct a simple query form to narrow down a search inside a collection. Subtopics are displayed inside tabs of the (old style) collection. It works with new (plone.app.collection.Collection) and old (Products.ATContentTypes.ATTopic) style collections Flexitopic does not install a new content type but just adds an additional view to the collection type. it degrades for non javascript browsers to a simple table - (almost) same usability, no information loss. it requires JQuery only (built into plone 4) no JQuery UI lightweight JS Flexigrid: 27 KB packed JSlider: 22 KB packed

collective.fastview-0.2.2-2.lbn25.noarch: View and viewlet helper modules for Plone theme and five.grok developers

collective.fancyzoomview-1.0.1-2.lbn25.noarch: collective.fancyzoomview provides smooth javascript image zooming for Plone folders, topics and news items based on Steve Smith's jQuery version of Fancy Zoom.

collective.facetednavigation-0.7.2-1.lbn25.noarch: What is faceted navigation (the concept) First, what is faceted classification: A faceted classification system allows the assignment of multiple classifications to an object, enabling the classifications to be ordered in multiple ways, rather than in a single, pre-determined, taxonomic order. -- Wikipedia (Faceted classification) Once we know what faceted classification is, we can infer what is a faceted browser: A faceted browser or faceted semantic browser is a user interface which makes use of faceted classification to allow the user to explore by filtering available information. Each facet typically corresponds to the possible values of a property common to a set of digital objects. -- Wikipedia (Faceted browser) An example would help, I guess: A traditional restaurant guide might group restaurants first by location, then by type, price, rating, awards, ambiance, and amenities. In a faceted system, a user might decide first to divide the restaurants by price, and then by location and then by type, while another user could first sort the restaurants by type and then by awards. Thus, faceted navigation, like taxonomic navigation, guides users by showing them available categories (or facets), but does not require them to browse through a hierarchy that may not precisely suit their needs or way of thinking. -- Wikipedia (Faceted classification) Sources: Faceted classification in Wikipedia; Faceted browser in Wikipedia. Various examples of faceted navigation are also available on the home page of the MIT Exhibit project. What is Faceted Navigation (the Plone product) This concept sounds cool, but what does Faceted Navigation (the product) exactly do? Once we have installed the product, we will have to configure facets (i.e. criteria), which are actually linked to default or custom catalog indexes. Then the user will see a new link in the portal actions bar (along "site map" and other links), called "Faceted navigation". This link leads to an user interface that lets the user browse portal items via... a faceted navigation.

collective.externaleditor-1.0.3-1.lbn25.noarch: This package add a Control Panel to enable or disable external editor (ext_editor property in Plone seems to be unused) and to choose on which content types action will be available. Technically this package add a skin layer to override external_edit.py and externalEditorEnabled.py python scripts from Plone to make them call views. These views respect the same behavior as today in Plone but add security checks (now you need "Modify Portal Content" to call external_edit) and add the support for content types you choose in the configlet. Permissions 'WebDAV Unlock items' and 'WebDAV Lock items' are given to the 'Editor' role. IMPORTANT : previous settings for these permissions will be erased.

collective.embedly-2.4-1.lbn25.noarch: This package provides TinyMCE visual editor support for embed.ly service: videos, images and other rich media can be inserted to Plone from different services through one API. The approach here is to use the Transform machinery to replace the URL with embed code by calling the embed.ly API. There are more than 200 services that support embed.ly service. These are such video sharing sites as Youtube, Blip.tv, Vimeo; such audio streaming services as Grooveshark, SoundCloud, last.fm; such image/photo stocks as Flickr, and many other: GoogleMaps, Facebook, Twitter, etc. Usage To embed media from the embedly-supported external resource to Plone: Go to the object’s edit form, select some text and click ‘Insert/Edit Embedly link’ button. In the panel add link and configure extra parameters in ‘Advanced’ tab. Check http://embed.ly/docs/arguments for params description. The text should now look like linked. TinyMCE makes the whole passage linked, so keep in mind that the whole passage will later be substituted with embedded media. Save this page. Now when rendered, there will be “preview” from embed.ly service inserted instead of the linked text. More about usage at http://projects.quintagroup.com/products/wiki/collective.embedly Note collective.embedly does not fix errors in provided URLs you can check if your URL will be transformed calling embed.ly manualy, for example: o video URL http://www.youtube.com/watch?v=L1NPLlhFTVk o you should call http://api.embed.ly/1/oembed setting ‘url’ parameter with your value o http://api.embed.ly/1/oembed?url=http://www.youtube.com/watch?v=L1NPLlhFTVk o http://api.embed.ly/1/oembed?url=http://www.youtube.com/watch?v=L1NPLlhFTVk&fromat=xml format result as xml You can set parameters by going to the Plone control panel / Embedly settings: o cache usage and timeout o service URL verification o API key You can update the regular expression for supported services by calling http://yourhost/plonesite/@@update_embedly_services The default is to not pass along an API key, your requests to embedly will be anonymous and based solely on IP address.

collective.elephantvocabulary-0.2.5-1.lbn25.noarch: Like elephants don't forget anything, so does not collective.elephantvocabulary. It provides a wrapper around for existing zope.schema vocabularies and make them not forget anything. Example usecase would be a vocabulary (source) of users which from certain point in time wants to hide / deactivate some users for form or listing. But at the same time you want keep old references to user term working. This is where collective.elephantvocabulary comes into the picture. With it you wrap existing vocabulary of users and provide set of hidden list of users (term values).

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.

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.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.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.doormat-0.1-2.lbn25.noarch: collective.doormat

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.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.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.datagridcolumns-0.7.0-1.lbn25.noarch: Additional columns for Plone and DataGridField

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.dancing-1.1-1.lbn25.noarch: Singing & Dancing is the next generation newsletter Product for Plone. It's an out of the box solution that works without modification for most of your use cases. And should you find something that Singing & Dancing can't do, it's built to be easily extended via plug-ins using the Zope 3 Component Architecture. Features Modern and extensible Singing & Dancing builds on the latest and greatest efforts in the Zope and Plone world. It makes heavy use of the excellent z3c.form library and the Zope 3 Component Architecture. This allows you to easily plug in and extend Singing & Dancing to fit your needs. Well tested An extensive suite of automated tests make Singing & Dancing exceptionally stable and reliable. We currently have 200+ tests. Singing & Dancing is not gonna leave you in the lurch! Fully managable through the Plone interface Singing & Dancing is fully usable out of the box. An extensive set of forms reachable through the configuration panel let you as the user configure many details of your newsletters, like when they're sent (periodically or manually), what is sent (through the use of the Smart Folder interface, or manually), and to whom. Subscriptions Singing & Dancing uses confirmed subscription, i.e. subscribers receive an e-mail to confirm their subscription. Users can subscribe via a standard subscription form that lists all available newsletters in the site, or through individual subscription forms, e.g. in portlets.

« Previous 20 items Next 20 items » 1 ... 675 676 677 678 679 680 681 ... 2449


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

Sections

Modified items