Personal tools
Skip to content. | Skip to navigation
plone.multilingualbehavior adds multilingual behavior to content types built with Dexterity. It uses the next generation multilingual engine powered by five/Zope3 technologies, plone.multilingual. The behavior provides the Dexterity-driven content with a marker interface "ITranslatable", and makes available to that translation enabled type all the translation UI components such as menus, views, etc... To make your Dexterity content type translatable, add the following line to the <!-- enabled behaviors --> section in your type's profile: <!-- enabled behaviors --> <property name="behaviors"> <element value="plone.multilingualbehavior.interfaces.IDexterityTranslatable" /> </property> plone.multilingualbehavior implements language independent fields. The content of language independent fields is the same across all language versions. This is convenient, but also a little dangerous, because editing the field on any language version will change the content on all other language versions. For details on how to make fields language independent, see the examples in the test folder. tests/schemata.py shows how to make fields language independent when using the Grok framework; tests/samplecontent_type.xml shows how to achieve the same thing in an xml file. It is also possible to set a field to be language independent through the web, given a sufficiently new version of plone.schemaeditor.
plone.rest allows you to use HTTP verbs such as GET, POST, PUT, DELETE, etc. in Plone. REST stands for Representational State Transfer. It is a software architectural principle to create loosely coupled web APIs. plone.rest provides the basic infrastructure that allows us to build RESTful endpoints in Plone. The reason for separating this infrastructure into a separate package from the ‘main’ full Plone REST API is so you can create alternative endpoints tailored to specific usecases. A number of these specific endpoints are already in active use. Audience plone.rest is for experienced web developers who want to build their own HTTP/REST endpoints on top of Plone. If you want to use a ready-made full RESTful Plone API, you should use plone.restapi. That package uses, and depends upon, this one. Features Registering RESTful service endpoints for the following HTTP verbs: GET POST PUT DELETE PATCH OPTIONS Support for Dexterity and Archetypes-based content objects Content negotiation (‘application/json’ is currently the only format supported). Named services allows to register service endpoints for custom URLs Registering RESTful Service Endpoints plone.rest allows you to register HTTP verbs for Plone content with ZCML.
collective.address This package provides an Dexterity behavior for location addresses to be used in Dexterity based types. How to provide a default value for the country field -If you want to provide a default value for the IAddress' country field, you can provide an ComputedWidgetAttribute adapter like so:: from zope.component import provideAdapter from z3c.form.widget import...
collective.ambidexterity collective.ambidexterity provides through-the-web editing of views, defaults, validators and vocabularies for Dexterity content types.Documentation: of the package The package currently only works in Plone 5.Installation Add collective.ambidexterity to the eggs list in your Plone 5 buildout. Run buildout.Use the add/remove addons option in site setup to activate the...
Introduction This contains two dexterity behaviors, vocabularies and indexers for two 'taxonomy-like' fields:- classifiers_themes (e.g. Air, Air > Quality, Air > Pollution, Water)- classifiers_categories (e.g. Report, Project, Project > Management)You want to show some information on your website and make it easy to find it. You have reports about air or about water. You also have projects...
collective.contact.membrane Integration of dexterity membrane with contacts from collective.contact.core.Contacts are Plone users When you install this package, contacts (Person contents) become Plone users. Once they have a password, they can login, using the contact id or the contact email (set the parameter in the control panel)Contact fields are properties of user. When you change some...