Search results

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.CMFQuickInstallerTool-3.0.16-2.lbn25.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.CMFQuickInstallerTool-3.0.16-2.lbn25.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.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.CMFTestCase-0.9.12-2.lbn25.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.CMFTestCase-0.9.12-2.lbn25.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.CMFTopic-2.2.1-3.lbn13.noarch

This product declares a topic content type for the Zope Content Management Framework (CMF).

Products.CMFTopic-2.2.1-3.lbn25.noarch

This product declares a topic content type for the Zope Content Management Framework (CMF).

Products.CMFTopic-2.2.1-3.lbn25.noarch

This product declares a topic content type for the Zope Content Management Framework (CMF).

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.