Search results

collective.themefragments-1.0.0-1.lbn19.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.

collective.tinymceplugins.advfilelinks-1.2.1-1.lbn19.noarch

An advanced Plone TinyMCE plugin for handling links to files

collective.tinymceplugins.codemagic-1.1-1.lbn19.noarch

Integration of the CodeMagic TinyMCE plugin with Plone

collective.tinymceplugins.imagebrowser-1.0b6-1.lbn19.noarch

A TinyMCE plugin to provide thumbnail image browsing and a ressource library

collective.transcode.star-0.21-1.lbn19.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.transmogrifier-1.5.1-2.lbn19.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.transmogrifier-devel-1.5.1-2.lbn19.noarch

collective.transmogrifier development suite (for tests)

collective.twitter.accounts-1.0.3-1.lbn19.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.twitter.action-1.0.1-2.lbn19.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.portlets-1.0b5-1.lbn19.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.