You are here: Home

Modified items

All recently modified items, latest first.
RPMPackage plone.app.referenceablebehavior-0.7.7-1.lbn25.noarch
The “IReferenceable” behavior is used for enabling UUID (plone.app.uuid) support for dexterity contents, like in archetypes content types. This allow for example references between archetypes and dexterity content types. Note: It can’t work with Plone==4.0 because it is based on plone.uuid integration in CMF. It is compatible with Plone>=4.1
RPMPackage plone.app.redirector-1.2.2-1.lbn25.noarch
============ Bring dead links back to life! plone.app.redirector knows where your content used to be and can bring you to its new location when content moves. This component expects you to register storage.RedirectionStorage as a local utility providing IRedirectionStorage (CMFPlone does this). Once that's done, the subscribers in subscribers.py will listen for object moved and object deleted events. When an object is moved (renamed or cut/pasted into a different location), the redirection storage will remember the old path. It is smart enough to deal with transitive references and circular references. When an object is deleted, all references to it are deleted as well. The view in browser.py contains methods (used in Plone's default_error_message.pt when it gets a NotFound error) that do the following: - attempt to redirect from the assumed intended path to the new path of an object, if the redirection storage holds a reference from the old path. - if not, look for the first valid parent of the assumed intended path, and present it as an option to the user - further, use the last id of the assumed intended path and attempt to search for objects in the catalog that contain this, presenting the options to the user
RPMPackage plone.app.querystring-1.3.3-1.lbn25.noarch
This package provides an queryparser, querybuilder and extra helper tools, to parse stored queries to actual results, used in new style collections. It includes a registry reader which reads operators, values and criteria from the Plone registry.
RPMPackage plone.app.openid-2.1.0-1.lbn25.noarch
This packages makes Plone a complete OpenID consumer, allowing people to authenticate in a site using their OpenID identity. It relies on the plone.openid_ package to implement authentication of identities and needs an external session management plugin such as plone.session_ to add session management.
RPMPackage plone.app.multilingual-3.0.2-1.lbn25.noarch
Introduction ============ Talking about multi-language support in Plone is talk about Products.LinguaPlone. It has been the *defacto* standard for managing translations of Archetypes-based content types in Plone through the years. Somehow its functionality never made its way into the Plone core and today it is in legacy status. Nowadays, Plone faces the rising of Dexterity content types and its incoming adoption into the Plone core in the near future (4.3) and complete the transition to Plone as default content types in Plone 5. plone.app.multilingual was designed originally to provide Plone a whole multilingual story. Using ZCA technologies, enables translations to Dexterity and Archetypes content types as well managed via an unified UI. This module provides the user interface for managing content translations. It's the app package of the next generation Plone multilingual engine. It's designed to work with Dexterity content types and the *old fashioned* Archetypes based content types as well. It only works with Plone 4.1 and above due to the use of UUIDs for referencing the translations. After more than 7 years, a GSOC, redesigns, reimplementations due to deprecated libraries, two major Plone versions finally we are able to say that plone.app.multilingual is finally here. Components ========== PAM is composed of four packages, two are mandatory: * plone.app.multilingual (UI) * plone.multilingual (core) and two optionals (at least one should be installed): * plone.multilingualbehavior (enables Dexterity support via a behavior) * archetypes.multilingual (enables Archetypes support) Usage ===== To use this package with both Dexterity and Archetypes based content types you should add the following line to your *eggs* buildout section:: eggs = plone.app.multilingual[archetypes, dexterity] If you need to use this package only with Archetypes based content types you only need the following line:: eggs = plone.app.multilingual[archetypes] While archetypes is default in Plone for now, you can strip ``[archetypes]``. This may change in future so we recommend adding an appendix as shown above. Setup ===== After re-running your buildout and installing the newly available add-ons, you should go to the *Languages* section of your site's control panel and select at least two or more languages for your site. You will now be able to create translations of Plone's default content types, or to link existing content as translations. Features ======== These are the most important features PAM provides. Root Language folders --------------------- After the setup, PAM will create root folders for each of your site's languages and put translated content into the appropriate folders. A language folder implements INavigationRoot, so from the user's point of view, each language is "jailed" inside its correspondent language folder. There are event subscribers in place to capture user interaction with content and update the language in contents accordingly, for example when user moves or copy content between language folders. Babel view ---------- An evolution of the LP *translate* view, unified for either Archetypes and Dexterity content types. It features an already translated content viewer for the current content being edited via an ajaxified dinamic selector that shows them on the fly on user request. Language independent fields --------------------------- PAM has support for language independent fields, but with a twist respect the LP implementation. As PAM does design does not give more relevance to one translated object above the others siblings (has no canonical object), fields marked as language independent get copied over all the members of the translation group always. The PAM UI will warn you about this behavior by reminding you that the values in the field on the other group participants will be overwritten. Translation locator policy -------------------------- When translating content, this policy decides how it would be placed in the site's structure. There are two policies in place: * LP way, the translation gets placed in the nearest translated folder in parent's hierarchy * Ask user where to place the translated element in the destination language root folder Language selector policy ------------------------ While browsing the site, the language selector viewlet allows users to switch site's content language and ease access between translations of the current content. There are two policies in place in case the translation of a specific language does not exist (yet): * LP way, the selector shows the nearest translated container. * Shows the user an informative view that shows the current available translations for the current content. Neutral root folder support --------------------------- The root language folders are used to place the tree of the correspondent language content. However, there are some use cases we need content that does not belongs to any language. For example, for assets or side resources like images, videos and documents. There is need to maintain a language neutral folder for place this kind of objects. After PAM setup, there is a special folder called *Language shared*. All items placed in this folder will have neutral as its default language and will be visible from the other root language folders as they were placed there. Translation map --------------- In order to ease the translation tasks, we devised a tool that displays in a useful way all the current translated objects and its current translation information. The map also shows a list of missing translations in case you want to build a *mirrored* (completely) translated site. Google Translation Service integration -------------------------------------- If you are subscriber of the Google Translation service (a paid service), you can setup your API key on *Languages* site setup. Then, you will notice a new icon in the babel view that takes the original field on the left side and using Google Translations service, translates its contents and fill the right side field. LinguaPlone migration --------------------- You can migrate your existing LP powered sites to PAM using the *Migration* tab in the *Languages* control panel. The migration has been divided into 4 steps for separation of concerns and for improving the success of each of the required procedures. Step 0 (optional) - Reindex the language index ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The migration of LinguaPlone content depends on an up-to-date Language index. Use this step to refresh this index. **Warning:** Depending on the number of items in your site, this can take a considerable amount of time. This step is not destructive and can be executed as many times as needed. Step 1 - Relocate content to the proper root language folder ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This step will move the site's content to its correspondent root language folder and previously will make a search for misplaced content through the site's content tree and will move them to its nearest translated parent. **Warning:** This step is destructive as it will alter your content tree structure. Make sure you have previously configured your site's languages properly in the 'Site Languages' tab of the 'Languages' control panel. It's advisable that you do not perform this step on production servers having not tried it in development/preproduction servers previously. Depending on the distribution of your site's content and the accuracy of the language information on each content object you may need to relocate manually some misplaced content after this step. Despite the fact that this step is 'destructive' it can be executed as times as needed if some problem is detected and afterwards you fix the problem. Please, refer to the procedure log when it finishes. Step 2 - Transfer multilingual catalog information ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This step will transfer the relations between translations stored by LinguaPlone to the PAM catalog. This step is not destructive and can be executed as many times as needed. Step 3 - Cleanup after migration ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This step will search and fix some lost dependencies to the ITranslatable interface hidden in the relation catalog and it gets rid of them. It must be run only when LinguaPlone is already uninstalled, so this step is hidden until then. Marking objects as translatables ================================ Archetypes ---------- By default, if PAM is installed, Archetypes-based content types are marked as translatables Dexterity --------- Users should mark a dexterity content type as translatable by assigning a the multilingual behavior to the definition of the content type either via file system, supermodel or through the web. Marking fields as language independant ====================================== Archetypes ---------- The language independent fields on Archetype-based content are marked the same way as in LinguaPlone:: atapi.StringField( 'myField', widget=atapi.StringWidget( .... ), languageIndependent=True ), .. note:: If you want to completely remove LinguaPlone of your installation, you should make sure that your code are dependant in any way of LP. Dexterity --------- There are four ways of achieve it. Grok directive ~~~~~~~~~~~~~~ In your content type class declaration:: from plone.multilingualbehavior import directives directives.languageindependent('field') Supermodel ~~~~~~~~~~ In your content type XML file declaration:: <field name="myField" type="zope.schema.TextLine" lingua:independent="true"> <description /> <title>myField</title> </field> Native ~~~~~~ In your code:: from plone.multilingualbehavior.interfaces import ILanguageIndependentField alsoProvides(ISchema['myField'], ILanguageIndependentField) Through the web ~~~~~~~~~~~~~~~ Via the content type definition in the *Dexterity Content Types* control panel. Internal design of plone.multilingual ====================================== All the internal features are implemented on the package plone.multilingual. The key points are: 1. Each translation is a content object 2. There is no canonical object 3. The translation reference storage is external to the content object 4. Adapt all the steps on translation 5. Language get/set via an unified adapter 6. Translatable marker interface(s) There is no canonical content object ------------------------------------ Having a canonical object on the content space produces a dependency which is not orthogonal with the normal behavior of Plone. Content objects should be autonomous and you should be able to remove it. This is the reason because we removed the canonical content object. There is a canonical object on the translation infrastructure but is not on the content space. Translation reference storage ----------------------------- In order to maintain the relations between the different language objects we designed a common object called a *translation group*. This translation group has an UUID on its own and each object member of the group stores it in the object catalog register. You can use the ITranslationManager utility to access and manipulate the members of a translation group given one object of the group. Adapt all the steps on translation ---------------------------------- The different aspects involved on a translation are adapted, so it's possible to create different policies for different types, sites, etc. * ITranslationFactory - General factory used to create a new content * ITranslationLocator - Where we are going to locate the new translated content Default : If the parent folder is translated create the content on the translated parent folder, otherwise create on the parent folder. * ITranslationCloner - Method to clone the original object to the new one Default : Nothing * ITranslationIdChooser - Which id is the translation Default : The original id + lang code-block * ILanguageIndependentFieldsManager - Manager for language independent fields Default: Nothing Language get/set via an unified adapter --------------------------------------- In order to access and modify the language of a content type regardless the type (Archetypes/Dexterity) there is a interface/adapter:: plone.multilingual.interfaces.ILanguage You can use:: from plone.multilingual.interfaces import ILanguage language = ILanguage(context).get_language() or in case you want to set the language of a content:: language = ILanguage(context).set_language('ca') Translatable marker interface ----------------------------- In order to know if a content can be translated there is a marker interface: plone.multilingual.interfaces.ITranslatable
RPMPackage plone.app.lockingbehavior-1.0.4-1.lbn25.noarch
Locking integration for dexterity content objects.
RPMPackage plone.app.locales-4.3.16-1.lbn25.noarch
This package contains the translation files for Plone Core and the LinguaPlone add-on product.
RPMPackage plone.app.ldap-1.3.1-1.lbn25.noarch
plone.app.ldap provides a user interface in a Plone site to manage LDAP and Active Directory servers. This package succeeds the simplon.plone.ldap package. It builds on the functionality provided by LDAPMultiPlugins, LDAPUserFolder and PloneLDAP.
RPMPackage plone.app.kss-1.7.1-3.lbn25.noarch
 
RPMPackage plone.app.jquerytools-1.9.4-1.lbn25.noarch
plone.app.jquerytools adds jquery.tools and some related overlay and form-handling JavaScript libraries to Plone. plone.app.jquerytools was developed for Plone 4. Earlier versions could be used in Plone 3.x by adding a zcml slug and running its GS Setup extension profile. This version requires Plone 4.x. Plone developers will wish to use plone.app.jquerytools to provide DOM popups, particularly if they require AJAX. There is extensive support for AJAX form posting. It's also useful for adding dateinput and forminput widgets that are HTML5 compatible. The AJAX and AJAX-form support is Plone-specific, and is documented in this module. Dateinput, rangeinput, accordions, and tooltips are all unchanged from jquerytools, and the jquerytools docs should be consulted.
RPMPackage plone.app.jquery-1.11.2-1.lbn25.noarch
plone.app.jquery adds jquery library to Plone. Version numbers of the package is the same as the jQuery library + packaging version.
RPMPackage plone.app.iterate-3.3.3-1.lbn25.noarch
iterate is a plone product that allows one to utilize a checkin / checkout procedure for content editing. It integrates in versioning, locking, and utilizes zope3 technology like adapters and events to allow for easy customization. Features -------- - versioning utilizing cmf editions - locking using zope dav locks - pluggable behavior for policies via adapters - observable behavior via events - specialized handling for archetypes references - simple, clean integration with the plone user interface Use Cases --------- iterate was designed to solve/enable the following use cases. Collaborative Document Editing Scenario ======================================= Workgroup or person working on a document, the ability to checkout and lock a document allows for a editing cycle, without concern of overwrites, and with an audit trail of versions. Publish/Modify/Review Cycles on a CMS ===================================== A common theme in content management, is publishing a web document, and then needing to revise it but not to change the published web content, till the modified document has undergone a review cycle. Iterate Lifecycle via the User Interface ---------------------------------------- iterate integrates with the plone user interface mainly through the actions menu. it adds three conditional actions to the menu.. checkout, checkin, and cancel checkout. checkout form ============= on this form a user is asked to which location they wish to checkout the current content, the vocabulary of checkouts is overridable via template customization and is currently the current folder, and the user's home folder. if the content is not yet versioned, versioning is applied and a new version is created before the checkout is performed. an adapter is utilized to perform the checkout mechanics and an object lifecycle event is generated with the baseline ( origin ) and checkout as attributes. the adapter is responsible for effecting a copy of the content to the checkout location and taking a lock on the origin content. whether this form and action are active on a given piece of content depends on the iterate policy adapter found for this content. checkouts have some system additional properties, versioning and workflow. they can be versioned independently of the baseline, with only changes from the latest version being merged into the baseline on checkin. they can undergoe separate workflows different from the baseline content. (this last feature requires some customization see docs/workflow.rst ). checkout status form ==================== visually checkouts are distinguished by an extra document icon (next to sendto, and rss links). clicking on this icon will lead to a checkout status page. which allows for looking at information regarding the checkout itself, such as when the checkout was performed and by whom. checkin form ============ a user is asked for a checkin message. on checkin the working copy is merged into the baseline, and a new version of the baseline is created, and the baseline is unlocked. cancel checkout =============== a confirmation dialog is displayed, if the checkout is canceled the working copy is destroyed, and the baseline is unlocked.
RPMPackage plone.app.intid-1.0.5-1.lbn25.noarch
This package provides a Generic Setup extension profile that will install an IntId utility in a CMF portal. Additionally, it registers intid handlers for the standard object events on CMF content. Finally, it finds existing CMF content in the portal and registers it with the IntId utility.
RPMPackage plone.app.imaging-1.0.13-1.lbn25.noarch
User-configurable, blob-aware image scaling for Plone.
RPMPackage plone.app.i18n-2.0.3-1.lbn25.noarch
Plone specific i18n extensions.
RPMPackage plone.app.form-2.2.7-1.lbn25.noarch
This package enables zope.formlib forms to work in Zope 2 code, styled to look like Plone forms. Note that developers should use zope.formlib directly, not Products.Five.formlib.
RPMPackage plone.app.folder-1.1.2-1.lbn25.noarch
Overview This package provides base classes for folderish Archetypes / ATContentTypes content types based on B-trees, a.k.a. "large folders" in Plone. Storing content in such folders provides significant performance benefits over regular folders. The package only contains the integration layer for the base class provided by plone.folder, however. Please see there for more detailed information. Caveats If you are using plone.app.folder in your product you may notice that PloneTestCase will fail to setup a Plone site for your functional tests. This can be resolved by adding this line to your functional test source: from plone.app.folder.tests import bbb
RPMPackage plone.app.drafts-1.0b3-1.lbn25.noarch
plone.app.drafts implements services for managing auto-saved content drafts in Plone. This addresses two problems: * If the browser is accidentally closed or crashes whilst a page is being edited, all changes are lost. * Some data may need to be managed asynchronously, e.g. via a pop-up dialogue box in the visual editor. This data should not be saved until the form is saved (and in the case of an add form, it is impossible to do so). The former problem pertains to any content add or edit form. The latter applies in particular to the "tiles" model as implemented by plone.app.tiles and its dependencies.
RPMPackage plone.app.discussion-2.3.3-1.lbn25.noarch
plone.app.discussion replaces the old commenting system in Plone 4.1 and is also available as an add-on product for Plone 3 and 4.
RPMPackage plone.app.dexterity-2.3.6-3.lbn25.noarch
Dexterity is a content type framework for CMF applications, with particular emphasis on Plone. It can be viewed as an alternative to Archetypes that is more light-weight and modular.
 
Distributions
To see exactly what is included in BastionLinux™, visit our online RPMDistro Builder.
Buy Now
Bastion CD
Subscribe Now
and get BastionLinux™ ...
Sponsored Links