Modified items

All recently modified items, latest first.

Products.ContentTypeValidator-2.0b4-1.lbn13.noarch: Provides a archetypes field validator for content types of files

Products.ClockServer-0.2_Zope2.9dev-2.lbn13.noarch: The Zope ClockServer product provides a mechanism for users to call Zope object methods without the use of an external clock source (e.g. cron/wget). It operates by acting as a medusa "server", essentially coopting Zope's asyncore mainloop and injecting "fake" requests into Zope's ZPublisher. Despite the complicated description, it's rather easy to use.

Products.CacheSetup-1.2.1-2.lbn13.noarch: CacheFu is a collection of products which aggregate and simplify various caching settings, speeding up Plone sites using a combination of memory, proxy, and browser caching. CacheFu can be used by itself or with Squid, Varnish, and/or Apache. Configuration files can be generated for Squid, Varnish, Squid-behind-Apache, Varnish-behind-Apache, and Apache cache proxy (if you are using a non-caching Apache by itself or just Zope-only, no extra configuration files are needed).

Products.CMFUid-2.2.1-3.lbn13.noarch: CMFUid introduces a simple unique id implementation. Implementation ============== The supplied tools attach the unique ids to the objects. The objects do not have to be aware of unique ids. The current implementation depends on the portal catalog to find an object of a given unique id. The interfaces do not imply the use of the catalog (except the IUniqueIdBrainQuery). Which Tool does What? ===================== The 'portal_uidgenerator' tools responsibility is to generate unique ids. The 'portal_uidannotation' tool is responsible to attach unique ids to a content object, and enforce rules about what happens on object move/create/delete. The 'portal_uidhandler' manages registering and accessing unique ids. This design was chosen to allow users replacing only parts of the functionality without having to understand the whole thing. Unique Id API ============= 'portal_uidhandler' implementing 'IUniqueIdHandler' is the main API for playing with unique ids. Usage ===== 'portal_uidhandler' fully implements IUniqueIdHandler (IUniqueIdSet for registering/unregistering unique ids, IUniqueIdQuery for queries and IUniqueIdBrainQuery for more efficient queries by returning catalog brains instead of objects). The current implementation of get/queryBrain and get/queryObject do not return invisible objects (and brains of invisible objects). By invisible objects, we mean objects that would be filtered out by portal_catalog.searchResults due to expiry/effective date and/or user roles. It is often necessary to avoid this filtering in an application. To do this, use the unrestrictedGet/QueryBrain and unrestrictedGet/QueryObject as this will avoid 'None' results. Have a look at the interfaces. CMFUid's functionality is used by CMFDefault's favorite content type to follow linked objects. The favorite content type works as before if CMFUid is not installed.

Products.CMFTopic-2.2.1-3.lbn13.noarch: This product declares a topic content type for the Zope Content Management Framework (CMF).

Products.CMFTestCase-0.9.12-2.lbn13.noarch: Integration testing framework for CMF CMFTestCase is a thin layer on top of the ZopeTestCase package. It has been developed to simplify testing of CMF-based applications and products.

Products.CMFQuickInstallerTool-3.0.6-2.lbn13.noarch: Products.CMFQuickInstallerTool ============================== Features -------- CMFQuickInstallerTool is a facility for comfortable activation/deactivation of CMF compliant products inside a CMF site. Therefore it has to be installed as a tool inside a CMF portal, where it stores the information about the installed products. The requirements for a product to be installable with QuickInstallerTool are quite simple (almost all existing CMF products fulfill them):: External Product: The product has to implement an external method 'install' in a python module 'Install.py' in its Extensions directory. OR The product ships with a GenericSetup extension profile and has no install method. It can still use an uninstall method for custom uninstallation tasks though. Products can be uninstalled and QuickInstellerTool removes the following items a product creates during install: - portal actions, - portal skins, - portal types, - portalobjects (objects created in the root of the portal), - workflows, - left and right slots (also checks them only for the portal), - resource registry entries Attention: QuickInstallerTool just tracks which objects are ADDED, but not what is changed or deleted. Usage ----- In the ZMI click on portal_quickinstaller. The management screen allows you to select products for installation and uninstallation. You can browse into the installed products and see what was created and the logs of the install process. Customized uninstall -------------------- In order to use a customize uninstall, the following requirements must be met:: External Product: The product has to implement an external method 'uninstall in a python module 'Install.py' in its Extensions directory. Please note that the customized uninstall method is invoked before (and in addition to) the standard removal of objects.

Products.CMFQuestions-0.5.2-8.lbn13.noarch: CMFQuestions is a simple product written to collect data from people - feedback on a course, simple data collection etc. Has support for multiple choice and free answer questions.

Products.CMFPlone-4.3.3-1.lbn13.noarch: Plone is a user friendly Content Management System running on top of Python, Zope and the CMF. It benefits from all features of Zope/CMF such as: RDBMS integration, Python extensions, Object Oriented Database, Web configurable workflow, pluggable membership and authentication, Undos, Form validation, amongst many many other features. Available protocols: FTP, XMLRPC, HTTP and WEBDAV Turn it into a distributed application system by installing ZEO. Plone shares some of the qualities of Livelink, Interwoven and Documentum. It aims to be the open source out-of-the-box publishing system. What is Plone? Plone is a ready-to-run content management system that is built on the powerful and free Zope application server. Plone is easy to set up, extremely flexible, and provides you with a system for managing web content that is ideal for project groups, communities, web sites, extranets and intranets. * Plone is easy to install. You can install Plone with a a click and run installer, and have a content management system running on your computer in just a few minutes. * Plone is easy to use. The Plone Team includes usability experts who have made Plone easy and attractive for content managers to add, update, and maintain content. * Plone is international. The Plone interface has more than 35 translations, and tools exist for managing multilingual content. * Plone is standard. Plone carefully follows standards for usability and accessibility. Plone pages are compliant with US Section 508, and the W3C's AAA rating for accessibility. * Plone is Open Source. Plone is licensed under the GNU General Public License, the same license used by Linux. This gives you the right to use Plone without a license fee, and to improve upon the product. * Plone is supported. There are over three hundred developers in the Plone Development Team around the world, and a multitude of companies that specialize in Plone development and support. * Plone is extensible. There is a multitude of add-on products for Plone to add new features and content types. In addition, Plone can be scripted using web standard solutions and Open Source languages. * Plone is technology neutral. Plone can interoperate with most relational database systems, open source and commercial, and runs on a vast array of platforms, including Linux, Windows, Mac OS X, Solaris and BSD. Technical overview Plone is a content management framework that works hand-in-hand and sits on top of Zope, a widely-used Open Source web application server and development system. To use Plone, you don't need to learn anything about Zope; to develop new Plone content types, a small amount of Zope knowledge is helpful, and it is covered in the documentation. Zope itself is written in Python, an easy-to-learn, widely-used and supported Open Source programming language. Python can be used to add new features to Plone, and used to understand or make changes to the way that Zope and Plone work. By default, Plone stores its contents in Zope's built in transactional object database, the ZODB. There are products and techniques, however, to share information with other sources, such as relational databases, LDAP, filesystem files, etc.

Products.CMFPlacefulWorkflow-1.5.10-1.lbn13.noarch: Overview ======== Placeful Workflow is a Plone product that allows you to define workflow policies that define content type to workflow mappings that can be applied in any sub-folder of your Plone site: 1. When you access the root of your site, you will see a new action in the workflow state drop-down menu called "policy". Click on the "policy" link. 2. The next page will let you add a policy to your folder by clicking on the "Add Workflow policy" link. Click on "Add Workflow policy". 3. Now you have a workflow policy in your site, and you can set the workflow policies for this folder and below. We didn't add any workflow policies, so you don't have a choice of different workflow policies yet, so the default workflow policy will be taken both for the folder and below. Usage ===== Now, let's define a new workflow policy: 1. Access "Site Setup" and click on "Placeful Workflow" in the "Add-on Product Configuration" section. 2. Enter the name "my_policy" in the "New policy" field, and click on "add". 3. Now you have a new policy. Enter the title "Example policy" and the description "This is an example policy". 4. Change the workflow for the content type "Folder" from "folder_workflow" to plone_workflow", and click on "Save". Now all your content types should use the "plone_workflow". Let's test the new workflow policy for "Folders" at the root of our site: 1. At the root of the site, select the "Policy" link in the workflow state drop-down menu. 2. Select "Example policy" for "In this Folder" and "Below this Folder" and click "Save". 3. Then, let's add a Folder to see whether the new workflow policy is active. Go to the root of your site and select "Folder" from the "Add new item" drop-down list. Enter the id "myfolder", the title "My folder" and the description "This is my folder", and click on "Save". 4. Now, when you access the "State" drop-down list, you will see that you have the possibility to "submit" the folder. The submit transition only exists in the "plone_workflow", and is absent from the "folder_workflow", which demonstrates that the workflow policy we have chosen is used for the "Folder" content type. Let's go one step further and add a new folder inside of "My folder". After having added the new folder, you should also find the "Submit" transition available. Now it would be interesting to change the workflow policy setting in the Plone site. Let's first change the workflow policy for "Below this Folder" to "Default Policy". You will find that the second folder does not more have the "submit" transition. You can add an additional workflow policy in the first folder, which assigns the "My policy" for "In this Folder", so the second folder will once again have the "submit" transition. Additional tools ================ The Placeful Workflow tool (portal_placeful_workflow) is installed by the installer. It provides a few configuration options so that you use to create you workflow policies through the ZMI.

Products.CMFPhotoAlbum-0.5.0-1.lbn13.noarch: A Plone-based photograph album

Products.CMFFormController-3.0.3-1.lbn13.noarch

Products.CMFEditions-2.2.9-1.lbn13.noarch: CMFEditions provides versioning in Plone. - It works out of the box. - It's higly extensible for specific use cases. Out Of The Box Experience ------------------------- Versionable content items edit views now allows saving a version on save (automatically or manually). The version history may be accessed quickly from the view view. Versionable content types also have an additional tab with version related functionality: - save new version - preview an old version - retrieve an old version (replacing the current state in the tree) - diffing versions A content panel allows configuring the versioning policy by content type: - enable or disable versioning - auto-versioning on save - auto-versioning on retrieve By default the contents of a folder is versioned independently of the folder. This may be changed through the ZMI and for specific cases on python level. Basic support for Archetypes references is built in. The current strategy is to save everything of the content item (incl. security information, workflow state, etc.). On retrieve some of these information are filtered out. This policy may completely be changed depending on specific needs (see modifiers below). Extensibility ------------- CMFEditions was from the beginning developed with extensibility in mind. A handful of tools provide the whole functionality: - repository layer: This is the public main API. The repository layer cares about recursive storing and retrieving of content items from/to Zope 2's Object File System (OFS). - archivist layer: It knows *how to clone* content items. The archivist "is Mr. Pickle". - modifiers: They're invoked by the archivist and know *what to clone*. This the main customization point. A modifier knows about what information on an object is a reference and if the referenced object has to be versioned also. - storage: Is responsible of storing content items versions in a history. The current storage implementation is a ZODB storage (it uses Zope Version Control Product from ZC). Other storages may be written (svn, file based, xml based, etc.). The storage API is quite simple and the storage implementation doesn't have to care about reference stuff as this is already done by the upper layers. - purge policy: The purge policy is called on every save operations and has full control over the version to save and the whole history. The current implementation may be configured to only hold the n current versions by purging the older versions from the repository. This functionality is by default disabled. It may be disabled through the ZMI. You should take care when you're saving objects with a lot of interrelations. Purging functionality is quite new! Additional Documentation ------------------------ A couple of presentations and ReSt documents may be found in documentation package that has to be downloaded separately (or the doc folder of CMFEditions). The CMFEditions team also started adding documentation in the download area <http://plone.org/products/cmfeditions/documentation> of plone.org. You're welcome to help out.

Products.CMFDynamicViewFTI-4.0.5-1.lbn13.noarch: CMFDynamicViewFTI is a product for dynamic views in CMF

Products.CMFDiffTool-2.1-1.lbn13.noarch: Diff tool for Plone

Products.CMFDefault-2.2.4-1.lbn13.noarch: This product declares basic content objects and provides default implementation of some of the framework services for the Zope Content Management Framework (CMF).

Products.CMFCore-2.2.7-2.lbn13.noarch: This product declares the key framework services for the Zope Content Management Framework (CMF).

Products.CMFCalendar-2.2.3-1.lbn13.noarch: The CMFCalendar product is an example of creating a CMF Product. The CMFCalendar product is also expected to be a generally useful *out of the box* and skinnable to accomodate customization within your existing CMF instance. To see how to go about building a CMF product, this hopefully allows a developer to follow through the process of registering their product, skins, and help with the CMF by example. It shows how an object is created and registered with the types_tool, necessary skins added to the skins_tool, with the Calendar skins directory added to the skin paths, and providing portal_metadatool with an Element policy for the content_type of the object. For installing set the *active site configuration* of your site's setup tool to the CMFCalendar profile and import all steps. After installing the CMFCalendar you should notice a calendar appear in your CMF. This is fully customisable to your portals needs.

Products.CMFActionIcons-2.1.3-3.lbn13.noarch: The action icons tool provides a centralized registry mapping CMF "actions" (identified by their category and ID) to additional presentation metadata (display title and icon). The skins here show alternative mechanisms for using this metadata within a site template.

Products.BlueAwstatsManagementTool-2.0-3.lbn13.noarch: BlueAwstatsManagementTool is a products to manage access to the available statistics from AWStats on a Server. Added outside a plone site in the ZMI you can controll access to statistics in general. Installed Inside a plone site you have better abilities to control access to statistics on user level. There must be at least one Management Tool inside a zope instance to use BlueAwstats (and only one per folder level). The first one found by aquisition is used for the calling plone site.

« Previous 20 items Next 20 items » 1 ... 2309 2310 2311 2312 2313 2314 2315 ... 2359


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

Sections

Modified items