Modified items

All recently modified items, latest first.

Products.PlacelessTranslationService-2.0.4-1.lbn13.noarch: What is PlacelessTranslationService? ------------------------------------ PTS is a way of internationalizing (i18n'ing) and localizing (l10n'ing) software for Zope 2. It's based on the files supported by the GNU gettext set of utilities. A good source of information and background reading is the gettext documentation: http://www.gnu.org/software/gettext/manual/ Using PlacelessTranslationService --------------------------------- PTS is used in the following steps: 1. i18n your software 2. Prepare a translation template 3. Prepare translations of the template 4. Install translations Each of these is explained below. 1. Internationalizing Your Software A good overview of this can be found at: http://www.upfrontsystems.co.za/Members/jean/mysite-i18n 2. Preparing a Translation Template A translation template is an empty Portable Object file as defined by the gettext standard with a special header block. The PO format is described in detail here: http://www.gnu.org/software/gettext/manual/html_node/gettext_9.html#SEC9 The header block is fairly self explanatory and can be seen in the sample.pot file included in this directory. All phrases in capitals, the language code, language name and (optionally) the content type and preferred encodings should be replaced with their correct values. There are several ways to prepare a PO template: -- By hand: This can be done by copying the blank.pot included in this directory, replacing the sample values as described above and and then manually adding msgid and empty msgstr pairs for each of the msgid's used in your software. -- Using i18ndude: i18ndude is a tool that is useful when all your software is in the form of ZPT's that are stored in files on the filesystem. It can be downloaded from: http://plone.org/products/i18ndude 3. Prepare Translations of the Template Preferably, find a translation company that can handle the gettext standards and send them your .pot file. They should send back .po files for the languages you require. If you're doing it yourself, copy the .pot file to a file on the name of the language you're translating to and with a .po extension. Then go through that file and fill in the msgstr sections. Finally, update all the metadata fields at the top of the file so they are correct for the translation you have just completed. At this point, you should have a .pot file and a collection of .po files. 4. Install Translations PTS will look in folders called 'i18n' for .po files to use as translations. These 'i18n' folders will be searched if they are in the INSTANCE_HOME or in the directories of any of the Products you have installed. Copy your .po files to a 'i18n' folder of your choice in one of these locations. Once that's done, restart Zope.

Products.PasswordResetTool-2.0.16-1.lbn13.noarch: The Password Reset Tool hooks into the standard mechanisms for password mailing provided by the CMF in the Registration Tool and certain skins and replaces this with a facility for resetting passwords with email authentication. This is useful not only to keep passwords out of cleartext email and is absolutely necessary if you choose to encrypt your passwords (and you should.) See the INSTALL.txt file for details on installation, and the LICENSE.txt file for the license this Product is under. Note, of course, that you must have a working MailHost to send email! The Password Reset Sequence from the User's Point of View The user will observe the following steps. * User forgets a password and * clicks "Forgot your password?", which * goes to a form that asks for a username. User fills this in and clicks a button to proceed, which * goes to a form explaining that an email has been sent. * User receives an email with a URL containing a random, unguessable key and opens it in a web browser. * This is a form that asks for username and password, which goes to * a form reporting success (or failure, if expired or illegitimate.)

Products.OrderedFolder-0.4.0-10.lbn13.noarch: Ordered Folders actually patches the ObjectManager to become the OrderedObjectManager and then simply provides a Base Class for the OrderedFolder. Ordered Folders allow your objects inside the Folder to have a specific order. This is especially useful, if you want to display the object in a certain order that is not dependent on any variable. Let's take Martijn Faassen's product Formulator for example, where the single Form Fields need to be in a certain, user-defined order. He could simply use the OrderedFolder as a base class for his form and receives instantanously order support. At iuveno AG we needed this product to implement similar functionality for some new parts of the Kontentor (which will be published soon).

Products.OpenXml-1.1.0-2.lbn13.noarch: OpenXml provides Plone resources for OpenXml documents : * A set of icons for Office 2007 documents * A set of PortalTransforms plugins suitable to OpenXml documents indexing

Products.OFolder-2.0.1-2.lbn13.noarch: Ordered folder for Zope

Products.OFSP-2.13.2-2.lbn13.noarch: General Zope 2 help screens.

Products.NuPlone-1.0b3-2.lbn13.noarch: NuPlone is a new theme for Plone 3.0 made by Cornelis Kolbach Visual design, design studies, initial CSS implementation. Alexander Limi Plone integration, additional CSS work, usability guidance.

Products.MimetypesRegistry-2.0.5-1.lbn13.noarch: * mimetypes_registry (the mimetypes tool) : handle mime types information

Products.MasterSelectWidget-0.4.5-1.lbn13.noarch: Master Select Widget is an Archetypes widget which looks and feels like a normal select dropdown; however, any time an item is selected it triggers javascript events which control the behavior of other fields in the schema. It can hide other fields using CSS, disable other widgets, and alter the vocabulary of other fields using XMLHttpRequest calls to a methods that produce AT DisplayLists (the subordinate fields must use Select, MultiSelect, or MasterSelect widgets). You may have many of these 'master' widgets on a page and each can control multiple 'slave' fields. The 'slave' fields themselves can use 'master' widgets controlling their own 'slaves'. Currently a 'master' can only control one aspect (vocabulary, visibility. etc.) for each of its slaves, but multiple 'masters' can control the same 'slave'.

Products.Marshall-2.1.2-1.lbn13.noarch: Marshall is a framework for pluggable marshalling policies Features ======== - A ControlledMarshaller class that delegates to underlying implementations - A marshall registry tool where you can configure some predicates for choosing marshallers based on several pieces of information available. Copyright ========= - This code is copyrighted by Enfold Systems, LLC. You can find more information at http://www.enfoldsystems.com/ - Portions of this code are copyright ObjectRealms You can find more information at http://www.objectrealms.net

Products.Maps-3.3-1.lbn13.noarch: A Google Maps solution for Plone with the 'GeoLocation' content type. The main purpose of this product is to provide a very simple to use Google Maps integration for Plone. The following goals were set for development: * Ease of use o Add locations to a folder o Set the view of the folder to Map o It figures out how to center and zoom the map automatically * Flexibility for enhancement by using the Zope 3 component architecture * Sane fallbacks when Javascript is not available * Clean separation of javascript, templates and logic * Works on Smart Folders Additionally Maps has the following features: * Support for content which has a location set with the geolocation product

Products.ManagableIndex-2.1.5-4.lbn13.noarch: Products.ManagableIndex is a framework for the easy construction of efficient, flexible, via the ZMI fully customizable indexes for Zope 2.11 (or above). It comes with a set of predefined indexes: Field, Keyword, Path, Range, Word and SimpleText index. Usually, they are more flexible and more efficient than the corresponding indexes from the Zope core. Products.ManagableIndex uses dm.incrementalsearch when it is installed. This can speed up queries by several orders of magnitude when used together with Products.AdvancedQuery

Products.MailHost-2.13.1-2.lbn13.noarch: zope.sendmail integration for Zope 2.

Products.MIMETools-2.13.0-2.lbn13.noarch: MIMETools provides the &lt;!--#mime--&gt; tag for DocumentTemplate.

Products.LDAPUserFolder-2.26-1.lbn13.noarch: This product is a replacement for a Zope user folder. It does not store its own user objects but builds them on the fly after authenticating a user against the LDAP database. Why does the LDAPUserFolder not show all my LDAP groups? According to feedback received from people who use Netscape directory products the way a new group is instantiated allows empty groups to exist in the system. However, according to the canonical definition for group records groups must always have a group member attribute. The LDAPUserFolder looks up group records by looking for group member entries. If a group record has no members then it will be skipped. As said above, this only seems to affect Netscape directory servers. To work around this (Netscape) phenomenon add one or more members to the group in question using the tools that came with the directory server. It should appear in the LDAPUserFolder after that. Why use LDAP to store user records? LDAP as a source of Zope user records is an excellent choice in many cases, like... * You already have an existing LDAP setup that might store company employee data and you do not want to duplicate any data into a Zope user folder * You want to make the same user database available to other applications like mail, address book clients, operating system authenticators (PAM-LDAP) or other network services that allow authentication against LDAP * You have several Zope installations that need to share user records or a ZEO setup * You want to be able to store more than just user name and password in your Zope user folder * You want to manipulate user data outside of Zope ... the list continues. The LDAP Schema Your LDAP server should contain records that can be used as user records. Any object types like person, organizationalPerson, or inetOrgPerson and any derivatives thereof should work. Records of type posixAccount should work correctly as well. The LDAPUserFolder expects your user records to have at least the following attributes, most of which are required for the abovementioned object classes, anyway: * an attribute to hold the user ID (like cn, uid, etc) * userPassword (the password field) * objectClass * whatever attribute you choose as the username attribute * typcial person-related attributes like sn (last name), givenName (first name), uid or mail (email address) will make working with the LDAPUserFolder nicer Zope users have certain roles associated with them, these roles determine what permissions the user have. For the LDAPUserFolder, role information can be expressed through membership in group records in LDAP. Group records can be of any object type that accepts multiple attributes of type "uniqueMember" or "member" and that has a "cn" attribute. One such type is "groupOfUniqueNames". The cn describes the group / role name while the member attributes point back to all those user records that are part of this group. Only those group-style records that use full DNs for its members are supported, which excludes classes like posixGroup. For examples of valid group- and user-records for LDAP please see the file SAMPLE_RECORDS.txt in this distribution. It has samples for a user- and a group record in LDIF format. It is outside of the scope of this documentation to describe the different object classes and attributes in detail, please see LDAP documentation for a better treatment. Things to watch out for Since a user folder is one of these items that can lock users out of your site if they break I suggest testing the settings in some inconspicuous location before replacing a site's main acl_users folder with a LDAPUserFolder. As a last resort you will always be able to log in and make changes as the superuser (or in newer Zope releases called "emergency user") who, as an added bonus, can delete and create user folders. This is a breach of the standard "the superuser cannot create / own anything" policy, but can save your skin in so many ways. LDAP Schema considerations when used with the CMF The CMF (and by extension, Plone) expect that every user has an email address. In order to make everything work correctly your LDAP user records must have a "mail" attribute, and this attribute must be set up in the "LDAP Schema" tab of your LDAPUserFolder. When you add the "mail" schema item make sure you set the "Map to Name" field to "email". The attributes that show up on the join form and the personalize view are governed by the properties you 'register' using the 'Member Properties' tab in the portal_memberdata tool ZMI view, which in turn is sourced from the 'LDAP Schema' tab in the LDAPUserFolder ZMI view. Attributes you would like to enable for portal members must be set up on the LDAPUserFolder 'LDAP Schema' tab first, and then registered using the 'Membeer properties' screen in the Member data tool ZMI view.

Products.LDAPMultiPlugins-1.14-1.lbn13.noarch: The LDAPMultiPlugins provides PluggableAuthService plugins that interoperate with LDAP.

Products.LDAPConnector-1.0-2.lbn13.noarch: Persistent Zope 2 LDAP connection manager

Products.GroupUserFolder-3.55.1-3.lbn13.noarch: GroupUserFolder is a kind of user folder that provides a special kind of user management.

Products.GenericSetup-1.7.4-1.lbn13.noarch: This product provides a mini-framework for expressing the configured state of a Zope Site as a set of filesystem artifacts. These artifacts consist of declarative XML files, which spell out the configuration settings for each "tool" in the site , and supporting scripts / templates, in their "canonical" filesystem representations.

Products.FusionChartsFree-4.0.3-2.lbn13.noarch: FusionCharts Free is a flash charting component that can be used to render data-driven & animated charts for your web applications and presentations. It is a cross-browser and cross-platform solution that can be used with PHP, ASP, JSP, ASP.NET, ColdFusion, Ruby on Rails, simple HTML pages or even PowerPoint Presentations to deliver interactive and powerful flash charts. You do NOT need to know anything about Flash to use FusionCharts. All you need to know is the language you're programming in.

« Previous 20 items Next 20 items » 1 ... 2324 2325 2326 2327 2328 2329 2330 ... 2359


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

Sections

Modified items