Search results

collective.transmogrifier-devel-1.5.2-1.lbn25.noarch

collective.transmogrifier development suite (for tests)

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.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.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.upload-9.18.0rc2-1.lbn25.noarch

Support for Archetypes and Dexterity-based content types No browser plugins required: The implementation is based on open standards like HTML5 and JavaScript and requires no additional browser plugins Multiple file upload: Allows to select multiple files at once and upload them simultaneously Drag & Drop support: Allows to upload files by dragging them from your desktop or filemanager and dropping them on your browser window Support for Exif metadata: Uploading images with Exif metadata will pre-populate description and rights Preview for images, audios and videos: A preview of image, video and audio files is displayed before uploading with browsers supporting the required JS APIs Client-side image resizing: Images can be automatically resized on client-side with browsers supporting the required JS APIs Upload progress bar: Shows a progress bar indicating the upload progress for individual files and for all uploads combined Cancelable uploads: Individual file uploads can be canceled to stop the upload progress Graceful fallback for legacy browsers: Uploads files via XMLHttpRequests if supported and uses iframes as fallback for legacy browsers Drag and drop uploads from another web page: Supports uploading files dragged from one page into another (tested with Firefox and Chrome

collective.uploadify-1.2-1.lbn25.noarch

Multifileupload for Plone using uploadify Usage After install, go to http://your-plone-site/@@upload

collective.usernamelogger-1.2-2.lbn25.noarch

Log user names when using cookie authentication in Zope/Plone.

collective.vdexvocabulary-0.1.2-1.lbn25.noarch

What this package do? IMS VDEX is a standard for exchanging vocabularies. collective.vdexvocabulary create bridge between vdex vocabularies and zope vocabularies, so you can easily use it in systems like Plone / Zope. Contents What this package do? Whats so special about it? How do I use it? Example VDEX file How to access relations (from code) Where can I complain / help / send rum? Credit TODO History 0.1.2 (2014-01-07) 0.1.1 (2010-10-11) 0.1 (2010-06-23) 0.1a1 (2010-04-29) Whats so special about it? Imagine you have big vocabularies with a lot of relations. I'm talking +10.000 terms with +30.000 relations. So this would be perfect use case to use collective.vdexvocabulary. Also there are other stuff which I didn't found in other vocabulary packages for Plone/Zope: i18n support (as it is defined in IMS VDEX) proper order also with unicode charecters (if zope.ucol is installed) easy registration using zcml relations as it specified in IMS VDEX standard How do I use it? In your configure.zcml add: <configure ... xmlns:vdex="http://namespaces.zope.org/vdex" ...> <include package="collective.vdexvocabulary" file="meta.zcml" /> <include package="collective.vdexvocabulary" /> And to register a vdex vocabulary simply add line bellow pointing to file containing vdex vocabulary: <configure ... xmlns:vdex="http://namespaces.zope.org/vdex" ...> <vdex:vocabulary file="path-to/very-interesting.xml" /> To make registration of vocabularies even easier you can also register several vocabularies and just point to directory: <configure ... xmlns:vdex="http://namespaces.zope.org/vdex" ...> <vdex:vocabulary directory="path-to/my-vdex-vocabularies" /> vdex files in path-to/my-vdex-vocabularies directory should have ending .vdex to be recognized by vdex:vocabulary ZCML directive. Example VDEX file Example of car manufacturers list (car_manufacturers.vdex).: <?xml version="1.0" encoding="utf-8"?> <vdex xmlns="http://www.imsglobal.org/xsd/imsvdex_v1p0" orderSignificant="false" language="en"> <vocabIdentifier>your.package.car_manufacturers</vocabIdentifier> <term> <termIdentifier>ford</termIdentifier> <caption> <langstring language="en">Ford</langstring> <langstring language="es">Una miedra de coche</langstring> </caption> </term> <term> <termIdentifier>bmw</termIdentifier> <caption> <langstring language="en">BMW</langstring> <langstring language="es">Be-eMe-uWe, mierda</langstring> </caption> </term> <relationship> <sourceTerm>bmw</sourceTerm> <targetTerm vocabIdentifier="your.package.car_models">very-special-bmw-model</targetTerm> <relationshipType source="http://www.imsglobal.org/vocabularies/iso2788_relations.xml">NT</relationshipType> </relationship> ... </vdex> List of car models (car_models.vdex).: <?xml version="1.0" encoding="utf-8"?> <vdex xmlns="http://www.imsglobal.org/xsd/imsvdex_v1p0" orderSignificant="false" language="en"> <vocabIdentifier>your.package.car_models</vocabIdentifier> <term> <termIdentifier>very-special-bmw-model</termIdentifier> <caption> <langstring language="en">Very special BMW model</langstring> <langstring language="es">Un modelo de Be-eMe-uWe</langstring> </caption> </term> <relationship> <sourceTerm>very-special-bmw-model</sourceTerm> <targetTerm vocabIdentifier="your.package.car_manufacturers">bmw</targetTerm> <relationshipType source="http://www.imsglobal.org/vocabularies/iso2788_relations.xml">BT</relationshipType> </relationship> ... </vdex> How to access relations (from code) Relations are defined by ISO2788. To get listing of BMW car models from above VDEX example you have to: from zope.schema.vocabulary import getVocabularyRegistry vr = getVocabularyRegistry() car_manufacturers = vr.get(self.context, 'your.package.car_manufacturers') car_models = vr.get(self.context, 'your.package.car_models') bmw = car_manufacturers.getTerm('bmw') bmw_car_models = bmw.related.get('NT', [])

collective.whoiswho-1.0-1.lbn25.noarch

Plone addon that provides read-only views which display all groups, the members per group and the member's details. The views are made available to the user through a link in the user's menu (iow, a user action).

collective.workspace-1.1-1.lbn25.noarch

collective.workspace package for providing 'membership' in specific areas of a Plone Site. It allows you to grant people access to areas of content using a membership group rather than local roles for each user, and to delegate control over that group to people who don't have access to the site-wide user/group control panel. collective.workspace provides a behavior that can be enabled for any Dexterity content type. When enabled, it adds a "Roster" tab which is where you can manage the team. All the functionality takes place via an IWorkspace adapter, which can be overridden to specify: A list of groups, and the roles that each group should receive. These groups are created automatically via a PAS plugin, and automatically granted local roles using a borg.localrole adapter. The schema for which fields should be stored for each member in the roster. This includes checkboxes for the groups, to determine which groups the member is in. Action links for each row in the roster. The default is an "Edit" link which brings up a popup to edit the fields for that person's roster membership. Action buttons at the bottom of the roster which apply to the rows the user selects. An example of this could be a 'Send email' action, so a roster admin can easily email users in the roster. Unlike similar previous packages (see slc.teamfolder and collective.local.*), collective.workspace supplies its own PAS groups plugin, instead of using standard Plone groups. This means that Workspace-specific groups do not appear in the sitewide group control panel. Some other features are: Membership in a roster is indexed, so you can search the catalog for items of portal_type X that have a particular user in their roster. Events are fired when roster memberships are added/modified/removed.